Master’s in OTA, Diagnostics & Operations Engineering
Online master's programme of 1,900 hours in OTA, diagnostics and operations engineering, structured in 12 modules covering OTA updates and update chain security, UDS and DoIP diagnostics, fleet telemetry, predictive maintenance, field quality, software operations, edge and cloud, operational cybersecurity and data regulation (UN ECE R156, ISO 24089, ISO 14229-1), with an assigned technical tutor.
Take the controls.
Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.
What you will be able to do
Design secure OTA architectures for the connected vehicle.
Implement SUMS in compliance with R156 and ISO 24089.
Apply UDS and DoIP diagnostic protocols.
Build fleet telemetry pipelines.
Develop predictive maintenance models.
Manage software operations and cybersecurity across the fleet.
Develop a connected vehicle operations project.
Who it's for
- OTA engineers responsible for software update systems.
- Diagnostics engineers working with UDS, DoIP and remote diagnostics.
- Telematics engineers developing connected vehicle services.
- Fleet operations managers overseeing vehicles in service.
- Field quality data analysts working with warranty and fleet data.
- Cloud platform engineers building automotive backends.
- Engineering or science graduates seeking to enter the automotive sector.
What you'll work with
- UN ECE R156 (software updates and update management systems)
- ISO 24089 (road vehicles – software update engineering)
- ISO 14229-1 (unified diagnostic services (UDS))
- ISO 13400-2 (diagnostic communication over IP (DoIP))
- UN ECE R155 (cybersecurity management systems)
- ISO/SAE 21434 (road vehicle cybersecurity engineering)
- Regulation (EU) 2023/2854 (Data Act) (EU rules on fair access to and use of data)
- ISO 22900-2 (modular vehicle communication interface (D-PDU API))
- Vector CANoe
- AWS IoT FleetWise
- Eclipse Mosquitto
- Uptane
- Grafana
12 modules · 1900 h
1.1Life cycle of the connected vehicle1.2On-board telematics and TCU units1.3Manufacturer's connected services1.4Fleet operations throughout the vehicle life1.5Relationship between OTA, diagnostics and data1.6Manufacturer's backend architecture1.7Regulation driving connectivity1.8After-sales business models1.9Organisation of vehicle operations1.10Case study: operations of a connected fleet
2.1Update types: firmware, software and data2.2Full and partial ECU updates2.3A/B architectures and partitions2.4Differential updates and compression2.5Orchestration of multi-ECU updates2.6Safe installation conditions2.7Recovery from update failures2.8User experience of the update2.9Data and bandwidth costs2.10Lab: A/B update on an embedded board
3.1Regulation R156 and the SUMS3.2The ISO 24089 standard3.3The Uptane framework for automotive3.4Package signing and verification3.5Rollback protection3.6Update server security3.7RXSWIN software identification3.8Configuration compatibility management3.9Evidence for type approval3.10Practical: Uptane test repository
4.1The UDS protocol ISO 142294.2Diagnostics over IP (DoIP)4.3Fault codes and snapshots4.4Regulatory OBD diagnostics4.5ODX diagnostic description4.6Remote diagnostics from the backend4.7Secure diagnostics and authentication4.8Workshop tools4.9Diagnostics of ADAS systems4.10Workshop: UDS session with CANoe
5.1In-vehicle data collection5.2MQTT protocols and transmission5.3Bandwidth management5.4Triggers and smart sampling5.5Mass ingestion platforms5.6Time-series storage5.7Data quality and completeness5.8Privacy and consent5.9Connectivity costs5.10Lab: MQTT pipeline to a time-series database
6.1Component degradation models6.2Remaining useful life prognosis6.3Battery state of health across the fleet6.4Anomaly detection in signals6.5Machine learning for failures6.6Integration with the workshop network6.7Management of preventive campaigns6.8Economic assessment of predictive maintenance6.9Industry success stories6.10Practical: battery remaining useful life model
7.1Early detection of quality problems7.2Warranty analysis7.3Management of recall campaigns7.4Communication with authorities7.5Root cause analysis with fleet data7.6Regulatory post-market monitoring7.7In-service quality indicators7.8Feedback to engineering7.9Management of serious incidents7.10Case study: detection of a software defect
8.1Fleet configuration management8.2Planning of update campaigns8.3Staged and canary deployments8.4Monitoring of update success8.5In-service version management8.6Withdrawal of defective versions8.7Support for older vehicles8.8Coordination with dealerships8.9Operations metrics8.10Workshop: staged deployment plan
9.1In-vehicle versus cloud processing9.2Vehicle edge architectures9.3Automotive cloud platforms9.4MEC computing in 5G networks9.5State synchronisation between vehicle and cloud9.6Digital twin of the vehicle9.7Backend scalability9.8Resilience to loss of connectivity9.9Infrastructure costs9.10Lab: vehicle digital twin in AWS IoT
10.1The VSOC operations centre10.2Intrusion detection across the fleet10.3In-service vulnerability management10.4Cybersecurity incident response10.5Automotive threat intelligence10.6Coordination with Auto-ISAC10.7Regulatory incident notifications10.8Response exercises10.9Operational security metrics10.10Practical: fleet response playbook
11.1The European Data Act regulation11.2GDPR in connected services11.3Third-party access to vehicle data11.4Data for independent repair11.5eCall and legal requirements11.6EDR and DSSAD recorders11.7Data retention and deletion11.8Transparency towards the user11.9Regulatory trends in data11.10Case study: data portal for workshops
12.1Definition of the fleet and services12.2OTA and SUMS architecture12.3Remote diagnostics strategy12.4Telemetry pipeline12.5Predictive maintenance model12.6Software operations plan12.7Operational cybersecurity plan12.8Conclusions and roadmap12.9Thesis report12.10Master's Thesis: defence before a panel
How you'll learn
100% online training on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within each intake, making it compatible with work.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is Vector CANoe, AWS IoT FleetWise, Eclipse Mosquitto, Uptane and Grafana, in free, academic or evaluation versions. Testing is studied through real procedures: UDS and DoIP diagnostic sessions, staged update campaigns and fleet data analysis for quality. Assessment is continuous for each module, plus the final Master's Thesis.
Standards covered: UN ECE R156, ISO 24089, ISO 14229-1, ISO 13400-2, UN ECE R155, ISO/SAE 21434, Regulation (EU) 2023/2854 (Data Act), ISO 22900-2.
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Where this takes you
Requirements
- A university degree in engineering, science or architecture, or equivalent demonstrable professional experience.
- An internet connection and a computer capable of running the programme software.
- English sufficient to read technical standards.
Ready to start?
Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.
Frequently asked questions
The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.
You work with Vector CANoe, AWS IoT FleetWise, Eclipse Mosquitto, Uptane and Grafana, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.
A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.
A degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the software and English sufficient to read technical standards.
Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.
Related programmes
Master’s in Product, Regulation & Business Engineering
Online master's programme of 1,900 hours in product, regulation and business engineering for automated driving: 12 modules covering product management, the international regulatory framework, safety as…
Master’s in Diagnostics, Telemetry and Edge Analytics Engineering
Online master's programme of 1,900 hours in diagnostics, telemetry and edge analytics engineering, structured in 12 modules covering on-board diagnostics, vehicle telemetry, edge analytics, cloud data…
Master’s in Heterogeneous Computing for AD (CPU/GPU/NPU)
Online master's programme of 1,900 hours in heterogeneous computing for autonomous driving (CPU/GPU/NPU). 12 modules covering GPU programming, neural network inference, task scheduling, memory, power and…
More in Autonomous, ADAS & Software-Defined Vehicle
All Autonomous, ADAS & Software-Defined Vehicle programmes → · How to apply · Fees & financing · Scholarships