Master'sAutonomous, ADAS & Software-Defined Vehicle Applications open

Master’s in Runtime Monitoring Engineering

Online master's programme of 1,900 hours in runtime monitoring engineering, structured in 12 modules covering runtime verification with temporal logic, perception, planning and ODD monitoring, safe states and degradation, monitors for AI components and safety certification under ISO 26262, ISO 21448 and UL 4600, with an assigned technical tutor.

Duration1900 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Virtual lab · try it before you enrol

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.

SIM · LIVE ●
Learning outcomes

What you will be able to do

01

Design runtime monitoring architectures.

02

Specify formal properties in temporal logic.

03

Implement perception, planning and ODD monitors.

04

Define safe states and degradation strategies.

05

Apply monitors to AI-based components.

06

Integrate monitors into the safety argument.

07

Develop a complete runtime monitoring project.

Profile

Who it's for

  • Autonomous systems safety engineers looking to deepen their expertise in runtime monitoring.
  • Runtime verification engineers who want a broader, standards-based view of supervision architectures.
  • Functional safety architects designing monitors and fallback paths.
  • Diagnostics engineers moving into supervision of automated driving systems.
  • Validation engineers responsible for monitor coverage and field evidence.
  • Researchers in formal methods seeking industrial application.
  • Engineering or science graduates aiming to enter the automotive sector.
Standards & tools

What you'll work with

  • ISO 26262 (functional safety of road vehicles)
  • ISO 21448 (safety of the intended functionality, SOTIF)
  • UL 4600 (safety of autonomous products)
  • ISO/PAS 8800 (safety and AI in road vehicles)
  • UN ECE R157 (Automated Lane Keeping Systems)
  • IEEE 2846 (assumptions for models in automated driving safety)
  • ISO 34503 (ODD taxonomy for automated driving)
  • IEC 61508 (functional safety of E/E/PE systems)
  • RTAMT
  • Breach
  • ROS 2
  • CARLA
  • MATLAB/Simulink
Syllabus

12 modules · 1900 h

  1. 1.1The need for runtime monitors
  2. 1.2Limits of pre-deployment verification
  3. 1.3Doer-checker monitoring architectures
  4. 1.4The simplex pattern and fallback control
  5. 1.5Monitors versus redundancy
  6. 1.6Monitoring in aviation and rail
  7. 1.7Independence requirements
  8. 1.8Taxonomy of monitors
  9. 1.9Examples in production vehicles
  10. 1.10Case study: monitoring architecture of a robotaxi
  1. 2.1Linear temporal logic (LTL)
  2. 2.2Signal temporal logic (STL)
  3. 2.3Monitor synthesis from specifications
  4. 2.4Quantitative robustness in STL
  5. 2.5Online and offline monitors
  6. 2.6The RTAMT and Breach tools
  7. 2.7Specification of traffic rules
  8. 2.8Predictive monitors
  9. 2.9Computational cost of monitors
  10. 2.10Lab: STL safe-distance monitor
  1. 3.1Detection of out-of-distribution inputs
  2. 3.2Uncertainty estimation in neural networks
  3. 3.3Temporal consistency monitors
  4. 3.4Consistency between redundant sensors
  5. 3.5Detection of ghost objects
  6. 3.6Image quality monitoring
  7. 3.7Activation-based monitors
  8. 3.8Evaluation of perception monitors
  9. 3.9Integration with sensor fusion
  10. 3.10Practical exercise: energy-based OOD detector
  1. 4.1Checking trajectories against collisions
  2. 4.2The RSS model as a monitor
  3. 4.3Online reachable sets
  4. 4.4Dynamic feasibility monitors
  5. 4.5Verification of traffic rules
  6. 4.6Control stability monitors
  7. 4.7Oscillation detection
  8. 4.8Actuator monitoring
  9. 4.9Arbitration and switching to fallback
  10. 4.10Workshop: RSS monitor in CARLA
  1. 5.1ODD specification
  2. 5.2Detection of ODD exit
  3. 5.3Weather and visibility monitoring
  4. 5.4Road type monitoring
  5. 5.5Traffic density monitoring
  6. 5.6Use of the map in ODD monitoring
  7. 5.7Warnings and control transitions
  8. 5.8Logging of exit events
  9. 5.9Validation of ODD monitors
  10. 5.10Lab: map-based ODD monitor
  1. 6.1ECU and process monitoring
  2. 6.2Watchdogs and heartbeats
  3. 6.3Latency and deadline monitoring
  4. 6.4Memory and resource monitoring
  5. 6.5Sensor diagnostics
  6. 6.6Fault management in AUTOSAR
  7. 6.7Monitoring of the communications network
  8. 6.8Aggregation of health status
  9. 6.9Degradation management
  10. 6.10Practical exercise: deadline supervisor in ROS 2
  1. 7.1Definition of safe states
  2. 7.2Minimal risk manoeuvre
  3. 7.3Graceful degradation of functions
  4. 7.4Fail-safe versus fail-operational
  5. 7.5Independent fallback paths
  6. 7.6Dual-channel architectures
  7. 7.7Transition requirements
  8. 7.8Coordination with the driver
  9. 7.9Validation of emergency manoeuvres
  10. 7.10Case study: MRM on a motorway
  1. 8.1Requirements of ISO/PAS 8800
  2. 8.2Input data monitoring
  3. 8.3Model drift monitoring
  4. 8.4Detection of adversarial attacks
  5. 8.5Explainability monitors
  6. 8.6Statistical guarantees of monitors
  7. 8.7Conformal prediction for guarantees
  8. 8.8Fleet monitoring
  9. 8.9Continuous improvement loop
  10. 8.10Workshop: conformal prediction in object detection
  1. 9.1Hardware and software independence
  2. 9.2ASIL allocation to monitors
  3. 9.3Implementation on safety microcontrollers
  4. 9.4Monitors in hypervisors
  5. 9.5Monitor latency requirements
  6. 9.6Secure communication with the monitor
  7. 9.7Automatic code generation
  8. 9.8Testing of monitors
  9. 9.9Configuration management
  10. 9.10Lab: monitor on an AURIX microcontroller
  1. 10.1Event data recorders
  2. 10.2DSSAD requirements
  3. 10.3Selection of data to record
  4. 10.4Monitor telemetry
  5. 10.5Analysis of activations
  6. 10.6Detection of new scenarios
  7. 10.7Feedback to development
  8. 10.8Privacy of recorded data
  9. 10.9Response to field incidents
  10. 10.10Practical exercise: analysis of monitor logs
  1. 11.1Monitors in ISO 26262
  2. 11.2Monitors in ISO 21448
  3. 11.3Requirements of UL 4600
  4. 11.4Safety argumentation with monitors
  5. 11.5Coverage evidence
  6. 11.6R157 requirements on DSSAD
  7. 11.7Audits and independent assessment
  8. 11.8Aviation standards as a reference
  9. 11.9Certification trends
  10. 11.10Workshop: GSN argument for monitoring
  1. 12.1Definition of the monitored system
  2. 12.2Formal specification of properties
  3. 12.3Design of perception monitors
  4. 12.4Design of planning monitors
  5. 12.5Safe-state strategy
  6. 12.6Implementation and testing
  7. 12.7Evaluation of coverage and false positives
  8. 12.8Conclusions and future work
  9. 12.9Thesis report
  10. 12.10Master's Thesis: defence before a panel
