# US 2024/0176595 A1 · Multiple controller smart object allocation in industrial design environment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0176595 A1
- Document ID: US20240176595A1
- Status: Published application
- Kind: A1
- Application number: 18/060,090
- Filed: 2022-11-30
- Published: 2024-05-30
- Earliest claimed: 2022-11-30
- Assignees: Rockwell Automation Technologies, Inc.
- Applicants: Rockwell Automation Technologies, Inc.
- Inventors: Anthony Carrara; Lorenzo P. Majewski; Christopher E. Stanek
- Web page: https://patentgrep.com/patent/US20240176595A1

## CPC

- G05B 19/056: {Programming the PLC}
- G06F 8/34: Graphical or visual programming
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

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.

## Claims

### Claim 1

A system, comprising:
a memory that stores executable components; and
a processor, operatively coupled to the memory, that executes the executable components, the executable components comprising:
a user interface component configured to render a project development interface and to receive, via interaction with the project development interface, design input that defines an industrial control program and controller definitions as part of an industrial control project, wherein the controller definitions represent respective industrial controllers; and
a project generation component configured to
create, based on the design input, a smart object definition that represents the industrial control program, and
allocate, in accordance with smart object allocation input received via interaction with the project development interface, multiple instances of the smart object definition to respective multiple controller definitions of the controller definitions,
wherein allocation of the multiple instances of the smart object definition to the respective multiple controller definitions configures the industrial control project to assign copies of the industrial control program defined by the smart object definition to multiple industrial controllers represented by the multiple controller definitions.

### Claim 2 (depends on 1)

The system of claim 1, wherein
I/O tags of the industrial control program are written to be agnostic with regard to controller I/O addresses, and
the project generation component is configured to, for an instance of the multiple instances of the smart object definition, map the I/O tags of the industrial control program to available I/O addresses of an industrial controller represented by a controller definition, of the multiple controller definitions, to which the instance is allocated.

### Claim 3 (depends on 1)

The system of claim 1, wherein at least two of the multiple controller definitions represent respective at least two industrial controllers that are different models or have different I/O configurations.

### Claim 4 (depends on 1)

The system of claim 1, wherein the project development interface permits the industrial control program to be written or partially written prior to the allocation of the instances of the smart object definition to the multiple controller definitions.

### Claim 5 (depends on 1)

The system of claim 1, wherein the instances of the smart object definition comprise respective copies of the industrial control program and associated data tag definitions.

### Claim 6 (depends on 1)

The system of claim 1, wherein the user interface component is further configured to
render a navigation tree that comprises browsable smart object nodes representing smart object definitions, including the smart object definition, that are defined for the industrial control project, and
receive the smart object allocation input via interaction with the navigation tree.

### Claim 7 (depends on 1)

The system of claim 1, wherein
the smart object definition designates another smart object definition as a child smart object definition of the smart object definition, and
the other smart object definition defines another industrial control program.

### Claim 8 (depends on 7)

The system of claim 7, wherein the allocation of an instance, of the multiple instances of the smart object definition, to a controller definition of the multiple controller definitions causes an instance of the child smart object definition to also be allocated to the controller definition.

### Claim 9 (depends on 1)

The system of claim 1, wherein the executable components further comprise a project deployment component configured to, in response to receipt of an instruction to export executable content associated with a controller definition, of the multiple controller definitions, export a copy of the industrial control program defined by the instance of the smart object definition in a format capable of execution on an industrial controller represented by the controller definition.

### Claim 10

A method, comprising:
receiving, by a system comprising a processor via interaction with a project development interface, control programming input that defines an industrial control program;
defining, by the system as part of an industrial control project, a smart object definition representing the industrial control program based on the control programming input;
receiving, by the system via interaction with the project development interface, controller definition input that defines properties of multiple industrial controllers;
storing, by the system as part of the industrial control project, the controller definition input as controller definitions that respectively represent the multiple industrial controllers; and
allocating, by the system in accordance with smart object allocation input received via interaction with the project development interface, instances of the smart object definition to the controller definitions, respectively,
wherein the allocating configures the industrial control project to allocate copies of the industrial control program defined by the smart object definition to multiple industrial controllers represented by the controller definitions.

### Claim 11 (depends on 10)

The method of claim 10, wherein
the receiving of the control programming input comprises defining I/O tags of the industrial control program to be agnostic with regard to controller I/O addresses, and
the allocating comprises, for an instance of the instances of the smart object definition, mapping the I/O tags of the industrial control program to available I/O addresses of an industrial controller represented by a controller definition, of the controller definitions, to which the instance is allocated.

### Claim 12 (depends on 10)

The method of claim 10, wherein the allocating comprises allocating at least two instances of the smart object definition to respective at least two controller definitions representing respective at least two industrial controllers that are different models or have different I/O configurations.

### Claim 13 (depends on 10)

The method of claim 10, wherein the instances of the smart object definition comprise respective copies of the industrial control program and associated data tag definitions.

### Claim 14 (depends on 10)

The method of claim 10, wherein the method further comprises:
rendering, by the system, a navigation tree comprising browsable smart object nodes representing smart object definitions, including the smart object definition, that are defined for the industrial control project, and
receiving, by the system, the smart object allocation input via interaction with the navigation tree.

### Claim 15 (depends on 10)

The method of claim 10, wherein
the smart object definition is a first smart object definition,
the industrial control program is a first industrial control program,
the first smart object definition designates a second smart object definition as a child smart object definition of the smart object definition, and
the second smart object definition defines another industrial control program.

### Claim 16 (depends on 15)

The method of claim 15, wherein the allocating comprises, in response to allocation of an instance, of the instances of the smart object definition, to a controller definition of the multiple controller definitions, allocating an instance of the child smart object definition to the controller definition.

### Claim 17 (depends on 11)

The method of claim 11, further comprising, in response to receiving an instruction to export executable content associated with a controller definition, of the controller definitions, outputting, by the system, a copy of the industrial control program defined by the instance of the smart object definition in a format capable of execution on an industrial controller represented by the controller definition.

### Claim 18

A non-transitory computer-readable medium having stored thereon instructions that, in response to execution, cause a system comprising a processor to perform operations, the operations comprising:
receiving, via interaction with a project development interface, design input that defines an industrial control program and controller definitions as part of an industrial control project, wherein the controller definitions define properties of respective industrial controllers;
create, by the system as part of an industrial control project, a smart object definition representing the industrial control program based on the design input; and
assigning, in accordance with smart object allocation input received via interaction with the project development interface, instances of the smart object definition to selected controller definitions of the controller definitions,
wherein the assigning configures the industrial control project to assign copies of the industrial control program defined by the smart object definition to industrial controllers represented by the selected controller definitions.

### Claim 19 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein
the receiving of the design input comprises defining I/O tags of the industrial control program that are agnostic with regard to controller I/O addresses, and
the assigning comprises, for an instance of the instances of the smart object definition, mapping the I/O tags of the industrial control program to available I/O addresses of an industrial controller represented by a controller definition, of the controller definitions, to which the instance is assigned.

### Claim 20 (depends on 18)

The non-transitory computer-readable medium of claim 18, wherein the assigning comprises assigning at least two instances of the smart object definition to respective at least two controller definitions representing respective at least two industrial controllers that are different models or have different I/O configurations.
