This naming convention applies by default to English-based hubs. For hubs that are not English-based, custom schema has been developed and can be found on individial pages where the mapping is stored. For example, the hub 5 schema in German can be found here.
Background
The FKL hubs use Vivenu as their ticketing platform. Historically, naming of events, categories, and types was inconsistent — the root cause of much of the parsing effort in the pipeline. This schema is applied across all hubs, events, and tickets and is designed to cover current and foreseeable edge cases.A few elements are provisional and may change as the Vivenu setup is optimised:
- Season passes are presently modelled as events. The intended direction is to use Vivenu bundles, with a parent–child relationship between a season ticket and its individual tickets.
- Ticket categories and ticket types are kept aligned (see Ticket Types). Whether this can be simplified is open.
- Metadata and API-driven creation are forward items: driving event and ticket creation through the API, with fixed selectable values rather than free text, would cut both effort and error.
1. Event Names
Format:[Category] [Region] [Series] [Round] - [Day], [Date Month]
Double-header edge case: Where two rounds run on the same day, both rounds appear in the event name and the format is otherwise unchanged.
Pro Championship Round 5 & 6 - Saturday, 29th August
2. Ticket Category Names
Single-event format:[Day] [AgeGroup] [WeightClass] [Timeslot] [Session]
Season-pass format:
[Day] [AgeGroup] [WeightClass] [Session] Pass
A future Combined Pass category may be introduced. The structure above is left unchanged until then.
3. Season-Pass Event Names
While season passes remain modelled as events, they follow: Format:[Category] [Region] [Series] [Year] [Session] Season Pass
4. Ticket Types
A ticket’s type aligns exactly with its category (see Ticket Category Names). They are kept in lockstep so the type carries no information the category does not.5. Alpha Hub-ID Prefix
Format:[[Hub-ID]] [Category] [Region] [Series] [Round]
The Hub-ID sits in square brackets at the start of the name.
6. Intacct Items
Format:[AgeGroup][Session]
The item dimension is deliberately coarse — the pipeline log holds the full breakdown, so Intacct only needs higher-level granularity. Age group crossed with session type gives twelve items:
Historical “Driver Training” categories map to the Testing items.
7. Intacct Project Codes
Format:[Entity]-[Region]-[Category]-[YY]-[DDMM]
DDMM is the day and month of the event. For a multi-day weekend it is always the Saturday date. Date-based codes are stable — if rounds are combined or renumbered, the code does not change.
Double-header weekends use one project code (Saturday and Sunday together), e.g.
UKFK-PRO-26-0405.
Mixed weekends — where Pro and Regional run on the same weekend — each series takes its own code so series profitability can be isolated. Finance performs the cost split at month end.
8. Calendar Session IDs
Format:[Entity]-[Cat][Region][Round]-[Day]-[Slot]-[Year]
9. Calendar Season IDs
Format:[Entity]-[Cat]-[Day]-[Sess]-[Year]
10. Pipeline Log References
Format:AUTO-[type]-[identifier]