The SAVI virtual integration process (VIP) is based on the core idea that models rather than paper documents should lead the engineering effort in developing today’s complex systems.
Architecture to ensure consistency among models is the key VIP element.
Models from multiple design teams contain multiple interdependent properties.
Multiple truth As-Is today.
- Each design team identifies multiple ways of modeling (abstracting) these common properties using multiple models and tools.
- Each team abstracts properties in different ways producing consistency within each model, but inconsistency among models.
- Each team’s approach to modeling common properties may not be equivalent
Multiple truths result from the approach. i.e. outcomes that are true within their own environment, but differ from those in other environments.
Single Truth with SAVI
The “single truth architectural model” uses SysML and AADL to structure a system and to provide system-wide analysis capability before physical integration begins. The approach ensures that all shared properties are true within all environments. i.e. a single truth.
As the system evolves, effects of changes are quantifiably tracked with iterative consistency checking. This process is very different from current development practices which rely on interface control documents.
Data Exchange Layer facilitates required data flow.
Enabling this distinctly different kind of integration requires a data flow that cuts across engineering disciplines and promotes communication between them. The SAVI MR/DEL structure is being built around ISO 10303-239 (Product Life Cycle Support) to ensure that this data flow is unimpeded throughout the development cycle.
The entire workbench of SAVI-compliant tools (to be described shortly) is meant to conform to this data exchange standard. Some of these tools are also designed to allow internal protection of intellectual property during development activities.