Abstract: 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.

Abstract: 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.

Abstract: A system includes a processor and a memory accessible by the processor. The memory stores instructions that, when executed by the processor, cause the processor to receive an industrial automation project code file, wherein the industrial automation project code file defines one or more operations of an industrial automation system during performance of an industrial automation process, retrieve a set of industrial automation rules associated with a set of best practices for project code files, analyze the industrial automation project code file based on the set of industrial automation rules, including identifying one or more instances of inefficient tag usage, and identifying one or more sets of parallel overlapping tasks, and generate a report based the analysis of the industrial automation project code file based on the set of industrial automation rules.

Abstract: 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. The industrial IDE can also provide tools that extend the platform to users who wish to customize the industrial DSL to suit their preferred programming approaches.

Abstract: A (GUI) for designing an industrial automation system includes a design window and a first accessory window. The GUI presents a library visualization representative of a plurality of objects within the first accessory window, each object is represented by an icon and corresponds to a respective industrial automation device. The GUI receives inputs indicative of a selection of one or more objects of the plurality of objects from the library, presents the one or more objects in the design window, determines that the one or more inputs do not comply with a set of industrial automation system rules comprising one or more relationships between a plurality of industrial automation devices, and displays a warning message that the one or more inputs do not comply with the set of industrial automation system rules.

Abstract: A system includes a processor and a memory accessible by the processor. The memory stores instructions that, when executed by the processor, cause the processor to receive an industrial automation project code file, wherein the industrial automation project code file defines one or more operations of an industrial automation system during performance of an industrial automation process, retrieve a set of industrial automation rules associated with a set of best practices for project code files, analyze the industrial automation project code file based on the set of industrial automation rules, including identifying one or more instances of inefficient tag usage, and identifying one or more sets of parallel overlapping tasks, and generate a report based the analysis of the industrial automation project code file based on the set of industrial automation rules.

Abstract: A method includes generating a graphical user interface (GUI) depicting an industrial automation system, including objects, each object corresponding to an industrial automation component of the system, identifying a first industrial automation component, represented by a first object, based on a stage of a product life cycle associated with the first component, applying machine learning to identify a second component for replacing the first component based on one or more other components within the industrial automation system, and specifications of each of the additional components, generating and presenting a notification indicative of a suggestion to replace the first industrial automation component with the second industrial automation component, receiving an input authorizing replacement of the first industrial automation component with the second industrial automation component via the notification, and replacing the first object with a second object.

Abstract: A graphical user interface (GUI) for designing and monitoring an industrial automation system presents an alert based on a condition of an object corresponding to a respective industrial automation device displayed on the GUI. The GUI generates one or more suggestions for resolving the alert, including referencing a historical data set, parsing the historical data set to identify one or more previous instances in which the condition of the object occurred and was successfully resolved, and identifying one or more respective remedial actions taken in each of the one or more identified previous instances to resolve the condition. The GUI presents the one or more remedial actions as the one or more suggestions for resolving the alert, receives an input selecting one of the one or more remedial actions, and implements the selected remedial action.

Abstract: An industrial integrated development environment (IDE) supports commissioning features that facilitate intelligent deployment of an automation system project to appropriate industrial devices (e.g., industrial controllers, drives, HMI terminals, etc.). In some embodiments, the industrial IDE system can generate validation checklists that can be used during commissioning to validate the system and manage project validation sign-off procedures. After commissioning of the system, the IDE system can also support a number of runtime monitoring features, including monitoring the automation system during operation and providing assistance with regard to detecting, predicting, and correcting maintenance issues.

Abstract: An industrial integrated development environment (IDE) supports commissioning features that facilitate intelligent deployment of an automation system project to appropriate industrial devices (e.g., industrial controllers, drives, HMI terminals, etc.). In some embodiments, the industrial IDE system can generate validation checklists that can be used during commissioning to validate the system and manage project validation sign-off procedures. After commissioning of the system, the IDE system can also support a number of runtime monitoring features, including monitoring the automation system during operation and providing assistance with regard to detecting, predicting, and correcting maintenance issues.

Abstract: A graphical user interface (GUI) for designing and monitoring an industrial automation system presents an alert based on a condition of an object corresponding to a respective industrial automation device displayed on the GUI. The GUI generates one or more suggestions for resolving the alert, including referencing a historical data set, parsing the historical data set to identify one or more previous instances in which the condition of the object occurred and was successfully resolved, and identifying one or more respective remedial actions taken in each of the one or more identified previous instances to resolve the condition. The GUI presents the one or more remedial actions as the one or more suggestions for resolving the alert, receives an input selecting one of the one or more remedial actions, and implements the selected remedial action.

