Common Data Model Segmentation for Plant Software Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In power plants, the heterogeneous software application landscape leads to data inconsistencies across different phases and systems due to loose coupling, lack of standard data models, and inefficient data exchange mechanisms, resulting in increased engineering costs and potential for undetected inconsistencies.

Innovation Solution

A common data model (CDM) managed by a configuration data service (CDS) for shared data, combined with application-specific configuration data services (App-CDS) for single applications, ensures data consistency and efficient exchange by focusing on the intersection set of data models, allowing for flexible and autonomous operation while maintaining business logic within individual applications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a common data model is implemented across all software applications, then data consistency is improved, but device complexity and implementation difficulty increase

Engineering Contradiction:
Improvedata consistencyVSAvoiddata model complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the data model into two distinct parts: a common data model (CDM) that defines shared data structures and semantics used across multiple software applications, and application-specific data models that extend or specialize the CDM for individual application needs. This segmentation allows data consistency to be maintained through the standardized CDM while reducing overall complexity by allowing each application to only define what is specific to it, rather than redefining entire data models.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If data exchange mechanisms are enhanced across heterogeneous applications, then interoperability is improved, but loss of time and computational resources increase

Engineering Contradiction:
ImproveinteroperabilityVSAvoiddata transformation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining the common data model structure, data types, and semantic relationships before actual data exchange occurs. The CDM serves as a pre-established framework that all applications agree upon in advance, eliminating the need for runtime data transformation and interpretation. This allows heterogeneous applications to exchange data directly using the standardized CDM structures, significantly reducing data transformation time and computational overhead while maintaining high interoperability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10496053B2Method for integrated data handling for engineering and operating a plant
Publication Date: 2019.12.03 SIEMENS AG
  • US10496053B2 patent drawing
  • US10496053B2 patent drawing
  • US10496053B2 patent drawing

AI summary

Method for integrated data handling for engineering and operation of a plant having a plurality of software applications with different functionalities, wherein the plurality of software applications are interconnected via a network, a common data model including data shared between at least two of the plurality of software applications is provided, the common data model is managed by a configuration data service, data specific to a single application is managed by an application specific configuration data service that is assigned to a number of applications such that flexible, consistent, performance-optimized and efficient management of the various heterogeneous systems in the plant is achieved.