Building a production-grade ISO 15118 software foundation for Microchip Technology
Services
Technologies
Challenge and business need

The shift to electric mobility depends on charging infrastructure that is not only fast, but interoperable and secure. ISO 15118 is key to that: it standardises how an electric vehicle (EV) and a charging station communicate, and it underpins capabilities such as secure, certificate-based charging sessions.
For a silicon and platform vendor, great hardware is only half the equation. Customers building EV charging products also need a software layer they can trust – one that turns a long, security-critical standard into working, maintainable code.
Microchip wanted a single ISO 15118 baseline it could stand behind. It had to work across product variants, meet the security and compliance demands of the EV charging ecosystem, and cut the integration effort for customers adopting Microchip platforms. In short: less time to market for Microchip’s EV charging customers, and less technical risk in getting a complex, safety- and security-relevant protocol right.
Our responsibilities
We delivered four connected workstreams, each aimed at making the baseline dependable enough to build products on.
- Protocol and integration. We implemented the ISO 15118-2 communication flows on the supply equipment communication controller (SECC) side – the charging station. That covers message handling, session and state management, and error handling. We then validated the alternating current (AC) and direct current (DC) charging-session paths against a reference vehicle-side implementation, so interoperability is proven rather than assumed.
- Security enablement. Secure communication sits at the heart of ISO 15118. The library integrates with the TLS layer and crypto stack, and supports the certificate-handling flows that a trusted charging session depends on.
- Architecture and portability. To make the baseline reusable rather than a one-off, it’s built modular, with protocol logic cleanly separated from the platform-dependent layers. A dedicated platform abstraction layer means porting to a new environment or product variant is a contained job, not a rewrite.
- Quality and validation. The code ships with automated unit, integration, and regression tests, plus logging, tracing, and diagnostic utilities. That makes the baseline easier to debug, support, and extend – and gives Microchip and its customers evidence that the software behaves as intended.
The result
Microchip has a maintainable ISO 15118-2 foundation it can reuse as an SDK or reference solution across its portfolio – not a single-project deliverable.
For Microchip’s EV charging customers, that shortens the path from platform selection to a working product. The security groundwork is already done: TLS integration and certificate-handling flows are in place, ready for a customer’s own production PKI and certificate provisioning.
The modular architecture, test coverage, and diagnostics also lower integration risk and leave room to grow. New ISO 15118-2 features and customer-specific requirements go on top of a documented base, rather than into it.
arrow_circle_rightCONTACT US