Shared meaning for system, subsystem, function, interface
Modern product development increasingly requires collaboration across traditionally separate engineering domains such as mechanics, electronics, and software. Complex systems are developed using many specialised tools, models, and standards, often with inconsistent terminology and overlapping concept definitions. In automotive and other high-complexity industries, this creates major integration challenges: different teams may use the same terms differently, or different terms for the same underlying concept, leading to misalignment in system interfaces, requirements, and lifecycle traceability.
The SDR challenge concerns semantic consistency in system design across domains. Effective engineering collaboration requires shared meaning for core concepts such as system, subsystem, function, interface, configuration, and lifecycle state. Without explicit semantic alignment, interoperability between engineering tools and models becomes brittle, and future AI-supported engineering workflows (e.g. automated reasoning or design assistants) risk being grounded in inconsistent or conflicting semantics.
How does Semantic Data Readiness support consistent interpretation and interoperability across engineering domains in complex system development?
Explicit shared semantics for engineering concepts significantly improves cross-domain integration, reduces ambiguity in system models, and enables more scalable AI-supported engineering processes.
Representative engineering design scenarios will be modelled using controlled datasets and semantic structures reflecting different SDR maturity levels. Experiments will explore how semantic alignment impacts integration between domain models, traceability of design decisions, and interpretability of shared system information. Benchmark scenarios may include interface consistency checks, mapping of standard terminology, and semantic linking across toolchains.
The case enables practical exploration of how semantic alignment can be improved across real engineering organisations, tool environments, and development processes. The focus is on identifying feasible entry points where semantic clarification delivers immediate value, while also supporting long-term interoperability and lifecycle consistency.
Connects to automated design and platform-based development (UC008), distributed ontology governance (UC009), and long-lifecycle system coordination (UC006).