Abstract: An industrial integrated development environment (IDE) allows project topologies to be defined using an industrial domain-specific language (DSL) script. DSL scripting language can be used to define a control system topology in terms of the devices that make up the control system as well as the data connections between those devices. The IDE system can translate resulting topology to a project tree that serves as the basis for a control system project.

Abstract: An industrial integrated development environment (IDE) can dynamically generate user interfaces for device profiles using predefined reusable profile templates together with data models of the devices for which the device profile interfaces are to be created. The device profile template defines features or components of profile interface views that are reusable across multiple different devices. The industrial IDE determines which interface features defined by the device profile template are required to support the device's data and supported features defined by the data model, and dynamically adapts the device profile template to yield a suitable device profile interface that can be used to view and edit the device's data and configuration parameter values.

Abstract: An industrial integrated development environment (IDE) allows add-on bus profiles and add-on controller profiles to be defined using an industrial domain-specific language (DSL) script. These add-on profiles can then be added to the IDE's device profile library for use in industrial control projects. This mitigates the need to write new source code to create these profiles and to release an updated version of the IDE software to make these profiles available for use. Industrial DSL scripting can also be used to define a physical and logical topology of an industrial control system within the IDE system as part of the control system project that will be deployed to the control system.

Abstract: An industrial integrated development environment (IDE) allows project topologies to be defined using an industrial domain-specific language (DSL) script. DSL scripting language can be used to define a control system topology in terms of the devices that make up the control system as well as the data connections between those devices. The IDE system can translate resulting topology to a project tree that serves as the basis for a control system project.

Abstract: An industrial integrated development environment (IDE) is designed to execute on a cloud-platform or a web-based platform. The IDE includes a library of device profiles that render graphical device configuration interfaces for reading and writing values of device parameters. To allow device profiles that were designed to operate within the context of a local, non-web-based IDE system to be used within the web-based IDE without the need to rewrite the device profiles or their associated services, the IDE can include a device service adapter that instantiates web services that translate the device configuration interfaces to a suitable web-based format, such as hypertext markup language. In this way, device profiles become agnostic with regard to the type of IDE platform in which the profiles are used.

Abstract: A centralized industrial catalog system aggregates product information from disparate sources and globally synchronizes updated catalog information to local versions of the product catalog at customer sites. The catalog system can execute as a service on a cloud platform accessible to end user applications or local catalogs. The catalog system serves as a scalable global authority for known product information for either a single product vendor or for multiple vendors. The industrial catalog system can ensure that local versions of product catalog content is synchronized with high-level sources.

Abstract: An industrial controller includes a processing unit and a memory. The industrial controller is operable to communicate using an optimized connection packet including I/O data from a plurality of I/O modules arranged as an unstructured data block. The processing unit is operable to operate on the I/O data within the optimized connection packet to control a process. The memory is operable to store a plurality of cast tags. Each cast tag is associated with one of the I/O modules and provides a logical reference to a subset of the unformatted data block including at least a portion of the I/O data for the associated I/O module.