Hierarchical Data Model for Industrial Automation Lifecycle Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional industrial controllers use a flat namespace data structure, making it inefficient to utilize data for higher-level systems, leading to data duplication and inefficiency in network operations, and lacking detailed information on data lifecycle and deployment.
Innovation Solution
Implementing a hierarchically structured data model with a state-based control system that includes editors for creating and modifying objects with deployment and lifecycle data, along with security and bridging components to manage and transmit data across disparate networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a flat namespace data structure is used in conventional industrial controllers, then real-time control efficiency is maintained, but data utilization for higher-level systems becomes inefficient and requires data duplication
Solution Approach 1:
The patent transitions from a flat namespace data structure to a hierarchical data model with multiple dimensions (global namespace, application namespaces, object namespaces). This dimensional change allows data to be organized in layers where higher-level systems can access aggregated data while lower-level controllers maintain their flat structure for real-time control, thus resolving the contradiction between control efficiency and data adaptability.
Solution Approach 2:
The data model is segmented into multiple hierarchical levels: global namespace at the top level for enterprise-wide data, application-level namespaces for specific applications, and controller-level namespaces for individual controllers. This segmentation allows each level to operate independently with appropriate data granularity, enabling efficient real-time control at the controller level while providing structured data access for higher-level systems.
2Ease of operation
If data is copied and organized separately in each application using conventional controllers, then each application can access its required data, but data duplication occurs and network efficiency decreases
Solution Approach 1:
The patent merges data management into a unified hierarchical namespace structure where data is defined once at the appropriate level (global or application level) and then referenced by multiple applications. This eliminates the need for each application to copy and separately organize data, reducing data duplication while maintaining ease of data access through the structured namespace hierarchy.
Solution Approach 2:
The hierarchical namespace structure serves multiple functions simultaneously: it provides a global data repository, enables application-specific data views, supports data sharing across applications, and maintains data integrity. This multi-functionality allows the system to serve diverse application needs without duplicating data, improving network efficiency while maintaining operational ease.
3Device complexity
If detailed lifecycle and deployment information is not provided to controllers, then controller design remains simple, but higher-level systems must determine data lifecycle and deployment manually
Solution Approach 1:
The patent implements preliminary action by embedding lifecycle and deployment information directly into the data model structure at design time. The hierarchical namespace includes metadata about data lifecycle (creation, modification, deletion) and deployment characteristics, which are predetermined and automatically available to higher-level systems. This eliminates the need for manual determination of data lifecycle and deployment, saving time while keeping controller design relatively simple.
4Adaptability or versatility
If multiple applications access data through conventional controllers, then each application can operate independently, but confusion arises and system coordination becomes difficult
Solution Approach 1:
The patent introduces a hierarchical dimension to data access where applications operate at different levels of the namespace hierarchy. Each application can access data appropriate to its level while the hierarchical structure provides automatic coordination through the global namespace. This dimensional organization maintains application independence while eliminating confusion through structured data relationships and clear ownership at each hierarchy level.
Data Source
AI summary
An editor in an industrial automation environment comprises an input component that receives modification data relating to at least one of lifecycle and deployment of an object, the object is associated with a programmable logic controller and configured in accordance with a hierarchically structured data model. An implementation component can implement the modification data with respect to the object. The editor can further comprise a security component that determines that an entity providing the data to the input component is authorized to implement the modification data.