Postgraduate DiplomaDesign, HMI & Product Applications open

Diploma in App↔Vehicle↔Charger: Usage Flow and Telemetry

Online postgraduate diploma of 800 hours in App↔Vehicle↔Charger: Flow and Usage Telemetry. 8 modules covering the connected EV ecosystem, charging communication protocols, app-vehicle-charger flow design, usage telemetry and data architecture, charging behaviour analytics, privacy and cybersecurity, and service quality with ISO 15118-20, OCPP 2.0.1 and Regulation (EU) 2016/679 (GDPR), with an assigned technical tutor.

Duration6–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

Describe the architecture of the connected ecosystem between app, vehicle and charger.

02

Explain the ISO 15118, OCPP and OCPI protocols and their impact on the experience.

03

Design robust user flows with intermediate and error states.

04

Define telemetry plans and product event schemas.

05

Analyse usage data to detect failures and opportunities for improvement.

06

Apply GDPR privacy requirements and UNECE R155 cybersecurity requirements.

07

Plan a complete connected service with tracking metrics.

Profile

Who it's for

  • Connected services product managers
  • Mobility app UX designers
  • Product data analysts
  • IoT solutions architects
  • Charging backend engineers
  • Product privacy leads
  • Engineering or science graduates looking to move into the automotive sector
Standards & tools

What you'll work with

  • ISO 15118-20 (second-generation vehicle-to-grid communication interface)
  • OCPP 2.0.1 (Open Charge Point Protocol)
  • Regulation (EU) 2016/679 (GDPR, General Data Protection Regulation)
  • IEC 61851-1 (electric vehicle conductive charging system)
  • UNECE R155 (vehicle cybersecurity and cybersecurity management system)
  • UNECE R156 (software updates and software update management system)
  • ISO/SAE 21434 (road vehicle cybersecurity engineering)
  • OCPI 2.2.1 (Open Charge Point Interface for roaming)
  • Figma
  • Postman
  • Apache Kafka
  • Grafana
  • Amplitude
Syllabus

