SDV Guide
digital.auto
  • Welcome
  • SDV101
    • Part A: Essentials
      • Smart Phone? No: Habitat on Wheels!
      • Basics: What is a Software-defined Vehicle
      • MHP: Expert Opinion
      • Challenges: What sets automotive software development apart?
      • SDV Domains and Two-Speed Delivery
    • Part B: Lessons Learned
      • Learnings from the Internet Folks
        • Innovation Management
        • Cloud Native Principles
          • DevOps and Continuous Delivery
          • Loose Coupling
            • Microservices & APIs
            • Containerization
            • Building Robust and Resilient Systems
      • Learnings from the Smart Phone Folks
    • Part C: Building Blocks
      • Foundation: E/E Architecture
        • Today`s E/E Architectures
        • Evolving Trends in E/E Architectur
        • Case Study: Rivian
      • Standards for Software-Defined Vehicles and E/E Architectures
      • Building Blocks of an SDV
        • Service-Oriented Architecture
          • The SOA Framework for SDVs
          • Container Runtimes
          • Vehicle APIs
          • Example: Real-World Application of SDV Concepts
          • Ensuring Functional Safety
          • Event Chains in Vehicle SOAs
          • Vehicle SOA Tech Stack
        • Over-the-Air Updates: The Backbone of Software-Defined Vehicles
        • Vehicle App Store: The Holy Grail of Software-Defined Vehicles
      • Summary: Building Blocks for Software-Defined Vehicles
    • Part D: Implementation Strategies
      • #DigitalFirst
      • Hardware vs Software Engineering
        • The Traditional V-Model in Automotive Development
        • Agile V-Model, anybody?
        • Key: Loosely Coupled, Automated Development Pipelines
        • The SDV Software Factory
      • Implementing the Shift Left
        • Simulation and Digital Prototyping
          • Early Validation: Cloud-based SDV Prototyping
          • Detailed Validation: SDVs and Simulation
        • Towards the Virtual Vehicle
          • Case Study: Multi-Supplier Collaboration on Virtual Platform
          • Long-Term Vision
        • Physical test system
        • De-Coupled, Multi-Speed System Evolution
        • Continuous Homologation
        • Summary and Outlook
      • Enterprise Topics
        • Variant Management
        • Engineering Intelligence
        • Enterprise Organization, Processes, and Architecture
        • Incumbent OEMs vs EV Start-ups
  • SDV201
  • ./pulse
    • SDV Culture
    • Lean Sourcing
      • LeanRM
        • Why so many Requirements?
      • SCM for SDVs
    • SDV Systems Engineering
      • LeanSE
      • SDVxMBSE
    • Digital First
    • Loose Coupling
      • API-first
      • Freeze Points
    • Automation and Engineering Intelligence
    • Continuous Homologation
    • Build / Measure / Learn
  • Glossary
Powered by GitBook

SDV Guide

  • Legal Notice
  • Disclaimer
  • Privacy Policy

(c) 2025 Dirk Slama

On this page
  • Incumbent OEMs
  • EV Start-ups
  • Engineering Intelligence: Dealing with Heterogeneity and Redundancy
  • Outlook: Product Line Engineering and Type-Based Product Line Engineering (TLPE)
  1. SDV101
  2. Part D: Implementation Strategies
  3. Enterprise Topics

Engineering Intelligence

PreviousVariant ManagementNextEnterprise Organization, Processes, and Architecture

Last updated 6 months ago

Engineering Intelligence brings together all relevant data from engineering sub-systems, such as PLM, MES, and CI/CD systems, by leveraging modern approaches like a data mesh. By connecting this data and applying Generative AI (GenAI), engineering processes, as well as manufacturing and aftermarket operations, can be optimized. Engineering Intelligence addresses the need for consistency, efficiency, and actionable insights across increasingly complex systems.

Incumbent OEMs

Incumbent OEMs face unique challenges due to their highly complex product portfolios and organically grown, heterogeneous toolchains. Their systems span across multiple repositories, connecting requirements management, PLM, MES, CI/CD, ERP, CRM, and sales systems (as shown in the first image). While this setup has evolved over time to support specific needs, it introduces redundancy, inconsistency, and complexity across the engineering lifecycle. Managing this complexity is particularly challenging when dealing with the scale of variants seen in incumbent OEMs’ portfolios.

EV Start-ups

In contrast, EV start-ups operate with leaner product portfolios and much more stringent variant policies. They prioritize simplicity and standardization, minimizing the number of configurations and focusing on software-driven differentiation. Start-ups are often referred to as single-repo companies, where all engineering-related artifacts are managed within a single repository per domain (as shown in the second image). While they still maintain multiple repositories in practice, the stringent discipline of "one repo per domain" brings significant benefits, including reduced complexity, improved data consistency, and a single point of truth.

Engineering Intelligence: Dealing with Heterogeneity and Redundancy

Engineering Intelligence must address the heterogeneity and redundancy inherent in complex engineering systems, particularly for incumbent OEMs. By leveraging a data mesh, data from disparate systems can be connected and made accessible across the organization, breaking down silos. Additionally, Generative AI can analyze this data to provide insights, automate routine tasks, and optimize engineering workflows. This allows companies to manage complexity, streamline processes, and ensure consistency across systems, from design to production and aftermarket support.

In summary, Engineering Intelligence, powered by data mesh and GenAI, is key to overcoming the challenges of heterogeneity and redundancy. It enables both incumbent OEMs and EV start-ups to optimize their engineering processes, reduce complexity, and achieve greater agility in the face of growing product and system demands.

Outlook: Product Line Engineering and Type-Based Product Line Engineering (TLPE)

Product Line Engineering (PLE) is a systematic approach to managing a portfolio of related products by identifying shared assets and features while accounting for differences. This approach is particularly valuable in managing vehicle variants efficiently, as it allows manufacturers to define a core architecture and customize features for specific configurations.

An emerging evolution of PLE is Type-Based Product Line Engineering (TLPE). TLPE introduces a more structured, modular approach to managing product lines by categorizing features and assets into distinct types. This allows for better reuse, standardization, and traceability across the engineering lifecycle.

Engineering Intelligence can both empower and benefit from TLPE. By integrating data from PLE systems, Engineering Intelligence can leverage AI-driven insights to identify opportunities for standardization, optimize feature reuse, and manage complexity effectively. Conversely, TLPE enhances the value of Engineering Intelligence by providing a clear, modular structure for data analysis, ensuring consistency across product lines.

In summary, Product Line Engineering, particularly with TLPE, offers a scalable approach to managing variants. Combined with Engineering Intelligence, it enables manufacturers to achieve greater efficiency, consistency, and innovation across complex product portfolios.