Live
Overview
The Operator Dashboard exists to reduce manual effort and data inconsistencies in the operational management of FKL events. Before this tool, operators managed bookings, drivers and event logistics through fragmented manual processes — typically via Vivenu directly and spreadsheets. The OD centralises this into a single internal application and serves as the bridge between the GKL Platform and the AlphaTiming timing system.
How It Works
The OD is an internal web application that communicates with GKL API for all data operations. It allows operators to manage bookings, events, users, tickets and drivers across FKL events, with no direct database access.
A critical operational function of the OD is the driver ID export workflow: operators download a driver ID export generated by GKL API from the OD, then manually upload it to AlphaTiming before each event. This populates the timing event with entries, allowing timing results to be matched to the correct drivers when read from TalentID:Coaching.
The OD also gives operators visibility of timing results by reading data directly from TalentID:Coaching, allowing them to cross-reference event data with performance data and save comments on data quality issues.
The driver ID upload to AlphaTiming is a manual process that must be completed before every event. If this step is missed, timing results will not be matched to drivers correctly in TalentID:Coaching.
Repositories
| Repository | Description |
|---|
| GklPlatform-OperatorWebApp | Operator Dashboard web application |
Dependencies
Internal
- GKL API — All data operations (event management, bookings, users, tickets, driver management, driver ID export) are handled via GKL API. The OD has no direct database access.
- TalentID: Coaching — The OD reads timing results directly from TalentID:Coaching to display performance data to operators alongside event data. Also writes operator comments on data quality issues back to TalentID:Coaching.
External
- AlphaTiming (indirect) — Operators download the driver ID export from the OD and manually upload it to AlphaTiming. This is a manual step and a process dependency for every event.
