World premiere at embedded world 2026

SECOR SDV LAB – the first development environment in which hardware and software for the Software Defined Vehicle (SDV) work together right from the start – not just in the prototype.

The SECOR SDV LAB: A real development environment – not just another concept

The SECOR SDV LAB is a compact, ready-to-use hardware platform that can be built on the existing development infrastructure of the Tier 1 – without system breaks or proprietary lock-ins. Tier-1s start with a single vehicle function and gradually extend the SECOR SDV LAB to the entire vehicle project.

Technical components

• ZCU (Zonal Control Unit) – zonal control unit on which the software modules of the Tier 1s run
• CCU (Central Control Unit) – central computing unit for the vehicle architecture
• connect – standardized interface modules for sensors and actuators
• Message Broker – communication layer between all components
• Direct connection to the SECOR SDV AppStore for over-the-air (OTA) software updates

THE PROCESS

Three phases: Development errors are prevented – not repaired

Phase 1: approx. 36 months before SoP – tender rethink

Instead of a complete component with ECU, the OEM will in future tender for two services: the hardware component (without ECU) and the associated software module. The SECOR SDV LAB supports Tier 1s in carrying out this separation precisely and in compliance with standards. Integration errors, which today only become visible in the prototype, are structurally impossible here.

Phase 2: approx. 24 months before SoP – integration without surprises

The OEM builds its test vehicle and loads all software directly via OTA from the SECOR SDV AppStore. Weekly function and system checks, structured error lists for each Tier 1 module, corrections directly in the LAB – an iterative process in short cycles. The classic integration stress at the end of development is eliminated.

Phase 3: from SoP – software lives with the vehicle

With the pay-per-use model of the SECOR SDV AppStore, the Tier 1 has an economic incentive to maintain its software over the entire vehicle life cycle. New features via OTA. Bug fixes without a recall. The end of the “develop once, then freeze” model.

MEASURABLE RESULTS

What OEMs and Tier 1s actually gain

30% lower development costs thanks to early hardware-software separation, parallel development and standardized APIs

50% faster time-to-market thanks to iterative integration from the first prototype instead of expensive correction rounds

100% updateable over the life cycle – OTA updates, AppStore model, permanently maintainable software without recalls