An industrial IDE supports development of control programming using an industrial domain-specific language (DSL) that allows control programming to be written using a scripted programming language having features catered to the industrial domain. The industrial DSL can simplify and streamline development of industrial control code relative to using conventional graphics-based control programming formats such as ladder logic, since a script-based industrial DSL can be used to write programming code using fewer mouse clicks relative to traditional control programming environments. Editing tools inherent to the industrial DSL can provide dynamic programming feedback that guides the developer through the process of developing control code. A development interface of the industrial IDE can comprises two editing windows that render the control program in a graphical format and in a text-based format simultaneously, allowing the user to edit the program in either format on the same interface.

A software defined (SD) process control system (SDCS) includes a control container having contents which are executable during run-time of the process plant to control at least a portion of an industrial process. The SDCS also includes a security service associated with the control container and including contents which define one or more security conditions. The security service executes via a container on a compute node of the SDCS to control access to and/or data flow from the control container based on the contents of the security container.

An industrial IDE supports development of control programming using an industrial domain-specific language (DSL) that allows control programming to be written using a scripted programming language having features catered to the industrial domain. The industrial DSL can simplify and streamline development of industrial control code relative to using conventional graphics-based control programming formats such as ladder logic, since a script-based industrial DSL can be used to write programming code using fewer mouse clicks relative to traditional control programming environments. Editing tools inherent to the industrial DSL can provide dynamic programming feedback that guides the developer through the process of developing control code. A development interface of the industrial IDE can comprises two editing windows that render the control program in a graphical format and in a text-based format simultaneously, allowing the user to edit the program in either format on the same interface.

An industrial integrated development environment (IDE) provides a development framework for designing, programming, and configuring multiple aspects of an industrial automation system using a common design environment and data model. Projects creating using embodiments of the IDE system can be built on an object-based model rather than, or in addition to, a tag-based architecture. To this end, the IDE system can support the use of automation objects that serve as building blocks for this object-based development structure. To ensure consistency within and between projects, as well as to ensure that a given industrial project is dynamically updated to reflect changes to an industrial asset's attributes (e.g., control code, visualization definitions, testing scripts, analytic code, etc.), embodiments of the IDE system can use automation object inheritance features to propagate changes made to an automation object definition to all instances of the automation object used throughout a control project.

A program generation device generating an operation program causing a robot to execute a task is provided. The program generation device includes: a display control unit displaying an input screen including an operation block, display area where an operation block relating to an operation of the robot is displayed, an operation block arrangement area where the operation block selected from the operation block display area is arranged to generate the operation program, and a text display area where the operation program is displayed in a text format; and a text editing unit editing the operation program in the text format and displaying the edited operation program in the text display area.

An industrial integrated development environment (IDE) provides a development framework for designing, programming, and configuring multiple aspects of an industrial automation system using a common design environment and data model. Projects creating using embodiments of the IDE system can be built on an object-based model rather than, or in addition to, a tag-based architecture. To this end, the IDE system can support the use of automation objects that serve as building blocks for this object-based development structure. To ensure consistency within and between projects, as well as to ensure that a given industrial project is dynamically updated to reflect changes to an industrial asset's attributes (e.g., control code, visualization definitions, testing scripts, analytic code, etc.), embodiments of the IDE system can use automation object inheritance features to propagate changes made to an automation object definition to all instances of the automation object used throughout a control project.

An industrial integrated development environment (IDE) comprises a development interface that affords a user a great deal of control over the editing tools, workspace canvases, and project information rendered at a given time. The industrial IDE system automatically filters the tools, panels, and information available for selection based on a current project development task, such that a focused subset of editing tools relevant to a current development task or context are made available for selection while other tools are hidden. The development interface also allows the user to selectively render or hide selected tools or information from among the relevant, filtered set of tools. This can reduce or eliminate unnecessary clutter and aid in quickly and easily locating and selecting a desired editing function. The IDE's development interface can also conform to a structured organization of workspace canvases and panels that facilitates intuitive workflow.

An industrial integrated development environment (IDE) supports collaborative tools that allow multiple designers and programmers to remotely submit design input to the same automation system project in parallel while maintaining project consistency. These collaborative features can include, for example, brokering between different sets of design input directed to the same portion of the system project, generating notifications to remote designers when a portion of the system project is modified, sharing of development interfaces or environments, facilitating involvement of outside technical support experts to assist with design issues, and other collaborative features.

An industrial IDE supports development of control programming using an industrial domain-specific language (DSL) that allows control programming to be written using a scripted programming language having features catered to the industrial domain. The industrial DSL can simplify and streamline development of industrial control code relative to using conventional graphics-based control programming formats such as ladder logic, since a script-based industrial DSL can be used to write programming code using fewer mouse clicks relative to traditional control programming environments. Editing tools inherent to the industrial DSL can provide dynamic programming feedback that guides the developer through the process of developing control code. A development interface of the industrial IDE can comprises two editing windows that render the control program in a graphical format and in a text-based format simultaneously, allowing the user to edit the program in either format on the same interface.

An industrial integrated development environment (IDE) provides a development framework for designing, programming, and configuring multiple aspects of an industrial automation system using a common design environment and data model. Projects creating using embodiments of the IDE system can be built on an object-based model rather than, or in addition to, a tag-based architecture. To this end, the IDE system can support the use of automation objects that serve as building blocks for this object-based development structure. To ensure consistency within and between projects, as well as to ensure that a given industrial project is dynamically updated to reflect changes to an industrial asset's attributes (e.g., control code, visualization definitions, testing scripts, analytic code, etc.), embodiments of the IDE system can use automation object inheritance features to propagate changes made to an automation object definition to all instances of the automation object used throughout a control project.