Industrial Automation Module Autonomy Across Integrated Skids
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In industrial automation processes, integrating software modules from multiple vendors for skids is labor-intensive and difficult to modify without affecting the integrity of the entire automation process, as existing solutions require extensive time and effort to manage and update individual control device files across multiple skids.
Innovation Solution
The system allows for rendering separate software modules corresponding to hardware component blocks as single navigable units, enabling vendors to efficiently update and debug their specific modules while maintaining autonomy, and allows downstream users to modify individual modules without compromising the integrity of the remaining software modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate software modules for each skid are maintained in individual automation control device files, then vendor autonomy and modular updates are improved, but integration complexity and modification difficulty increase
Solution Approach 1:
The patent introduces a master automation control device file that acts as an intermediary, containing references to multiple vendor-specific automation control device files. This master file coordinates the integrated skids while allowing each vendor to maintain autonomy over their own files, thus reducing integration complexity without sacrificing vendor independence.
Solution Approach 2:
The system segments the automation control into a hierarchical structure where the master file divides the overall process into discrete skid-level modules. Each vendor's software module remains a separate, modifiable unit that can be independently updated while being coordinated through the master file's reference structure.
2Device complexity
If a single custom automation control device file encompasses the totality of the industrial automation process, then integration is simplified, but modification time and labor increase significantly
Solution Approach 1:
The patent divides the single custom automation control device file into multiple vendor-specific automation control device files, each representing a discrete skid. This segmentation allows the master file to maintain simplified integration while enabling rapid modification of individual vendor modules without affecting the entire system, thus reducing modification time significantly.
Solution Approach 2:
The patent extracts individual vendor software modules from a monolithic automation control file into separate, standalone files. This extraction enables vendors to modify their specific modules independently and quickly, while the master file maintains the overall integration structure, thereby reducing the time and labor required for system-wide modifications.
3Adaptability or versatility
If multiple vendors supply skids with their own software modules, then system versatility and functionality improve, but difficulty to modify individual modules while maintaining integrity increases
Solution Approach 1:
The master automation control device file serves as a mediator that coordinates modifications across multiple vendor-specific files. When a modification is needed, the master file manages the changes while ensuring integrity across all integrated skids, thus maintaining ease of operation without compromising system functionality or vendor autonomy.
Solution Approach 2:
The system dynamically adjusts the level of integration based on modification needs. During normal operation, the master file provides unified coordination, but during modification phases, individual vendor modules can be independently accessed and updated, making the system adaptable to different operational states and improving modification ease.
Data Source
AI summary
The present disclosure is directed to systems, methods and devices for maintaining automated process module autonomy across integrated design environments. An indication to render a plurality of software modules for an automated industrial process into a module that is navigable as a singular unit may be received. The plurality of software modules may be rendered as a single module that is navigable as a singular unit. A modification to a first one of the plurality of software modules that affects at least a second one of the plurality of software modules may be received. A request to remove the second one of the plurality of software modules from the single module may be received, and the second one of the plurality of software modules may be removed from the single module.