Postgraduate DiplomaData, AI, Simulation & Analytics Applications open

Diploma in Platform MLOps: CI/CD of Models and Traceability

Online postgraduate diploma of 800 hours in platform MLOps: model CI/CD and traceability. 8 modules covering ISO/IEC 42001:2023, Regulation (EU) 2024/1689 (AI Act) and ISO/IEC 23894:2023, with MLflow, Kubeflow Pipelines, DVC and KServe, with an assigned technical tutor.

Duration800 hours · 6–8 months
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

Understand the complete life cycle of ML models.

02

Version data, code and models reproducibly.

03

Build continuous integration pipelines with ML tests.

04

Deploy models with safe, reversible strategies.

05

Ensure the traceability and lineage required by regulation.

06

Monitor and retrain models automatically.

07

Design and govern an internal MLOps platform.

Profile

Who it's for

  • MLOps engineers.
  • ML platform engineers building shared tooling for data science teams.
  • Machine learning engineers taking models to production.
  • AI architects.
  • DevOps engineers moving into ML workloads.
  • AI governance managers who need technical traceability.
  • Engineering or science graduates aiming to enter manufacturing.
Standards & tools

What you'll work with

  • ISO/IEC 42001:2023 (AI management systems)
  • Regulation (EU) 2024/1689 (Artificial Intelligence Act)
  • ISO/IEC 23894:2023 (AI risk management)
  • ISO/IEC 5338:2023 (AI system life cycle processes)
  • ISO/IEC 25059:2023 (quality model for AI systems)
  • SLSA (Supply-chain Levels for Software Artifacts)
  • NIST AI RMF 1.0 (AI risk management framework)
  • MLflow
  • Kubeflow Pipelines
  • DVC
  • KServe
  • Argo CD
Syllabus

8 modules

  1. 1.1From experiment to production
  2. 1.2Hidden technical debt in ML systems
  3. 1.3Google's MLOps maturity levels
  4. 1.4Roles: data scientist, ML engineer and platform
  5. 1.5Experiment reproducibility
  6. 1.6Components of an MLOps platform
  7. 1.7Managed versus open platforms
  8. 1.8Requirements of industrial environments
  9. 1.9Common anti-patterns in ML projects
  10. 1.10Workshop: MLOps maturity assessment
  1. 2.1Code versioning with Git
  2. 2.2Data versioning with DVC and lakeFS
  3. 2.3Experiment tracking with MLflow
  4. 2.4Model registry and stages
  5. 2.5Model metadata and signatures
  6. 2.6Reproducible environments with containers
  7. 2.7Dependency management
  8. 2.8Seeds and determinism
  9. 2.9Model cards
  10. 2.10Practical: model registry with MLflow
  1. 3.1Unit testing of ML code
  2. 3.2Data and schema tests
  3. 3.3Model behaviour tests
  4. 3.4Quality thresholds as gates
  5. 3.5Pipelines with GitHub Actions and GitLab CI
  6. 3.6Training in CI with limited resources
  7. 3.7Code and model review
  8. 3.8Static analysis and dependency security
  9. 3.9Artefacts and image signing
  10. 3.10Lab: CI pipeline with model tests
  1. 4.1Training pipelines with Kubeflow
  2. 4.2Orchestration with Argo Workflows
  3. 4.3Model serving with KServe and Seldon
  4. 4.4Batch and online inference
  5. 4.5Canary and blue-green deployments
  6. 4.6Shadow testing
  7. 4.7Automatic rollback on degradation
  8. 4.8GitOps with Argo CD
  9. 4.9GPU management and scaling
  10. 4.10Lab: canary deployment with KServe
  1. 5.1Data, code and model lineage
  2. 5.2Lineage events with OpenLineage
  3. 5.3Prediction traceability
  4. 5.4Immutable audit logs
  5. 5.5Reproducing a historical prediction
  6. 5.6Approval management
  7. 5.7Automatic model documentation
  8. 5.8Traceability required by the AI Act
  9. 5.9Evidence retention
  10. 5.10Case study: reconstructing a model's lineage
  1. 6.1Service and business metrics
  2. 6.2Data drift and concept drift
  3. 6.3Logging inputs and outputs
  4. 6.4Retraining triggers
  5. 6.5Scheduled continuous training
  6. 6.6Champion and challenger model validation
  7. 6.7Alerts and on-call
  8. 6.8Feedback with delayed labels
  9. 6.9Inference and training costs
  10. 6.10Practical: automated retraining loop
  1. 7.1Designing an internal ML platform
  2. 7.2Templates and golden paths
  3. 7.3Multi-tenancy and isolation
  4. 7.4Model and supply chain security
  5. 7.5AI risk management according to ISO/IEC 23894
  6. 7.6Approval and governance policies
  7. 7.7FinOps for ML
  8. 7.8Platform teams and team topologies
  9. 7.9Measuring productivity
  10. 7.10Workshop: designing an internal MLOps platform
  1. 8.1Use case and MLOps platform requirements
  2. 8.2MLOps platform architecture
  3. 8.3Versioning and registry
  4. 8.4CI pipeline
  5. 8.5Deployment pipeline
  6. 8.6Lineage and auditing
  7. 8.7Monitoring and retraining
  8. 8.8Evaluating the solution
  9. 8.9Report and presentation
  10. 8.10Final project: final review with the tutor
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 each intake, so the programme fits around your job.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is MLflow, Kubeflow Pipelines, DVC, KServe and Argo CD, in free, academic or evaluation versions. Practical work is based on real procedures: CI/CD pipelines with automated model tests, canary deployments with automatic rollback, and reconstructing the lineage of a prediction. Assessment is continuous by module, plus the final project.

Standards covered: ISO/IEC 42001:2023, Regulation (EU) 2024/1689 (AI Act), ISO/IEC 23894:2023, ISO/IEC 5338:2023, ISO/IEC 25059:2023, SLSA and NIST AI RMF 1.0.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ISO/IEC 42001:2023, the EU AI Act and ISO/IEC 23894:2023 applied to real cases, not as a theoretical annex.
Industry software:MLflow, Kubeflow Pipelines, DVC, KServe and Argo CD, in free, academic or evaluation versions.
Final project:an end-to-end MLOps platform for a real use case, from versioning and CI/CD to lineage, monitoring and retraining, reviewed by your tutor.
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.

Requirements and architecture
Define the use case, platform requirements and MLOps architecture.
Versioning and CI
Set up versioning, the model registry and a CI pipeline with model tests.
Deployment pipeline
Build a deployment pipeline with safe, reversible strategies.
Lineage and monitoring
Add lineage, auditing, monitoring and automated retraining.
Final project
Evaluate and present the complete solution, reviewed by your tutor.
Career opportunities

Where this takes you

MLOps engineerML platform engineerMachine learning engineerAI architectDevOps engineerAI governance manager
Admissions & scholarships

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.
  • 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 800 hours over 6–8 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.

You work with MLflow, Kubeflow Pipelines, DVC, KServe and Argo CD, 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 final project. 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 are recognised in a higher programme in the same area (postgraduate diploma or master's). Ask about the recognition policy when you enrol.

Prior technical training or professional experience in the sector (no university degree required), 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.

Diploma in Platform MLOps: CI/CD of Models and TraceabilityEnrol
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.