DevOps for Automotive & mobility platforms

What regulates the infrastructure

What actually goes wrong here

• Enterprise IT compromise halting global production. The Jaguar Land Rover incident starting late August 2025 stopped manufacturing across UK, Slovak, Brazilian and Indian plants for roughly five weeks; UK car output that September was reported as the lowest for the month since 1952, with estimated economy-wide damage around GBP 1.9 billion and thousands of supply-chain businesses affected. The mechanism is that ordering, scheduling and parts-call-off systems are what actually run the line.
• Sub-tier supplier compromise propagating upward through just-in-sequence supply. Sequenced parts arrive in build order with almost no buffer, so a supplier's IT failure stops the OEM within a shift — the February 2022 ransomware compromise of Toyota's tier-1 supplier Kojima Industries halted all 14 of Toyota's Japanese plants and 28 production lines — and the deeper the tier, the less visibility the OEM has into that supplier's security posture.
• Vehicle backend compromise as a type-approval exposure. Because UN R155 brings backend servers inside the approved CSMS, a backend security failure can call the approval itself into question, not merely trigger an incident response — a consequence with no equivalent in most other industries' cloud estates.
• Loss or corruption of software configuration records under UN R156. If the manufacturer cannot demonstrate which approved software version is on which vehicle, the update path is blocked until the record is reconstructed, so record integrity gates the ability to ship fixes.
• OTA campaign failure leaving vehicles in an inconsistent or non-drivable state. Rollback across a distributed fleet with intermittent connectivity is materially harder than server-side rollback, and the failed units are in customers' driveways.
• Prototype and pre-launch design data leakage through the supplier chain, which damages competitive position and can breach the prototype-protection commitments that TISAX-assessed suppliers give contractually.

How demand behaves

Production itself is takt-paced and deliberately steady — the line runs to a fixed cycle time and the supply chain is tuned to it, so volatility is a defect rather than a feature. The variable load sits elsewhere: connected-vehicle telemetry ingest scales with the size of the fleet in the field and runs continuously, and OTA campaign windows create large, scheduled egress bursts when a software release is pushed to hundreds of thousands of vehicles. Engineering compute (simulation, ADAS data labelling, validation) is bursty and concentrated ahead of programme milestones.

Data you will be holding

Vehicle telemetry linked to a VIN or an account is personal data in the EU — the EDPB's guidelines on connected vehicles treat location and usage data as identifying — and location history is among the more sensitive categories. Separately, pre-launch design data, tooling and prototype information is protected under supplier contracts, and the industry's TISAX scheme (built on the VDA ISA catalogue) sets specific prototype-protection requirements that go beyond ordinary information security.

Architecture this pushes you toward

Three distinct estates coexist with different constraints: plant systems (MES, sequencing, andon, robot cells) that are latency-sensitive and must keep running through a WAN failure; engineering and validation compute (CAE simulation, ADAS sensor-data labelling and replay) that is bursty and petabyte-scale; and vehicle backends that must be globally reachable, region-partitioned for data-protection reasons, and provably in scope of the certified CSMS. Homologation evidence and software configuration records have retention horizons matching the vehicle's service life, which is far longer than typical enterprise retention.

Availability expectation

No single industry figure. Assembly-line tolerance is expressed as cost per minute of line stoppage rather than as an availability percentage, and OEMs cascade that intolerance to suppliers through contractual line-stoppage liability. Vehicle backend services carry a separate expectation because a failed backend can affect vehicles already in customers' hands, and under UN R155 the backend is part of the approved system rather than an ordinary IT service.