Plant Semantic Model Linking Multi-Domain Asset Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current engineering infrastructure for industrial plants lacks a consistent model across different engineering domains, leading to duplicated data, high engineering costs, and inefficient cross-domain interactions, as each domain relies on dedicated standards and models.
Innovation Solution
A semantic model is created by retrieving and linking asset identifiers and relationships across different engineering domains, allowing for a unified asset-centric view that reduces duplication and enables seamless information sharing through dedicated applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If dedicated models and tools are used for each engineering domain, then domain-specific engineering precision is improved, but data duplication and engineering cost increase
Solution Approach 1:
The patent merges multiple domain-specific models (mechanical, process, electrical, instrumentation) into a single unified plant-wide model using a common data structure and namespace. This allows assets to be represented once with consistent identifiers while enabling access from multiple engineering domains, thereby eliminating data duplication and reducing engineering costs while maintaining domain-specific precision through the unified model's comprehensive structure.
Solution Approach 2:
The unified model implements universality by creating a single asset representation that serves multiple engineering domains simultaneously. Each asset is defined once with a universal identifier and can be accessed and utilized by mechanical, process, electrical, and instrumentation disciplines without requiring separate domain-specific instances, thus reducing redundancy while maintaining specialized engineering capabilities.
2Reliability
If domain-specific standards and data models are used, then domain expertise and reliability are improved, but cross-domain information sharing deteriorates
Solution Approach 1:
The unified model acts as an intermediary layer between domain-specific engineering disciplines. It provides a common namespace and data structure that translates and connects assets across mechanical, process, electrical, and instrumentation domains, enabling seamless information sharing while preserving domain-specific expertise through the standardized interface.
Solution Approach 2:
The universal asset model enables cross-domain information sharing by providing a single source of truth that all engineering disciplines can access. Each domain maintains its specialized knowledge and standards while the unified model ensures consistent asset identification and relationships across domains, preventing information loss and enabling efficient collaboration.
3Adaptability or versatility
If multiple import/export operations are performed between domains, then domain-specific requirements are met, but engineering time and productivity are reduced
Solution Approach 1:
The patent combines multiple domain-specific data models into a single unified model that eliminates the need for repeated import/export operations. Assets are defined once in the unified model and can be accessed by all engineering domains simultaneously, thereby eliminating redundant data transfer operations and significantly reducing engineering time while maintaining adaptability to domain-specific requirements.
Data Source
AI summary
For providing a set of services relating to a semantic model of an infrastructure including assets belonging to different engineering domains, an application server: retrieves, for each engineering domain, asset identifiers respectively associated with assets of the engineering domain and with sets of attributes and for determining asset relationships between the asset identifiers; builds, for each engineering domain, an engineering domain model including assets identifiers that are linked between them based on the asset relationships; determines at least one asset identifier that belongs or is connected to at least two different engineering domain models and linking the at least two different engineering domain models via the at least one asset identifier to build a semantic model of the infrastructure; and provides a set of services for the semantic model of the infrastructure, the services using sets of attributes associated with asset identifiers that belong to different engineering domain models.