MBSE Collaboration Module for Cross-Platform Model Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing model-based systems engineering platforms face challenges in seamless communication and collaboration with other engineering domains due to incompatibility and reliance on document-based approaches, leading to inefficiencies and miscommunication.

Innovation Solution

A collaboration module for a model-based systems engineering platform that enables digital data exchange with other modeling platforms using universally unique identifiers and database identifiers, allowing for synchronized updates and sharing of project elements between systems engineers and domain-specific engineers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If document-based approaches are used for communication between engineering domains, then information can be shared, but miscommunication and inefficiency occur due to incompatibility

Engineering Contradiction:
Improveinformation accuracyVSAvoidcollaboration efficiency
Core Design Contradiction:
Loss of informationVSProductivity

Solution Approach 1:

The patent introduces a collaboration module as an intermediary system that includes a database with standardized schemas and data transformation logic. This mediator translates between different modeling platforms' data formats, ensuring accurate information exchange while maintaining high collaboration efficiency. The standardized database schema acts as a common language that eliminates miscommunication between domains.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If different modeling platforms are used by systems engineers and domain-specific engineers, then specialized expertise can be maintained, but seamless communication becomes difficult

Engineering Contradiction:
Improvedomain expertiseVSAvoidplatform compatibility
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The collaboration module implements a universal interface layer that can work with multiple different modeling platforms simultaneously. The system maintains compatibility with various platforms (e.g., SysML tools, domain-specific modeling tools) while providing a unified collaboration experience. This allows engineers to use their preferred specialized tools while seamlessly communicating with other domains through the standardized database interface.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If real-time synchronized updates are implemented across platforms, then collaboration accuracy improves, but system complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidsystem architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements a feedback mechanism where the database schema stores version information and update timestamps for each data element. When updates occur, the system automatically tracks changes and notifies relevant platforms of synchronization status. This feedback loop ensures data consistency across platforms without requiring complex manual coordination, as the system self-regulates the synchronization process through structured feedback signals.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS12493857B1Collaboration module for model-based systems engineering platform
Publication Date: 2025.12.09 THE UNITED STATES OF AMERICA AS REPRESENTED BY THE SECRETARY OF THE NAVY
  • US12493857B1 patent drawing
  • US12493857B1 patent drawing
  • US12493857B1 patent drawing

AI summary

A computer-implemented method is performed by a collaboration module of a model-based systems engineering platform. The method includes maintaining a working version of a project and importing a first element from a remote database that stores a collaborative version of the project. Importing the first element includes comparing a database identifier (DBID) of the first element to elements included in the working version of the project. If the DBID matches the DBID of an existing element in the working version, then one or more data fields of the existing element are updated. If no DBID match is found, then the working version is searched for an element having a universally unique identifier (UUID) that matches a UUID of the first element. If, however, the first element does not include a UUID, then the first element is added to the working version of the project as a new element.