ETSA Digital Grand Prix

Build. Compete. Get Discovered.

A project-based talent discovery program where African builders prove what they can do by solving real problems. The Digital Grand Prix is the umbrella; its first competitive edition will focus on developers.

Join the Grid Read the Working Brief
The Naming Structure

One platform. Multiple competitive classes.

ETSA Digital Grand Prix is designed to grow beyond one profession. Each edition can focus on a different discipline while using the same discovery, assessment and showcase system.

Umbrella Program

ETSA Digital Grand Prix

The permanent project-based talent discovery platform: open calls, qualifying tasks, build sprints, assessment, public showcases and ETSA Grid Cards.

Opening Competitive Class

Developer Edition

The first edition offers two separate project briefs for software and technical builders: driver telemetry analysis, or rig calibration and scrutineering.

Data & AI Product & UX Game & Simulation Hardware & Embedded Digital Media Esports Operations

These are possible future classes, not announced competitions. ETSA will open new classes only when the challenge, judging capacity and partner opportunities are credible.

Working Brief v2

Developer Edition: choose one of two independent projects.

Project 1 focuses on turning driving telemetry into useful coaching insight. Project 2 focuses on calibrating, comparing and scrutinising simulator rigs. Each project has its own users, problem statement, technical requirements and judging evidence.

Project 1 Driver Telemetry & Coaching Tool

Turn compatible lap and session data into clear, actionable driver-development insight.

 Project 2 Rig Calibration & Scrutineering Tool

Calibrate controls, compare simulator rigs and provide traceable technical evidence.
01
Independent Project 1

Driver Telemetry & Coaching Tool

Build a mobile-first tool that imports compatible motorsport or sim-racing telemetry and helps drivers and coaches understand where performance was gained, lost or made inconsistent. This project analyses driving performance after the data has been captured; it does not calibrate or scrutinise simulator hardware.

Performance Comparison

Explain the lap

  • Compare two compatible laps or sessions
  • Show lap, sector and mini-sector differences
  • Overlay speed, throttle, brake and steering traces when supplied
  • Identify consistency patterns and major time-loss areas
Coaching Output

Turn evidence into action

  • Translate data into clear observations
  • Separate measured facts from interpretation
  • Allow driver or coach notes and next-session targets
  • Present useful insight on mobile and low bandwidth
Comparison Gate

Compare like with like

  • Check track, layout, vehicle and session
  • Check units, timing and sampling rules when supplied
  • Show mismatched and unavailable parameters
  • Never invent missing telemetry
02
Independent Project 2

Rig Calibration & Scrutineering Tool

Build a vendor-neutral technical tool that helps teams calibrate simulator controls, allows scrutineers to test whether different rigs respond equivalently, and gives drivers evidence for developing braking, throttle and steering inputs. This is a hardware-configuration, control-response and rig-equivalence project, separate from lap coaching.

Reference Test Case

Same driver. Same declared conditions. Different result.

A driver tests Rig 2 and Rig 3 using the same game, vehicle, circuit, setup and session conditions, but the performance is different. The tool must determine whether the controllers, joysticks, wheel and pedals are calibrated and mapped equivalently, identify measurable differences, and show which differences could contribute to an advantage. It must report evidence and uncertainty rather than assume the rig caused the result.

Technical Team

Calibrate the rig

  • Record controllers, joysticks, wheel, pedals, firmware, drivers and relevant settings
  • Measure axis centre, dead zones, saturation, range, linearity, noise and repeatability
  • Compare live raw device input with the value received by the game
  • Calibrate brake, throttle, clutch, steering angle and force-feedback settings where accessible
Scrutineering

Compare rigs consistently

  • Lock game build, car, track, setup, assists, conditions and test procedure
  • Run the same driver through a repeatable Rig A/Rig B crossover test
  • Compare calibration, input latency, sampling, jitter and in-game response
  • Classify each parameter as equivalent, mismatched or unavailable
Driver Development