Methodology, software & labs

How you'll learn

Training is 100% online 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 the intake, so the programme can be combined with work.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is RTAMT, Breach, ROS 2, CARLA and MATLAB/Simulink, in free, academic or evaluation versions. Exercises are based on real procedures for specifying monitors in STL logic, evaluating monitors in simulation and analysing activations in fleet data. Assessment is continuous by module, plus the final Master's Thesis.

Standards covered: ISO 26262, ISO 21448, UL 4600, ISO/PAS 8800, UN ECE R157, IEEE 2846, ISO 34503, IEC 61508.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ISO 26262, ISO 21448 and UL 4600 applied to real cases, not as a theoretical annex.
Industry software:RTAMT, Breach, ROS 2, CARLA and MATLAB/Simulink, in free, academic or evaluation versions.
Master's Thesis with defence:A complete runtime monitoring project, from formal property specification to perception and planning monitors, safe-state strategy and coverage evaluation, defended before a panel.
Flexible format:100% online, no fixed timetables, compatible with full-time work.
Capstone project

Build it end to end

Your final project follows the real engineering workflow, step by step, reviewed by your tutor.

Define the monitored system
Describe the automated system, its ODD and the hazards the monitors must cover.
Specify formal properties
Write the safety properties in STL and synthesise monitors with RTAMT or Breach.
Design perception and planning monitors
Build OOD, consistency and RSS-based monitors and integrate them in ROS 2 and CARLA.
Define the safe-state strategy
Specify fallback paths, minimal risk manoeuvres and degradation logic.
Master's Thesis
Implement, test and evaluate coverage and false positives of the monitoring architecture, defended before a panel.
Career opportunities

Where this takes you

Autonomous Systems Safety EngineerRuntime Verification EngineerFunctional Safety ArchitectDiagnostics EngineerValidation EngineerFormal Methods Researcher
Admissions & scholarships

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's 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.

FAQ

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 RTAMT, Breach, ROS 2, CARLA and MATLAB/Simulink, 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 university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the programme's 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.

Master’s in Runtime Monitoring EngineeringEnrol
Scroll to Top
SEIUM – Institute of Advanced Engineering
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.