Capability building: systems engineering as an organizational capability
- **Technical lead / coordination** of a cross-site SE competence network across: **requirements engineering** · **architecture & networks** · **cross functions** (e.g. diagnostics, remote update/OTA) · **function development** · **component development** - **Methods & framework development**: workshops → process/artifact building blocks → product development framework - **Continuous improvement**: framework building blocks tested, evaluated, and iteratively improved in practice ## Enablement - Built and scaled a training portfolio (overall **>500 people** trained across the portfolio and own formats) - Developed my own training: “**full-vehicle development for component owners & function owners**” (~140 slides) - Systematized lessons learned and transferred them into standards/guidelines - Contributed to a **competence management** working group (identify, describe, and deliberately develop competencies) ## Project & stakeholder management - Agile/hybrid, from feature teams to steering; decision and risk management, maturity/dependency steering - “Translator” between **technology, organization and management** - **International site coordination** (USA/China — San Francisco & Beijing), incl. synchronous alignment of maturity, findings and measures - **Large-group planning / execution**: planned sign-off drives as a “mini program” (route, variants, logistics) and executed them with up to 60 participants over 5 days - Interface management between development, QA and full-vehicle development — with a clear plan, clear roles and robust documentation ## Tooling / IT landscapes - ALM / PLM / CI/CD: introduction, integration, customizing (goal: faster, more reliable development & evidence) ## Component development (mandate) - **Capability ownership**: evolve the “component development” competency (training, lessons learned, approaches/standards) - **Project mandate (delivery)**: integration & change steering so components meet requirements in the full-vehicle context with evidence --- ## Project milestones (excerpt) ## EDAG – Systems Engineering Professionalization (Capability Building) **Role**: coordination of interdisciplinary SE competence team **Scope**: approx. **5 core people** (competencies: architecture, networks, requirements, cross functions such as diagnostics/remote update, function development, MBSE/MPSE) - Preserved, evolved, and embedded full-vehicle engineering know-how across the organization - Moderated/structured **method workshops**, derived a **product development framework** - Built and scaled a **training portfolio**; developed my own training (“full-vehicle development for component/function owners”, **~140 slides**) - Trained **>500 people** overall (portfolio incl. own training) --- ## EDAG – Systems Engineer & Project Manager (Organization + Projects) **Role**: Systems Engineer & Project Manager **Focus**: product processes, project organization, working methods (E/E & full-vehicle) + customer/project scopes - Made SE methods & traceability practical (incl. toolchain integration) - Stakeholder alignment from team level up to steering - Component development mandate: integration & change steering to meet requirements --- ## Customer (Automotive) – Agile Systems Engineering / SE Framework & ASPICE Support **Role**: Consultant Agile Systems Engineering (braking systems domain) **Period**: 10/2022 – 12/2024 - Applied corporate SE framework and adapted it to the project context - Operationalized function development - Support toward **Automotive SPICE Level 2** (process-oriented evidence) --- ## Concept project – Truck/Trailer coupling system (ASIL-D) **Role**: concept developer / decision preparation **Period**: 04/2025 – 07/2025 - Product shaping, requirements analysis, future-proof architecture - Tooling/competence analysis (A-SPICE / Safety) + project planning (WBS) --- ## Audi e-tron GT – E/E concept & series transfer (full-vehicle context) **Role**: project lead E/E concept (and subsequent series development transition) **Team / Setup** - Core team approx. **5 people**, own infotainment/connect team approx. **10 people** - Collaboration with **4 teams** total - Component responsibility for approx. **10 individual components** **Contribution** - E/E concept incl. platform analysis (reuse vs. new development) and hardware/vehicle architecture - Structured transition concept → series (decisions, interfaces, implementation logic) - **SOP achieved on schedule** (no schedule slip) --- ## Connected Car – Online services & apps **Role**: project lead **Period**: 08/2015 – 08/2017 - Online services in the vehicle and mobile apps, function development, testing, staged roll-out - Coordination between development, validation, and stakeholders --- ## Infotainment – Test management / system analysis (early years) **Role**: test manager **Period**: 2007 – 2015 (compressed summary) **Context** Securing quality and maturity of premium infotainment systems across multiple variants, releases, and international interfaces. - **International alignment** and coordination with sites in **San Francisco** and **Beijing** (incl. travel), synchronizing topics/findings, maturity, and next steps - **Test drives** conducted personally (>150,000 km over time), incl. structured documentation of findings and feedback into development/validation - **Sign-off drives planned and orchestrated**: route, vehicle variants, logistics/hotels, daily schedules - Moderated collaboration between **development departments, QA, and full-vehicle development** (OEM) - Peak scale: up to 60 participants, 5 days, across Europe (one sign-off drive)