The systems changing how vehicles are engineered, maintained and connected.
A software defined vehicle runs most functions as updatable software on a few central computers. That changes supplier roles, makes over-the-air updates a regulated activity and keeps the product changing long after sale.
Fleet dashcams record employees and the public, so operators need a DPIA before installation, audio off by default, short purpose-led retention, a subject access process and a plain explanation for drivers.
GSR2 requires drowsiness and distraction warnings on new EU vehicles, with limits on data use. Fleets should treat the built-in warning separately from any camera or telematics they add, which needs its own lawful basis.
SAE levels describe how the driving task is shared, but UK law uses its own self-driving test and user-in-charge categories. Check the ODD, the approval and the legal status before relying on any automation claim.
Switching behaviour without replacing an executable can increase operational flexibility and configuration complexity. Vehicle teams should govern flags through applicability, approved combinations and observable state, with clear ownership of activation decisions.
Cloud services can outlast development programmes and change ownership during a vehicle support life. Manufacturers should map dependencies and define a retirement path before a connected function becomes a lasting customer commitment.
A digital representation is useful when its evidence fits a specific decision. Automotive teams should define model scope, calibration and update responsibilities before relying on a digital twin to guide engineering or operations.
Open collaboration can support shared automotive software, but adoption creates responsibilities inside the manufacturer. Teams should assess maintenance, upstream participation and integration evidence alongside the functionality a component offers.
A vehicle software feature can change sustained resource demand. Engineering teams should review performance alongside thermal behaviour, monitoring and degraded operation so a successful short demonstration does not conceal a long-running constraint.
Processor capacity is a product planning decision as well as a hardware choice. Manufacturers should connect future workloads, shared resources and support commitments before treating spare compute as a guarantee of upgradeability.