Postgraduate Diploma in Vehicle SRE: SLIs/SLOs and Field Telemetry
Online Postgraduate Diploma of 800 hours in Vehicle SRE: SLIs/SLOs and Field Telemetry. 8 modules covering UNECE R156, ISO 24089:2023 and Prometheus. Assigned tutor and open enrolment.
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
Apply SRE principles to fleets of connected vehicles.
Design user-oriented service level indicators.
Set service objectives and manage error budgets.
Architect field telemetry while respecting privacy.
Monitor fleet health with actionable alerts.
Manage fleet incidents and learn from them.
Build reliability into the design of services.
Who it's for
- Vehicle SRE engineer who wants to specialise in Vehicle SRE: SLIs/SLOs and Field Telemetry.
- Telemetry engineer who wants to specialise in Vehicle SRE: SLIs/SLOs and Field Telemetry.
- Fleet operations manager who wants to specialise in Vehicle SRE: SLIs/SLOs and Field Telemetry.
- Automotive backend engineer who wants to specialise in Vehicle SRE: SLIs/SLOs and Field Telemetry.
- Field quality analyst who wants to specialise in Vehicle SRE: SLIs/SLOs and Field Telemetry.
- Incident manager who wants to specialise in Vehicle SRE: SLIs/SLOs and Field Telemetry.
- Graduates in engineering or sciences seeking to join car manufacturers.
What you'll work with
- UNECE R156
- ISO 24089:2023
- ISO/SAE 21434:2021
- Reglamento (UE) 2023/2854
- Reglamento (UE) 2016/679
- ISO 26262-7:2018
- ISO/IEC 20000-1:2018
- ISO 20078
8 modules · 800 h
1.1Principles of SRE and their origin1.2Differences between cloud services and vehicle fleets1.3Reliability, availability and safety1.4Error budgets and decision-making1.5Toil and operational automation1.6Relationship with functional safety1.7Responsibilities of the fleet SRE team1.8Support models and on-call duty1.9Blameless culture and learning1.10Case study: analysis of a mass infotainment failure
2.1Indicators oriented to the vehicle user2.2Availability of connected functions and services2.3Start-up latency and HMI response latency2.4Update failure rate2.5Cellular connectivity quality2.6SLIs for ADAS systems: availability and deactivations2.7Measurement in the vehicle versus measurement in the backend2.8Sampling and measurement bias2.9Documentation of SLI specifications2.10Workshop: SLI catalogue for a remote charging service
3.1Objectives by function and fleet segment3.2Evaluation windows3.3Error budgets and release policies3.4Composite SLOs and dependencies3.5Agreements with service providers3.6Alerts based on burn rate3.7Periodic review of objectives3.8Communication with product and management3.9Common mistakes when setting objectives3.10Practice: error budget policy for OTA updates
4.1Data collection architecture in the vehicle4.2Signals normalised with COVESA VSS4.3Triggers, buffers and prioritisation4.4Transmission with MQTT and compression4.5Ingestion into streaming platforms4.6Time-series storage4.7Driver consent and privacy4.8Data access under the European Data Act4.9Connectivity costs4.10Laboratory: telemetry pipeline with MQTT and Kafka
5.1Fleet health dashboards5.2Segmentation by model, version and region5.3Statistical anomaly detection5.4Event correlation across vehicles5.5Actionable alerts and noise reduction5.6Geographic heat maps5.7Monitoring of cloud dependencies5.8Visualisation tools5.9Review of alert effectiveness5.10Practice: fleet health dashboard in Grafana
6.1Detection, triage and escalation6.2Incident roles and communication6.3Mitigation: rollback, deactivation and patching6.4Coordination with after-sales service and workshops6.5Incidents with safety impact6.6Notification to authorities and recall campaigns6.7Blameless postmortem analysis6.8Follow-up of corrective actions6.9Incident simulations6.10Case study: postmortem of a failed update across a fleet
7.1Failure mode analysis of connected services7.2Graceful degradation without connectivity7.3Watchdogs and automatic recovery in ECUs7.4Chaos testing on the backend and on the bench7.5Backend capacity planning7.6Reliability of the update chain7.7Management of third-party dependencies7.8Production readiness reviews7.9Reliability indicators in the development lifecycle7.10Workshop: production readiness review of a connected service
8.1Selection of the service or function8.2Definition of SLIs8.3Setting SLOs and error budget8.4Telemetry design8.5Dashboards and alerts8.6Incident management procedure8.7Reliability improvement plan8.8Reliability report8.9Dissertation and presentation8.10Final review with the tutor
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: students progress at their own pace within the intake, which makes it possible to combine the programme with work.
Each module combines theory, guided reading of the original standard and applied exercises. The working software is Prometheus, Grafana, Apache Kafka, OpenTelemetry, InfluxDB, in free, academic or evaluation versions. The practical tests draw on real procedures for monitoring SLOs across connected fleets, postmortem analysis of field incidents and chaos testing on the backend of connected services. Assessment is continuous, module by module, plus the final integrative project.
Build it end to end
Your final project follows the real engineering workflow, step by step, reviewed by your tutor.
Apply SRE principles to fleets of connected vehicles.
Design user-oriented service level indicators.
Set service objectives and manage error budgets.
Architect field telemetry while respecting privacy.
Monitor fleet health with actionable alerts.
Where this takes you
Requirements
- Prior technical training or professional experience in the sector. No university degree is required.
- Internet connection and a computer capable of running the programme's software.
- Sufficient Spanish to follow the reading of technical regulations.
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 comprises 800 hours in total, spread over 6 to 8 months. That is between 10 and 15 hours a week on average, compatible with a full-time job.
The programme works with Prometheus, Grafana, Apache Kafka, OpenTelemetry, InfluxDB. Free, academic or evaluation versions are used, and the tutor indicates the free alternative where one exists.
An own diploma from SEIUM upon passing the continuous assessment and the integrative project. It is in-house training, not an official qualification from the Ministry.
Yes. Modules passed in a course or postgraduate diploma in the same area are recognised towards the advanced programme. Check the recognition policy when you enrol.
Related programmes
Diploma in Product Management of SDV/ADAS and Feature Monetization
Online postgraduate diploma of 800 hours in SDV/ADAS product management and feature monetisation. 8 modules covering the software-defined vehicle as a product, product discovery, roadmaps and…
Postgraduate Diploma in Risk-Based Scenario Catalogues and ODD KPIs
Online 800-hour Postgraduate Diploma in Risk-Based Scenario Catalogues and ODD KPIs. 8 modules covering ISO 34502:2022, ISO 34503:2023 and esmini. Assigned tutor and open enrolment.
Postgraduate Diploma in In-Vehicle Stores and SDV Operational Telemetry
Online 800-hour Postgraduate Diploma in In-Vehicle Stores and SDV Operational Telemetry. 8 modules covering UN Regulation No. 156, Regulation (EU) 2016/679 (GDPR) and Grafana. Dedicated tutor…
More in Autonomous, ADAS & Software-Defined Vehicle
All Autonomous, ADAS & Software-Defined Vehicle programmes → · How to apply · Fees & financing · Scholarships