MBSE Configuration Management via Baseline Working Partitioning

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current configuration management tools for model-based systems engineering (MBSE) face challenges such as high server bandwidth demands, merge failures, and limited change control capabilities, particularly with branching and merging techniques, which can lead to errors and inefficiencies in managing changes across large, complex projects.

Innovation Solution

The solution involves partitioning a system project into a baseline portion under strict change control and a working portion, generating a change package, performing an impact analysis to identify directly and indirectly impacted elements, and integrating changes into the baseline model while maintaining a unidirectional relationship to avoid conflicts and optimize change management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If branching and merging techniques are used for configuration management, then users can work on separate copies of the project, but server bandwidth demands and hardware requirements increase significantly

Engineering Contradiction:

Improvechange control capabilityVSAvoidserver bandwidth demand

Core Design Contradiction:

Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The system segments the project model into baseline elements and working elements, allowing concurrent access without full branching. Users can work on working elements while the baseline remains stable, reducing the need to replicate entire project copies across servers.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism that manages changes between working elements and baseline elements. This intermediary layer coordinates updates and resolves conflicts without requiring full project replication, thereby reducing server bandwidth consumption.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Ease of operation

If branching and merging techniques are used, then users can edit project copies independently, but merge failures and conflicts increase

Engineering Contradiction:

Improveindependent editing capabilityVSAvoidmerge success rate

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing a unidirectional relationship from baseline to working elements before editing occurs. This pre-configured structure guides the integration process and reduces the likelihood of merge conflicts by anticipating dependency relationships.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms that track changes from working elements back to the baseline. This feedback loop enables automatic detection and resolution of conflicts, improving merge reliability without sacrificing independent editing capabilities.

Inventive Principle:

Principle #23Feedback

3Reliability

If locking impacted elements is used to prevent conflicts, then change control is strengthened, but user coordination capability is severely limited

Engineering Contradiction:

Improvechange controlVSAvoidsimultaneous user collaboration

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The system dynamically manages element accessibility based on their role in the change process. Baseline elements remain stable while working elements are freely editable. This dynamic approach provides strong change control for baseline elements while allowing simultaneous collaboration on working elements.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

By segmenting elements into baseline and working categories, the system allows multiple users to simultaneously edit working elements without locking conflicts, while maintaining strict control over baseline elements through the unidirectional relationship mechanism.

Inventive Principle:

Principle #1Segmentation

4Loss of information

If manual resyncing of branches is performed, then trunk changes can be reflected in branches, but the process is time-consuming and error-prone

Engineering Contradiction:

Improvechange propagationVSAvoidresync time

Core Design Contradiction:

Loss of informationVSLoss of time

Solution Approach 1:

The patent establishes a continuous unidirectional relationship from baseline to working elements that automatically propagates changes. This eliminates the need for manual resyncing operations, as the system continuously maintains consistency without user intervention, saving time and reducing errors.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS11521152B2Configuration management for model-based systems engineering

Publication Date: 2022.12.06 THE BOEING CO

AI summary

Solutions are provided for configuration management for model-based systems engineering (MBSE). An example includes: partitioning a system project into a baseline portion and a working portion; generating, in the working portion, a change package; generating, for the change package, an impact analysis, wherein generating the impact analysis comprises: based at least on change information, determining directly impacted elements; and based at least on the directly impacted elements, determining indirectly impacted elements; importing, from a baseline model into the change package, the directly impacted elements and the indirectly impacted elements; modifying at least one imported directly impacted element to generate a modified element; and integrating the modified element into the baseline model. Some examples further include generating a relation map indicating relationships among the directly impacted elements and the indirectly impacted elements to assist the impact analysis.