CSDM december 2022 Digital thread
Presenters
Introduction
In this introduction we will present the goal of the Digital Thread .
We will present our referential of design which organized into a pradigm of :
- RFLP (Requirements, Functional, Logical, Physical) for systems modelling.
- MSR (Model, Scenario, Results) to support V+R simulation.
Note that it is possible to use several languages like SysML UML UAF RFLP to create the models through this RFLP paradigm.
White Belt : Unified Data Management
Collaborative Designer for CATIA Magic CATIA Magic Power'by Unified Data Management
To ease the collaboration between teams, a first system federation step (white belt) would consist into giving access to data sources in a given version, from which the documents have been generated. This requires also to identify which data is validated from the ones that are in progress
Yellow Belt : Traceability
Systems traceability Analyst traceability Compliancy
The second step (yellow belt) is to federate the traceability in an authoritative single source of truth: capture the traceability links where it exists, give to possibility to create it where it is needed.
Getting this authoritative single source of truth enables:
- To create traceability between data from their source (databases, files in versioned repositories), without any data duplication
- To collaborate on digital models managed in configuration
- To facilitate the change process through impact analysis
- To support the certification process by providing evidences
Brown Belt : Modelling & Simulation
IVVQ (Integration, Verification, Validation, Qualification)
Collaborative Designer for CATIA SCANeR ModSim
Systems software Production Engineer Code Generation
More than 12 years ago, the Object Management Group (OMG) and the International Council on Systems Engineering (INCOSE) began working on a new way – a standard way- of implementing systems engineering. This approach involved visual models, built on a standard modeling language (e.g. UAF, SysML), to support the development of requirements, behavioral and functional analysis, and structural design through conceptual, logical, and later phases of the system life cycle. INCOSE has stated that Model-Based Systems Engineering IS the Systems engineering of the future. Most of the organization who have applied Model Based Systems Engineering have developed descriptive models.
Gaining in efficiency requires using a modeling and simulation approach, like in mechanical design in the last 30 years. This virtual twin system accelerates holistic understanding, optimal decision-making, and effective action through dynamic behavior understanding.
Black Belt : Process Governance
Data science experience Dashboarding
Systems Engineering to govern discipline desgin
The development of a system involves an eco-system with various disciplines interacting together.
For an automotive project, it is about 1.000 people distributed in 40 different disciplines. For an aircraft project, we are talking about 10.000 people involved.
As a matter of facts, those people are producing deliverables during the project lifecycle that need to remain consistent each other.
These deliverables are produced by different teams, working with different tools, within different scopes of responsibilities (system scope, design scope, component scope), with requirements and interfaces defined at each level.
Organizing the consistency through a unified configuration and change management is mandatory to achieve the system development.
Of course all of the tools have their own way to manage configuration / versioning. Federating governance on an authoritative single source of truth is a key factor for success.
This is seen as a black Belt for the reason that those topic are very complex to manage. Moreover, it is considered as a second priority in systems engineering process, methods and tools. As you can see in the figures below, models and design do have a lifecycle with evolution that comes from various origin. In each cases, the system architect should be the orchestrator of the impact analysis of those changes. By the way, he needs to be able to track the evolution status according to the request.
Conclusion
Paper :
Presentation
