Reference Model Requirement Orchestration in Digital Twin Development
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for developing complex technical systems face difficulties in efficiently forwarding and comparing specifications or requirements from pre-existing reference models, leading to high effort and understanding issues between senders and receivers, especially in identifying synergies between different specifications.
Innovation Solution
A method and tool for reference model-based, requirement-based development that automatically ascertains and forwards suitable specifications or requirements by accessing a digital twin, using user-based data and logic-based processing to orchestrate access to the reference model requirements, dividing the process into three orchestration phases for relevance assessment and extraction.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If text-based specifications or requirements are created and forwarded manually, then the process can be completed, but the effort for the creator and receiver is high and understanding problems occur
Solution Approach 1:
The patent replaces manual text-based specification creation and comparison with an automated computer-based system. The system automatically extracts requirements from reference models, processes them through logic-based orchestration, and generates standardized requirement specifications, eliminating the manual mechanical process of writing and comparing text documents.
Solution Approach 2:
The system enables self-service by automatically generating requirement specifications without human intervention in the extraction and initial processing stages. The automated orchestration logic independently assesses relevance, extracts appropriate requirements, and formats them according to standards, allowing the system to serve itself rather than requiring continuous human management.
2Reliability
If multiple specifications or requirements are obtained from different senders, then comprehensive requirements can be gathered, but identifying synergies between them becomes difficult and effort-intensive
Solution Approach 1:
The patent merges multiple requirements from different reference models and senders into a unified standardized format. The system consolidates requirements through common data structures and orchestration logic, combining disparate specifications into a coherent set that can be systematically analyzed for synergies and conflicts.
Solution Approach 2:
The system transforms requirements by changing their parameter representation from diverse text-based formats to standardized structured parameters. This parameter transformation enables automated comparison and synergy identification by expressing all requirements in terms of comparable attributes and metrics.
3Productivity
If pre-existing reference models are used to develop technical systems, then development can be accelerated, but automatically selecting and forwarding appropriate specifications is difficult
Solution Approach 1:
The system implements feedback mechanisms where the orchestration logic continuously assesses the relevance of extracted requirements against the target system context. The system receives feedback about which requirements are appropriate and adjusts the extraction and selection process accordingly, enabling automated adaptation to different development scenarios.
Solution Approach 2:
The patent applies preliminary action by pre-processing and structuring requirements from reference models before they are needed for actual system development. The system performs advance extraction, validation, and organization of requirements from reference models, so that when development needs arise, pre-processed requirements are readily available for automated selection and integration.
Data Source
AI summary
A method, computer program product and modelling tool for a reference model requirement based development of a technical system is ascertained, (i) in a first orchestration phase, to ascertain a storage location in the digital twin for the suitable reference model requirement, (ii) in a second orchestration phase, to ascertain a relevance of the reference model requirement belonging to the storage location and relevant to the forwarding from different perspectives for the development of the technical system, and (iii) in a third orchestration phase, to extract the reference model requirement from the ascertained relevance.