Why it matters
Without AI, BoP adherence and driver categorisation risk misallocation, penalties, unbalanced grids, and scrutineering delays that erode results and budgets.
From design to safety
Design
Define BoP and driver categories
The system reads BoP proposals, weight targets, power limits, and driver ratings; it models balance impact, updates setup sheets, and seeds a homologation baseline for parc ferme.
- BoP tables
- weight targets
- driver ratings
Build
Incorporate calculations into build data
Data from BoP, weights, and planned stints is embedded into the car's setup sheets, homologation records, and simulation baselines, with versioned change control and traceable approvals.
- data framework
- setup sheets
- compliance dossier
Operation
Run real-time BoP checks
System cross-checks live telemetry with current BoP, ensures power/weight stays within limits, flags anomalies, and generates proactive alerts for pit crew and race control before parc ferme.
- telemetry feed
- BoP validation module
- stint planner
Maintenance
Lifed-part and configuration tracking
AI reviews wear indicators on ballast, weight sensors, and ECU mappings; triggers reallocation or repairs during rebuilds between events, maintaining a continuous BoP ledger.
- weighing scales
- ballast mapping
- ECU log
Safety
Auditable regulatory compliance
All BoP decisions and driver categorisations are signed off by the technical director and logged for scrutineering and FIA checks, with tamper-evident records and exportable reports.
- compliance ledger
- auditable reports
- driver rating records
Part by part
- 1
weighing scales and load cells
- Watch for
- weight drift, ballast choke, or sensor cross-talk during pre-event validation and setup verification
- AI action
- flag overweight/underweight readings; trigger recheck and reprint setup sheets immediately
- 2
powertrain control unit (ECU)
- Watch for
- ECU maps drifting from BoP targets or switching preloads unexpectedly
- AI action
- recommend ballast or map adjustments; log BoP-aligned changes in records
- 3
fuel flow sensor
- Watch for
- aberrant fuel flow readings affecting power metrics during BoP verification
- AI action
- alert for potential BoP + fuel strategy mismatch; propose recalibration
- 4
dashboard driver rating display
- Watch for
- driver rating category drift or misrecorded class in central dashboard
- AI action
- update driver category, adjust stint rules in strategy module
- 5
stint timer unit
- Watch for
- stint length deviations from planned allocations across multiple drivers
- AI action
- adjust future stints; propose alternate driver assignments
- 6
transponder and data logger
- Watch for
- data gaps or timestamp misalignments in telemetry feeds
- AI action
- flag data integrity issues; initiate data stitching and verification
Worked example
Balancing BoP and driver categorisation before a sprint race
Illustrative scenario with sample data.
A GT field requires updated BoP and driver categorisation due to model shifts; AI recalibrates allocations and prepares docs for parc ferme with versioned approvals and backstop rules for parity.
Signal in
BoP version: v2.3.4; car weights: 1130 kg, target power: 520 kW, driver ratings: A, B, C; stints: 20/25/20 minutes; ballast offsets: +6 kg, -4 kg; fuel window: 70 L; BoP table row: 12A+
System out
BoP-adjusted weights and power setpoints; updated driver categories; revised setup sheets; regenerated parc ferme compliance logs; new stint plan with fallback driver assignments; traceable change records linked to v2.3.4
Human sign-off: Technical Director approves BoP and driver category changes; Compliance Manager signs off on the driver categorisation and BoP adjustments; logs are archived for scrutineering and FIA checks.
How to roll it out
Phase 1
Weeks 1 to 4
Baseline BoP integration with data ledger; establish data feeds, validation checks, and versioned change control.
Phase 2
Weeks 5 to 8
Pilot on test events; calibrate thresholds, refine alerting rules, and document approval workflows.
Phase 3
Weeks 9 to 12
Full weekend rollout; lock in BoP updates, driver categories, reporting templates, and scrutineering-ready exports.
Where people stay in charge
- Decisions on driver categorisation stay with the regulator or series’ governing body; no unilateral changes after submission.
- BoP adjustments require two-person sign-off: technical director and compliance manager, with timestamped records.
- All data changes must be logged with user IDs, timestamps, and changelog exports for scrutineering.
Questions owners and crews ask
How will AI handle driver categorisation changes across a season?
AI maps drivers to pre-defined categories based on performance indicators, experience, eligibility rules, and observed race data; final approval rests with the team principal and the regulator.
What happens if a BoP reading conflicts with a regulatory sheet?
The regulatory sheet overrides; AI flags the discrepancy for immediate human review, reconciliation before parc ferme, and a documented corrective action.
Can the system adjust stints automatically during a race?
Yes, it proposes optimal stint breaks based on fuel, tire wear, and BoP limits; final decision rests with the race engineer and captain.
How is data integrity protected for scrutineering?
All BoP decisions and driver category changes are logged in an auditable ledger with timestamped records and signed approvals; exportable to regulatory portals.