8 modules

  1. 1.1Actors: manufacturer, operator, mobility provider and user
  2. 1.2Telematics unit and cellular connectivity
  3. 1.3Manufacturer cloud platforms
  4. 1.4Charge point operator backends
  5. 1.5Identity and user account management
  6. 1.6Data flows between app, vehicle and charger
  7. 1.7Latency, availability and offline modes
  8. 1.8Business models for connected services
  9. 1.9Ecosystem dependency map
  10. 1.10Case study: context diagram of a remote charging service
  1. 2.1PWM communication and IEC 61851 states
  2. 2.2ISO 15118 high-level communication
  3. 2.3OCPP protocol between charger and backend
  4. 2.4OCPI protocol for roaming
  5. 2.5OpenADR and demand response
  6. 2.6MQTT messaging and REST APIs
  7. 2.7Plug & Charge contracts and certificates
  8. 2.8Interoperability and conformance testing
  9. 2.9Protocol errors and their effect on the user
  10. 2.10Lab: analysis of OCPP messages in a simulator
  1. 3.1Remote unlocking and pre-conditioning
  2. 3.2Starting and stopping charging from the app
  3. 3.3Time scheduling and state-of-charge limit
  4. 3.4Push notifications and intermediate states
  5. 3.5State synchronisation across devices
  6. 3.6Design of error states and recovery
  7. 3.7First-use flows and vehicle pairing
  8. 3.8Vehicle sharing and multiple profiles
  9. 3.9App accessibility and localisation
  10. 3.10Workshop: state diagram of a charging session
  1. 4.1CAN signals relevant to charging
  2. 4.2Sampling, aggregation and upload to the cloud
  3. 4.3Product event modelling
  4. 4.4Data pipelines and streaming ingestion
  5. 4.5Storage in a data lake and data warehouse
  6. 4.6Data quality and handling gaps
  7. 4.7Fleet data versus individual data
  8. 4.8Connectivity cost and signal prioritisation
  9. 4.9Event schema and data dictionary
  10. 4.10Practical exercise: designing the event plan for a charging app
  1. 5.1Home and public charging patterns
  2. 5.2Funnels of app feature usage
  3. 5.3Cohorts and feature retention
  4. 5.4Detecting charging failures from telemetry
  5. 5.5Segmenting drivers by habits
  6. 5.6Visualisation with dashboards
  7. 5.7Predictive models of charging demand
  8. 5.8A/B experimentation on connected features
  9. 5.9Communicating insights to product
  10. 5.10Practical exercise: charging sessions dashboard
  1. 6.1Driver personal and location data
  2. 6.2Legal bases and consent under the GDPR
  3. 6.3EDPB guidelines on connected vehicles
  4. 6.4Pseudonymisation and data minimisation
  5. 6.5Vehicle cybersecurity under UNECE R155
  6. 6.6Update management under UNECE R156
  7. 6.7API security and OAuth 2.0 authentication
  8. 6.8Cybersecurity engineering under ISO/SAE 21434
  9. 6.9Transparent communication of privacy
  10. 6.10Case study: impact assessment of a telemetry service
  1. 7.1Availability and reliability indicators
  2. 7.2Service monitoring and alerting
  3. 7.3Incident management and user support
  4. 7.4Over-the-air (OTA) feature updates
  5. 7.5API versioning and compatibility
  6. 7.6App life cycle and releases
  7. 7.7User feedback and prioritisation
  8. 7.8Operating costs of the connected service
  9. 7.9Scalability as the fleet grows
  10. 7.10Case study: analysis of a mass remote-charging failure
  1. 8.1Definition of the service and scope
  2. 8.2Map of flows between app, vehicle and charger
  3. 8.3Design of interfaces and states
  4. 8.4Telemetry and event plan
  5. 8.5Privacy and security analysis
  6. 8.6Prototype and user testing
  7. 8.7Tracking dashboard
  8. 8.8Launch and evolution plan
  9. 8.9Report and presentation
  10. 8.10Final project: final review with the tutor
Methodology, software & labs

How you'll learn

100% online programme 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 it fits around your job.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is Figma, Postman, Apache Kafka, Grafana and Amplitude, in free, academic or evaluation versions. Testing is studied on real procedures: simulating charging sessions with an OCPP backend, usability tests of the app with a real vehicle, and analysis of fleet telemetry in dashboards. Assessment is continuous by module, plus the final project.

Standards covered: ISO 15118-20, OCPP 2.0.1, Regulation (EU) 2016/679, IEC 61851-1, UNECE R155, UNECE R156, ISO/SAE 21434, OCPI 2.2.1.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ISO 15118-20, OCPP 2.0.1 and the GDPR applied to real cases, not as a theoretical annex.
Industry software:Figma, Postman, Apache Kafka, Grafana and Amplitude, in free, academic or evaluation versions.
Final project:a connected service project covering app-vehicle-charger flows, telemetry plan, privacy and security analysis and a tracking dashboard, 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.

Service definition
Define the connected service, its scope and the flows between app, vehicle and charger.
Interface and state design
Design the interfaces with their intermediate and error states.
Telemetry plan
Define the telemetry and event plan and analyse privacy and security.
Prototype and tracking
Prototype and test with users, and build the tracking dashboard.
Final project
Present the launch and evolution plan, report and presentation for review by your tutor.
Career opportunities

Where this takes you

Connected services product managerMobility app UX designerProduct data analystIoT solutions architectCharging backend engineerProduct privacy lead
Admissions & scholarships

Requirements

  • Prior technical training or professional experience in the sector. No university degree is required.
  • An internet connection and a computer able to run 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 Figma, Postman, Apache Kafka, Grafana and Amplitude, 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 App↔Vehicle↔Charger: Usage Flow and TelemetryEnrol
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.