Global Data Model for Application Integration Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In power utilities, inconsistencies in data across different local applications and IT systems are challenging to resolve due to insufficient coordination and automation of work processes, leading to complex navigation, synchronization, and high maintenance efforts, especially in large utilities with millions of assets.
Innovation Solution
A method that utilizes a global data model with reference containers to maintain data consistency by continuously monitoring local applications for changes and performing synchronization only upon specific triggering events, reducing the number of synchronization actions and computational efforts, and ensuring access through Application Program Interfaces (APIs) to avoid direct database access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If direct synchronization of all databases is implemented to maintain data consistency, then data consistency is improved, but computational cost and system complexity increase significantly
Solution Approach 1:
The patent segments the monolithic database synchronization problem into smaller, manageable units by introducing a global data model that represents only the essential integrated objects and their relationships. This global model acts as a simplified abstraction layer that segments the complexity away from the underlying diverse local databases, allowing consistency to be maintained through targeted updates rather than full database synchronization.
Solution Approach 2:
The global data model serves as an intermediary between local applications and the integrated system. It provides a unified view of integrated objects without requiring direct access to or synchronization of all local databases. The global model mediates data access and consistency maintenance, reducing the complexity of coordinating changes across multiple database systems.
2Reliability
If continuous monitoring of all local applications is performed to detect changes, then data consistency is maintained, but processing time and computational resources increase
Solution Approach 1:
Instead of continuous monitoring, the system uses event-driven periodic action where change detection is triggered only when specific events occur (such as data modifications in local applications). This approach transforms continuous monitoring into discrete, periodic checks triggered by meaningful events, reducing unnecessary processing while maintaining consistency.
Solution Approach 2:
Local applications autonomously notify the global data model when changes occur in their data sets. This self-service mechanism eliminates the need for centralized continuous monitoring, as each application independently detects and reports its own changes, reducing the computational burden on the central system.
3Reliability
If all databases are synchronized upon any change to maintain consistency, then data integrity is improved, but productivity and response time deteriorate due to frequent full synchronizations
Solution Approach 1:
The patent applies local quality by synchronizing only the specific portions of the global data model that are affected by changes in local applications, rather than performing full database synchronization. This targeted approach maintains data integrity for affected objects while preserving productivity by avoiding unnecessary synchronization of unrelated data.
Solution Approach 2:
The system performs partial synchronization actions, updating only the necessary subset of the global data model that corresponds to changed local data. This partial action approach is sufficient to maintain integrity for affected objects while being more efficient than complete synchronization, avoiding the excessive overhead of full database updates.
4Reliability
If redundant components are deployed to handle hardware or software failures, then system reliability is improved, but systematic errors cannot be resolved and maintenance complexity increases
Solution Approach 1:
The system implements feedback mechanisms where local applications notify the global data model of changes and status. This feedback loop enables the system to detect and respond to failures systematically, allowing the global model to maintain consistency even when individual components fail, without requiring complex redundant architectures.
Data Source
AI summary
The present disclosure facilitates the interoperability between different local applications. Related local data objects are referenced via global objects or reference containers within a global data model or a global address space of an integration solution. The present disclosure assumes that the integration solution is per default in a consistent state, e.g., an engineered or initially configured global address space is regarded as consistent, and all software components that operate within this space assume that the information they access is valid and likewise consistent. The local applications are the only components that can interact with the global address space and introduce invalidations, they are continuously monitored for changes. Invalidation and subsequent synchronization or restoration of consistency is performed upon a particular triggering event related to a change in a local application object (such as an insertion or removal of an object or a modification of an attribute thereof) or related to a changing application or adapter status (component shutdown/startup).