Show notes
🎙️ WHEN THE RACE CIRCUIT BECOMES THE NETWORKIn this episode of Automotive Storytelling, Stéphane Lagresle travels to the Isle of Man during TT Race Week to examine one of the most structurally underexplored problems in connected vehicles: what actually happens to a car's data between the antenna and the application. Filmed on location with the founders of Stacuity, a software-defined connectivity company, this conversation moves from a 37-mile racing circuit to the engineering reality beneath the SDV transition.🎯 KEY INSIGHTSThe Tromboning ProblemA Latency Risk Built Into Most Connected Vehicle Architectures Today A car in Australia connects to a mobile network. The data leaves the country, routes to Europe, and comes back. That round trip adds hundreds of milliseconds to every session. Brazil has already legislated against it. India is moving in the same direction. More markets are following faster than vehicle programmes can respond. And the cars already in the field cannot be recalled to fit new SIMs.Fleet Retrofits Without Hardware ChangesWhat APN Repointing Actually Means The most commercially significant detail in this episode is also the least intuitive. Existing fleets can be redirected to in-country infrastructure without touching a single vehicle. No SIM swap, no over-the-air update to the device itself. John Freeman walks through the mechanism: you repoint an Access Point Name inside the network, and every existing subscriber follows. For OEMs facing sovereignty regulation in markets they are already operating in, this changes the nature of the problem entirely.Software-Defined Connectivity Compresses Market Entry From Months to Weeks A partner approached Stacuity with a test request: half a million subscribers, edge connectivity validation for a Chinese customer. Traditional infrastructure: six to nine months. With Stacuity's software-defined layer, the APN was configured and traffic routed in four minutes. The full live solution went live four and a half weeks after the request arrived. John Freeman's framing: the connectivity layer should never be the variable that slows an OEM's market entry.The Marshals as a Network Architecture Model Laura Sawyer describes how more than five hundred marshals manage a 37-mile public road circuit with no single point of failure. Each node passes information forward, flags anomalies, and routes around failure. The episode uses this as its central analogy: handover, edge intelligence, and redundancy, running as a human distributed network since 1907, long before anyone gave it a technical name. It is the clearest non-specialist explanation of what software-defined connectivity is actually trying to replicate.💡 PRACTICAL TAKEAWAYSAudit your data routing paths before regulation arrives. If your vehicles route connectivity data through servers outside the country of use, the legal exposure is already building. Brazil and India have acted. More markets are moving. The audit is easier than the retrofit.Do not assume hardware changes are required for sovereignty compliance. If your fleet uses traditional SIM-based routing, an APN-level redirect may resolve the regulatory exposure without vehicle recall. Understand the mechanism before scoping a programme.Evaluate connectivity infrastructure against deployment speed, not feature parity alone. A six-to-nine-month connectivity deployment timeline is not a technical constraint. It is an architecture choice. Software-defined alternatives exist and are in production.Treat connectivity as a core SDV design variable, not a commodity. The software-defined vehicle requires a software-defined network layer. Connectivity decisions made at programme start will determine what is achievable at launch and in the field.🌟 ABOUT YOUR GUIDESChris Hall is Chairman of Stacuity. In 2001, he was part of the team who secured Europe's first 3G licence and launched the Western Hemisphere's first 3G network from the Isle of Man, competing directly with Japan's DoCoMo. His route to the licence: a letter, a 19-pence stamp, and a week's wait.John Freeman is CEO of Stacuity. He leads commercial strategy and partnership development for a platform designed to give OEMs and operators the network-layer flexibility that traditional mobile infrastructure cannot provide.Mike Bromwich is CTO and co-founder of Stacuity. During lockdown, he built a complete mobile core network from first principles, software-only and without proprietary hardware, because the existing architecture could not answer the questions the industry was beginning to ask. His explanation of what software-defined connectivity means in engineering terms is the clearest in this episode.Laura Sawyer is Director of Marshals for the Isle of Man TT, responsible for more than five hundred volunteer officials across a 37-mile public road circuit. Her description of how the marshal network operates provides the episode's central analogy, and the reason this conversation was filmed here and nowhere else."Under the Hood: Automotive Storytelling" uncovers the human narratives driving innovation in an industry that impacts lives worldwide. Hosted by Stéphane Lagresle, this podcast explores how the power of storytelling ultimately connects technology to humans.