Compliance
Compliance that works in everyday practice.
The rules keep growing, not shrinking: new laws, regulations and standards. Yet companies still have to develop, deliver and make money. There is plenty of paper for all this. What’s missing are processes that actually work when it counts. That’s where I come in.
What compliance means to me
For me, compliance is not about filling binders. Processes, evidence and teams should be set up so that an obligation is met when it falls due, on Monday morning just as on Friday evening. Lean, pragmatic and without extra bureaucracy. Better safe, or rather secure, than sorry.
Focus: Cyber Resilience Act (CRA)
The Cyber Resilience Act applies to manufacturers of products with digital elements. The reporting obligations have applied since 11 September 2026: for actively exploited vulnerabilities and severe security incidents, an early warning is due within 24 hours and the notification within 72 hours, each from the time of becoming aware. The remaining obligations apply from 11 December 2027.
The starting point is the reporting drill. Together with your team, we walk through a fictitious case tailored to your product and check whether the reporting chain holds on any given day, weekends included.
- All about the CRA and the three steps
- CRA Self-Check (in German): a first assessment in your browser, nothing is stored
I support you with technology, processes and evidence. This does not include legal advice, nor the conformity assessment itself, which lies with the manufacturer or, depending on the product class, with a notified body.
Automotive SPICE: processes your team actually uses
For many automotive suppliers, Automotive SPICE compliance is a must-have customer demand. Yet improvement initiatives rarely fail because of the model. They fail because processes are written past the team’s daily work. As a practitioner, I go the other way and translate the model into lean processes people actually live: clear team roles, good templates, useful checklists. That is how I have built, introduced, and globally rolled out Automotive SPICE-compliant development processes for international system manufacturers and global automotive suppliers. My reference is the current VDA QMC process assessment model, Automotive SPICE 4.1. My goal is to help teams deliver outcomes efficiently while meeting high compliance, safety, and cybersecurity requirements.
What I do
- Gap analysis: where does your development stand against Automotive SPICE 4.1?
- Team roles, templates, and checklists tailored to your project
- Alignment with agile ways of working and related standards such as ISO 26262 and ISO/SAE 21434
- Tool support, e.g., with the Atlassian stack (Jira, Confluence)
- Coaching until the processes carry themselves
Assessment Readiness: success built on experience
An Automotive SPICE assessment is often part of the contract, and ASPICE compliance is a fundamental requirement, because your future supplier status and further business are at stake. I am an ASPICE practitioner. I prepare teams for assessments as a team member. I clarify the scope and the target capability level, find and close process gaps, structure the evidence, and prepare the team for the assessment interviews. I know what counts in an assessment, and from my own implementation work, I know what that means in a running project. Independent, certified assessors conduct the assessment itself, and I act as the interface between the assessment world and the project world. I help select and align with the lead assessors and support the assessment sessions. That is how I have prepared teams to pass capability level 2 assessments, among others, in complex projects within the VDA scope, e.g., an ASIL B customer project or autonomous driving (ASIL D). A passed ASPICE assessment gives successful teams motivation and momentum.
What you get
- Readiness check: where does the project stand, process by process?
- A prioritized action plan up to the assessment date
- Mock interviews and evidence review
- Alignment with the lead assessor and the customer, support during the sessions
- Follow-up: turning findings into real improvements
These are examples of my successful projects:
- Introduction of a maturity model, level 2 (automotive industry)
- Introduction of a maturity model, level 3 (automotive sector)
- Introduction of Automotive SPICE, maturity level 2 (automotive industry)
- Automotive SPICE assessment in the self-driving car (ASIL D), passed successfully on level 2 of Automotive SPICE
- Caching and successfully passing a formal, external Automotive SPICE assessment (level 2 maturity in the entire VDA scope) in an ASIL B customer project
We work on interim assignments.
