Controller Allocation in Industrial IDEs for Decoupled Program Reuse
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing control program development platforms require binding industrial control programs to a specific industrial controller at the outset, limiting flexibility and scalability, especially when the hardware implementation is yet to be determined.
Innovation Solution
An industrial integrated development environment (IDE) system that allows industrial control programs to be defined and stored as smart objects without initial binding to a specific controller, enabling decoupled development and subsequent assignment to multiple controllers, supporting a one-to-many relationship.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If industrial control programs are bound to a specific controller at the outset, then the control project structure is simplified and the controller is clearly defined, but the flexibility and scalability are limited when hardware implementation is yet to be determined
Solution Approach 1:
The system segments the control program from the controller definition by introducing an intermediate binding mechanism. The control program is first created as a standalone entity, then selectively bound to controller definitions through a many-to-many relationship model, allowing independent development and flexible assignment later
Solution Approach 2:
The control program binding mechanism is designed to be universal, supporting one-to-one, one-to-many, and many-to-one relationships between control programs and controller definitions. This multi-functional binding system allows the same control program to serve multiple controllers or be shared across different projects
2Adaptability or versatility
If industrial control programs are bound to a specific controller at the outset, then the control project is clearly structured, but the scalability to multiple controllers is limited
Solution Approach 1:
The system enables copying and reusing control programs across multiple controller definitions without requiring redevelopment. A control program created once can be bound to multiple controllers, and changes to the original control program automatically update all bound instances, eliminating redundant development work
Solution Approach 2:
The control program is developed and validated in advance without being tied to a specific controller. This preliminary development phase allows the control logic to be finalized and tested independently, then quickly deployed to multiple controllers when hardware decisions are made
3Adaptability or versatility
If a one-to-one relationship is enforced between control project and controller, then the project structure is simple and clear, but the ability to reuse control functionality across different automation systems is reduced
Solution Approach 1:
The binding relationship between control programs and controller definitions is made dynamic rather than static. The system allows the binding configuration to change over time, supporting different relationship models (one-to-one, one-to-many, many-to-one) based on project requirements, enabling flexible reuse scenarios
Data Source
AI summary
An industrial integrated development environment (IDE) supports decoupled development of industrial control programs without requiring the programs to be initially bound to a specific industrial controller. The IDE system allows industrial control programs to be defined as smart objects within an industrial control project. These smart objects can be created without an initial binding to an industrial controller, and can subsequently be assigned to selected industrial controllers after development of the control programs is complete, or while program development is in progress. A smart object can be reused and deployed to multiple industrial controllers, providing a simple means to implement common control functionality on multiple different automation systems. To allow for deployment of smart objects to selected controllers, the IDE system supports creation of a control project having a one-to-many relationship with industrial controllers, such that multiple controllers can be defined within a single project.