Abstract: 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.

Abstract: An industrial integrated development environment (IDE) supports open or extensible application programming interfaces (APIs) that enable end users (e.g., plant asset owners, original equipment manufacturers (OEM), system integrators, etc.) to build upon the IDE's development platform to create custom views or to code custom functionality. This can include, for example, defining a control programming syntax supported by the industrial IDE, customizing a development environment view afforded by the IDE's interface, modifying or creating project editing functions, defining customized programming guardrails designed to guide compliance with in-house programming standards, or other such IDE customizations.

Abstract: An industrial integrated development environment (IDE) supports a testing framework that verifies operation of all aspects of the project (e.g., controller code, HMI screens or other visualizations, panel layouts, wiring schedules, etc.). As part of this testing framework, automation objects supported by the industrial IDE include associated test scripts designed to execute one or more test scenarios appropriate to the type of automation object or project being tested. Test scripts can also be associated with portions of the system project. The testing platform applies testing to the automation project as a whole in a holistic manner rather than to specific portions of a control program, verifying linkages across design platforms (e.g., control code, visualization, panel layouts, wiring, piping, etc.) that may otherwise not be tested.

Abstract: An industrial integrated development environment (IDE) includes a training component that improves the IDE's automated design tools over time based on analysis of aggregated project data submitted by developers over time. The industrial IDE can apply analytics (e.g., artificial intelligence, machine learning, etc.) to project data submitted by developers across multiple industrial enterprises to identify commonly used control code, visualizations, device configurations, or control system architectures that are frequently used for a given industrial function, machine, or application. This learned information can be encoded in a training module, which can be leveraged by the IDE to generate programming, visualization, or configuration recommendations. The IDE can automatically add suitable control code, visualizations, or configuration data to new control projects being developed based on an inference of the developer's design goals and knowledge of how these goals have been implemented by other developers.

Abstract: An industrial integrated development environment (IDE) supports a testing framework that verifies operation of all aspects of the project (e.g., controller code, HMI screens or other visualizations, panel layouts, wiring schedules, etc.). As part of this testing framework, automation objects supported by the industrial IDE include associated test scripts designed to execute one or more test scenarios appropriate to the type of automation object or project being tested. Test scripts can also be associated with portions of the system project. The testing platform applies testing to the automation project as a whole in a holistic manner rather than to specific portions of a control program, verifying linkages across design platforms (e.g., control code, visualization, panel layouts, wiring, piping, etc.) that may otherwise not be tested.

Abstract: An industrial integrated development environment (IDE) supports open or extensible application programming interfaces (APIs) that enable end users (e.g., plant asset owners, original equipment manufacturers (OEM), system integrators, etc.) to build upon the IDE's development platform to create custom views or to code custom functionality. This can include, for example, defining a control programming syntax supported by the industrial IDE, customizing a development environment view afforded by the IDE's interface, modifying or creating project editing functions, defining customized programming guardrails designed to guide compliance with in-house programming standards, or other such IDE customizations.

Abstract: An industrial integrated development environment (IDE) includes a training component that improves the IDE's automated design tools over time based on analysis of aggregated project data submitted by developers over time. The industrial IDE can apply analytics (e.g., artificial intelligence, machine learning, etc.) to project data submitted by developers across multiple industrial enterprises to identify commonly used control code, visualizations, device configurations, or control system architectures that are frequently used for a given industrial function, machine, or application. This learned information can be encoded in a training module, which can be leveraged by the IDE to generate programming, visualization, or configuration recommendations. The IDE can automatically add suitable control code, visualizations, or configuration data to new control projects being developed based on an inference of the developer's design goals and knowledge of how these goals have been implemented by other developers.

Abstract: 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. The industrial IDE can also provide tools that extend the platform to users who wish to customize the industrial DSL to suit their preferred programming approaches.

Abstract: A (GUI) for designing an industrial automation system includes a design window and a first accessory window. The GUI presents a library visualization representative of a plurality of objects within the first accessory window, each object is represented by an icon and corresponds to a respective industrial automation device. The GUI receives inputs indicative of a selection of one or more objects of the plurality of objects from the library, presents the one or more objects in the design window, determines that the one or more inputs do not comply with a set of industrial automation system rules comprising one or more relationships between a plurality of industrial automation devices, and displays a warning message that the one or more inputs do not comply with the set of industrial automation system rules.