Develop control technique

  • Plot brake-pressure build-up and release curves
  • Compare trail-braking shapes and pedal repeatability
  • Review throttle application and steering-angle input
  • Compare steering rate, smoothness and force-feedback response where supplied
Calibration Record

Make every setup traceable

  • Save dated calibration profiles
  • Record who changed each controller setting, when and why
  • Compare before-and-after control response
  • Export a Rig 2/Rig 3 equivalence report
Integrity Rules

Evidence, not automatic penalties

  • Keep measured values, observations and decisions separate
  • Show missing information as unavailable
  • Identify possible advantage factors without claiming causation
  • Flag deviations without making automatic sporting decisions
  • Protect private technical and driver information
Practical Use

Work across different equipment

  • Use a vendor-neutral data model
  • Support wheels, pedals, controllers and joysticks
  • Support imported data and guided manual calibration tests
  • State which measurements the hardware can and cannot provide
  • Remain useful without requiring identical rig brands
Requirements for Both Projects

Working software and verifiable evidence.

Minimum submission

  • Working prototype or deployed demonstration
  • Source repository accessible to judges
  • README with setup and usage instructions
  • Short product demonstration video
  • Named contribution from every team member

Required testing

  • Project 1: compatible and incompatible telemetry comparisons
  • Project 2: repeatability, tolerance and rig-mismatch tests
  • Clear handling of missing or invalid data
  • Documented limitations and assumptions

Participant profiles

  • Software developers and technical builders
  • Data, electronics, simulation or product specialists
  • Students, professionals and self-taught talent
  • Individuals or small teams

Participants will enter Project 1 or Project 2 as separate submissions. The final briefs will define the supplied data, accepted hardware interfaces, calibration procedure, privacy rules and judging tests before entries open.

Planned Competition Pathway

From open interest to demonstrated ability.

The format is designed to reduce empty applications and reveal how people actually think, build, explain and collaborate.

1

Join the Grid

Register interest, identify your discipline and receive the launch announcement when the final brief is ready.

2

Qualify

Complete a focused individual task that verifies baseline ability before the main build stage.

3

Build

Develop the project during an online sprint and submit working evidence, documentation and a demonstration.

4

Showcase

Finalists demonstrate live; completed participants receive a record of verified challenge performance.

Provisional Evaluation

A transparent technical score, not a popularity contest.

Public engagement may support a separate Community Choice recognition, but technical winners should be determined by evidence and structured judging.

Technical execution25%
Problem relevance and usefulness20%
User experience and accessibility15%
Innovation15%
Reliability and performance10%
Low-bandwidth suitability10%
Documentation and demonstration5%

This matrix is provisional. The final scoring rules, tie-break process, judging panel and submission requirements will be published together in the official competition regulations.

What ETSA Is Building

More than a podium.

The aim is to leave participants with verified evidence and visibility, while giving partners a credible way to discover talent and useful prototypes.

ETSA Grid Card

A shareable profile showing demonstrated skills, project role, challenge result, badges and portfolio links.

Project Showcase

Valid submissions can be presented through an ETSA showcase, with finalists receiving greater visibility.

Partner Opportunities

Subject to partner confirmation: mentorship, equipment, cash awards, internships, paid projects, incubation or pilot discussions.

Planned intellectual-property principle: participants retain ownership of their work. ETSA and challenge partners may review and showcase submissions; any licensing, acquisition, employment or commercial development should require a separate agreement.

Register Interest

Join the Grid.

Register now to receive the official brief when entries open. The form also welcomes people interested in future Digital Grand Prix classes, judging, community distribution and sponsorship.

  • No entry fee or participation commitment at this stage
  • Dates and final rules have not yet been announced
  • Submitting this form does not guarantee selection
  • Your details will be used for ETSA challenge communication

Sponsors and technical partners

ETSA is inviting organisations to help define credible problems, provide judges and mentors, support rewards, and create real opportunities for high-performing participants.

Discuss Partnership