Mike: Uwe, you have been instrumental in forming the new Compliance Work Group. What was the motivation for this?
Uwe: When JOYNEXT decided to become an eSync Alliance Member, we wanted to know the benefits. The opportunity to contribute to the enhancements of the eSync standard, and to implement compliant products, was somehow only the left side of the well-known V-cycle for software development. So, we discussed increasing the value of alliance membership by adding the right side to the scope of eSync, and very quickly the idea of the CWG was born.
Mike: What made you decide to take the challenge and chair the CWG?
Uwe: To be honest, that was not really a rational decision. Once we started to discuss the idea of a CWG, colleagues from the eSync and JOYNEXT teams began to identify important topics, and to create and discuss concepts for a certification bench and a certification process. I collected all that valuable input, and saw it would answer my questions about benefits - so it was an easy decision when I was asked to apply for the role.
Mike: Can you share with us your vision for the CWG?
Uwe: I would like OEMs to reduce their integration efforts to a minimum for OTA and the vehicle to cloud data pipeline functionalities, by simply specifying those functions to be eSync compliant. By specifying an eSync compliant implementation:
- Suppliers will be able to implement those functions according to a specification that can be 100% verified
- Suppliers that are eSync members will gain access to a certification bench that ensures ASPICE-compliant implementation and verification
- OEMs will get certified products with full functionality, interoperability, robustness and security of the OTA data pipeline
Mike: Would you like to highlight a particular aspect of your work as the chair of the CWG?
Uwe: What makes it most interesting is finding the right balance between the technical implementation of the test tool itself, and the development of a whole certification process. We must always change the perspective between software developers and testers from Tier1/Tier2 suppliers, and the expectations from OEMs. It is inspiring to see the participants contributing to the work results of the CWG on a weekly basis.