Application Containers for Portable Automation Control Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automation control systems face challenges in achieving portability and efficient deployment across multiple operating systems due to complex software stacks, cumbersome integration processes, and runtime misbehaviors caused by unfulfilled dependencies and configuration conflicts.
Innovation Solution
A supervisory device with independent application containers that include a guest operating system integrated during development, allowing for a one-time system integration, enabling deployment across different host operating systems without requiring additional configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a monolithic software stack is integrated into a designated operating system, then the system achieves functional completeness, but any modification to subcomponents requires complete re-integration of all interdependencies
Solution Approach 1:
The software stack is divided into independent, loosely-coupled modules that can be modified separately. Each module is encapsulated with clearly defined interfaces, allowing individual subcomponents to be updated without requiring complete re-integration of the entire system.
Solution Approach 2:
Integration templates and dependency management frameworks are prepared in advance during the module design phase. This preliminary setup establishes the integration structure and interdependency relationships before actual modifications occur, enabling rapid re-integration when changes are needed.
2Reliability
If automation software stack is customized for each target operating system, then system compatibility is ensured, but portability across different operating systems is reduced
Solution Approach 1:
The software architecture is designed with universal integration templates that can adapt to multiple operating systems. The modular design with standardized interfaces allows the same software stack to be deployed across different target operating systems without requiring extensive customization for each platform.
Solution Approach 2:
The integration templates utilize configurable parameters that can be adjusted based on the target operating system. By changing these parameters rather than the core architecture, the software maintains compatibility with different OS while preserving portability through a unified codebase.
3Reliability
If system integration is performed manually for each target device, then configuration accuracy can be verified, but integration time and complexity increase significantly
Solution Approach 1:
Integration templates define the correct configuration and dependency relationships in advance during the development phase. This preliminary configuration setup ensures accuracy is built-in from the start, eliminating the need for time-consuming manual verification and adjustment during deployment.
Solution Approach 2:
The modular architecture with automated dependency management enables the system to self-configure during deployment. The integration framework automatically resolves dependencies and configures components based on the predefined templates, reducing manual intervention while maintaining configuration accuracy through automated validation.
4Adaptability or versatility
If modularization is implemented with cross-module interactions through designed interfaces, then system adaptability improves, but integration complexity during initial deployment increases
Solution Approach 1:
The interface designs and integration templates for modular components are prepared in advance during the development phase. This preliminary work establishes the interaction protocols and dependency relationships between modules before deployment, reducing the complexity of initial system integration despite the modular architecture.
Data Source
AI summary
A system and method for supervisory and control support in an industrial automation system, including a supervisory device with a software stack having a host operating system and a plurality of independent application containers Each container includes a modular application platform being associated with a base functionality for the supervisory device and a guest operating system layer integrated with the modular application platform according to a system integration. A one-time integration of system dependencies is executed during development of the container. The independent application containers are portable for direct deployment in an operating system of a type different than that of the host operating system and can run unchanged without requiring any change to component artifacts.