Patent Description:
<CIT> discloses that automatic conversion of textual program code to graphical program code is performed. The method automatically translates the given functionality of a textual program code into executable graphical program code, corresponding to the same functionality. The method includes a parsing routine that generates a syntax tree and code generation routines, which create graphical program code from the syntax tree.

<CIT> discloses a system and method for developing a sequence of motion control operations. A motion control prototyping environment application is described that is designed to enable a user to develop/prototype a motion control sequence, e.g., without needing to write or construct code in any programming language. The environment provides a graphical user interface (GUI) enabling the user to develop/prototype the motion control sequence, by selecting from and configuring a sequence of motion control operations using the GUI.

It is therefore the object of the present invention to provide an improved system for developing industrial control programming, a corresponding method and a corresponding computer-readable medium.

The following presents a simplified summary in order to provide a basic understanding of some aspects described herein. This summary is not an extensive overview nor is intended to identify key/critical elements or to delineate the scope of the various aspects described herein. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

In one or more embodiments, a system for developing industrial control programming is provided, comprising a user interface component configured to receive industrial control programming formatted as an industrial domain-specific language (DSL) and to render programming feedback in response to receipt of the industrial control programming; and a DSL editor configured to parse the industrial control programming, formatted as the industrial DSL, to yield a hierarchical model of the industrial control programming and to compile the hierarchical model to yield industrial control code that is executable on an industrial control device.

Also, one or more embodiments provide a method for programming industrial systems, comprising receiving, by a system comprising a processor, industrial control programming scripted as an industrial domain-specific language (DSL); rendering, by the system, programming feedback in response to receipt of the industrial control programming; parsing, by the system, the industrial control programming formatted as the industrial DSL to yield a hierarchical model of the industrial control programming; and compiling, by the system, the hierarchical model to yield industrial control code that is executable on an industrial control device.

Also, according to one or more embodiments, a non-transitory computer-readable medium is provided having stored thereon instructions that, in response to execution, cause a system to perform operations, the operations comprising receiving industrial control programming scripted as an industrial domain-specific language (DSL); rendering programming feedback in response to receipt of the industrial control programming; parsing the industrial control programming formatted as the industrial DSL to yield a hierarchical model of the industrial control programming; and compiling the hierarchical model into industrial control code that is executable on an industrial control device.

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of various ways which can be practiced, all of which are intended to be covered herein. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.

The subject disclosure is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. It may be evident, however, that the subject disclosure can be practiced without these specific details.

As used in this application, the terms "component," "system," "platform," "layer," "controller," "terminal," "station," "node," "interface" are intended to refer to a computer-related entity or an entity related to, or that is part of, an operational apparatus with one or more specific functionalities, wherein such entities can be either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical or magnetic storage medium) including affixed (e.g., screwed or bolted) or removable affixed solid-state storage drives; an object; an executable; a thread of execution; a computer-executable program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers. Also, components as described herein can execute from various computer readable storage media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry which is operated by a software or a firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can include a processor therein to execute software or firmware that provides at least in part the functionality of the electronic components. As further yet another example, interface(s) can include input/output (I/O) components as well as associated processor, application, or Application Programming Interface (API) components. While the foregoing examples are directed to aspects of a component, the exemplified aspects or features also apply to a system, platform, interface, layer, controller, terminal, and the like.

As used herein, the terms "to infer" and "inference" refer generally to the process of reasoning about or inferring states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic-that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.

Furthermore, the term "set" as employed herein excludes the empty set; e.g., the set with no elements therein. Thus, a "set" in the subject disclosure includes one or more elements or entities. As an illustration, a set of controllers includes one or more controllers; a set of data resources includes one or more data resources; etc. Likewise, the term "group" as utilized herein refers to a collection of one or more entities; e.g., a group of nodes refers to one or more nodes.

Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. A combination of these approaches also can be used.

<FIG> is a block diagram of an example industrial control environment <NUM>. In this example, a number of industrial controllers <NUM> are deployed throughout an industrial plant environment to monitor and control respective industrial systems or processes relating to product manufacture, machining, motion control, batch processing, material handling, or other such industrial functions. Industrial controllers <NUM> typically execute respective control programs to facilitate monitoring and control of industrial devices <NUM> making up the controlled industrial assets or systems (e.g., industrial machines). One or more industrial controllers <NUM> may also comprise a soft controller executed on a personal computer or other hardware platform, or on a cloud platform. Some hybrid devices may also combine controller functionality with other functions (e.g., visualization). The control programs executed by industrial controllers <NUM> can comprise substantially any type of code capable of processing input signals read from the industrial devices <NUM> and controlling output signals generated by the industrial controllers <NUM>, including but not limited to ladder logic, sequential function charts, function block diagrams, or structured text.

Industrial devices <NUM> may include both input devices that provide data relating to the controlled industrial systems to the industrial controllers <NUM>, and output devices that respond to control signals generated by the industrial controllers <NUM> to control aspects of the industrial systems. Example input devices can include telemetry devices (e.g., temperature sensors, flow meters, level sensors, pressure sensors, etc.), manual operator control devices (e.g., push buttons, selector switches, etc.), safety monitoring devices (e.g., safety mats, safety pull cords, light curtains, etc.), and other such devices. Output devices may include motor drives, pneumatic actuators, signaling devices, robot control inputs, valves, pumps, and the like.

Industrial controllers <NUM> may communicatively interface with industrial devices <NUM> over hardwired or networked connections. For example, industrial controllers <NUM> can be equipped with native hardwired inputs and outputs that communicate with the industrial devices <NUM> to effect control of the devices. The native controller I/O can include digital I/O that transmits and receives discrete voltage signals to and from the field devices, or analog I/O that transmits and receives analog voltage or current signals to and from the devices. The controller I/O can communicate with a controller's processor over a backplane such that the digital and analog signals can be read into and controlled by the control programs. Industrial controllers <NUM> can also communicate with industrial devices <NUM> over a network using, for example, a communication module or an integrated networking port. Exemplary networks can include the Internet, intranets, Ethernet, DeviceNet, ControlNet, Data Highway and Data Highway Plus (DH/DH+), Remote I/O, Fieldbus, Modbus, Profibus, wireless networks, serial protocols, and the like. The industrial controllers <NUM> can also store persisted data values that can be referenced by their associated control programs and used for control decisions, including but not limited to measured or calculated values representing operational states of a controlled machine or process (e.g., tank levels, positions, alarms, etc.) or captured time series data that is collected during operation of the automation system (e.g., status information for multiple points in time, diagnostic occurrences, etc.). Similarly, some intelligent devices - including but not limited to motor drives, instruments, or condition monitoring modules - may store data values that are used for control and/or to visualize states of operation. Such devices may also capture time-series data or events on a log for later retrieval and viewing.

Industrial automation systems often include one or more human-machine interfaces (HMIs) <NUM> that allow plant personnel to view telemetry and status data associated with the automation systems, and to control some aspects of system operation. HMIs <NUM> may communicate with one or more of the industrial controllers <NUM> over a plant network <NUM>, and exchange data with the industrial controllers to facilitate visualization of information relating to the controlled industrial processes on one or more pre-developed operator interface screens. HMIs <NUM> can also be configured to allow operators to submit data to specified data tags or memory addresses of the industrial controllers <NUM>, thereby providing a means for operators to issue commands to the controlled systems (e.g., cycle start commands, device actuation commands, etc.), to modify setpoint values, etc. HMIs <NUM> can generate one or more display screens through which the operator interacts with the industrial controllers <NUM>, and thereby with the controlled processes and/or systems. Example display screens can visualize present states of industrial systems or their associated devices using graphical representations of the processes that display metered or calculated values, employ color or position animations based on state, render alarm notifications, or employ other such techniques for presenting relevant data to the operator. Data presented in this manner is read from industrial controllers <NUM> by HMIs <NUM> and presented on one or more of the display screens according to display formats chosen by the HMI developer. HMIs may comprise fixed location or mobile devices with either user-installed or pre-installed operating systems, and either user-installed or pre-installed graphical application software.

Some industrial environments may also include other systems or devices relating to specific aspects of the controlled industrial systems. These may include, for example, a data historian <NUM> that aggregates and stores production information collected from the industrial controllers <NUM> or other data sources. device documentation stores containing electronic documentation for the various industrial devices making up the controlled industrial systems, inventory tracking systems, work order management systems, repositories for machine or process drawings and documentation, vendor product documentation storage, vendor knowledgebases, internal knowledgebases, work scheduling applications, or other such systems, some or all of which may reside on an office network <NUM> of the industrial environment.

Higher-level systems <NUM> may carry out functions that are less directly related to control of the industrial automation systems on the plant floor, and instead are directed to long term planning, high-level supervisory control, analytics, reporting, or other such high-level functions. These systems <NUM> may reside on the office network <NUM> at an external location relative to the plant facility, or on a cloud platform with access to the office and/or plant networks. Higher-level systems <NUM> may include, but are not limited to, cloud storage and analysis systems, big data analysis systems, manufacturing execution systems, data lakes, reporting systems, etc. In some scenarios, applications running at these higher levels of the enterprise may be configured to analyze control system operational data, and the results of this analysis may be fed back to an operator at the control system or directly to a controller <NUM> or device <NUM> in the control system.

The various control, monitoring, and analytical devices that make up an industrial environment must be programmed or configured using respective configuration applications specific to each device. For example, industrial controllers <NUM> are typically configured and programmed using a control programming development application such as a ladder logic editor (e.g., executing on a client device <NUM>). Using such development platforms, a designer can write control programming (e.g., ladder logic, structured text, function block diagrams, etc.) for carrying out a desired industrial sequence or process and download the resulting program files to the controller <NUM>. Separately, developers design visualization screens and associated navigation structures for HMIs <NUM> using an HMI development platform (e.g., executing on client device <NUM>) and download the resulting visualization files to the HMI <NUM>. Some industrial devices <NUM> - such as motor drives, telemetry devices, safety input devices, etc. - may also require configuration using separate device configuration tools (e.g., executing on client device <NUM>) that are specific to the device being configured. Such device configuration tools may be used to set device parameters or operating modes (e.g., high/low limits, output signal formats, scale factors, energy consumption modes, etc.).

The necessity of using separate configuration tools to program and configure disparate aspects of an industrial automation system results in a piecemeal design approach whereby different but related or overlapping aspects of an automation system are designed, configured, and programmed separately on different development environments. For example, a motion control system may require an industrial controller to be programmed and a control loop to be tuned using a control logic programming platform, a motor drive to be configured using another configuration platform, and an associated HMI to be programmed using a visualization development platform. Related peripheral systems - such as vision systems, safety systems, etc. - may also require configuration using separate programming or development applications.

This segregated development approach can also necessitate considerable testing and debugging efforts to ensure proper integration of the separately configured system aspects. In this regard, intended data interfacing or coordinated actions between the different system aspects may require significant debugging due to a failure to properly coordinate disparate programming efforts.

Industrial development platforms are also limited in terms of the development interfaces offered to the user to facilitate programming and configuration. These interfaces typically offer a fixed user experience that requires the user to develop control code, visualizations, or other control system aspects using a vendor-specific or industry-specific language or interface.

To address at least some of these or other issues, one or more embodiments described herein provide an integrated development environment (IDE) for programming and configuration of multiple aspects of an industrial automation system using a common design environment and data model. Embodiments of the industrial IDE can be used to configure and manage automation system devices in a common way, facilitating integrated, multi-discipline programming of control, visualization, and other aspects of the control system.

In general, the industrial IDE implements features that span the full automation lifecycle, including design (e.g., device selection and sizing, controller programming, visualization development, device configuration, testing, etc.); installation, configuration and commissioning; operation, improvement, and administration; and troubleshooting, expanding, and upgrading.

Embodiments of the industrial IDE can include a library of modular code and visualizations that are specific to industry verticals and common industrial applications within those verticals. These code and visualization modules can simplify development and shorten the development cycle, while also supporting consistency and reuse across an industrial enterprise.

Also, one or more embodiments of the industrial IDE can support 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. For example, the industrial DSL can support the creation and inclusion of automation objects within the control program. Automation object types can represent various types of industrial assets or entities, including but not limited to industrial processes, machines, industrial devices (e.g., controllers, motor drives, telemetry devices, etc.), industrial robots, actuators, HMI screens, control routines, controller tags, or other such entities specific to the industrial domain. These automation objects can be organized according to a namespace that defines parent-child relationships between the objects; e.g., in terms of the hierarchical relationships between their associated industrial assets or entities.

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 also provide dynamic programming feedback that guides the developer through the process of developing control code. This feedback can be generated based on industry-specific or vertical-specific standards encoded in the industrial IDE as programming guardrails. These guardrails can provide programming feedback that facilitate compliance with industry control or programming standards, which may be specific to the particular industrial vertical for which the program is being developed (e.g. automotive, food and drug, textiles, oil and gas, etc.). The guardrails can also be customized to provide feedback that keeps programmers within compliance of in-house programming standards.

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. This can include allowing users to define their own automation objects, programming syntax, syntax or error highlighting, programming guardrails, or other such features of the industrial DSL.

<FIG> is a block diagram of an example integrated development environment (IDE) system <NUM> according to one or more embodiments of this disclosure. Aspects of the systems, apparatuses, or processes explained in this disclosure can constitute machine-executable components embodied within machine(s), e.g., embodied in one or more computer-readable mediums (or media) associated with one or more machines. Such components, when executed by one or more machines, e.g., computer(s), computing device(s), automation device(s), virtual machine(s), etc., can cause the machine(s) to perform the operations described.

IDE system <NUM> can include a user interface component <NUM> including a DSL editor <NUM>, a project generation component <NUM>, a project deployment component <NUM>, an editor definition component <NUM>, one or more processors <NUM>, and memory <NUM>. In various embodiments, one or more of the user interface component <NUM>, project generation component <NUM>, project deployment component <NUM>, editor definition component <NUM>, the one or more processors <NUM>, and memory <NUM> can be electrically and/or communicatively coupled to one another to perform one or more of the functions of the IDE system <NUM>. In some embodiments, components <NUM>, <NUM>, <NUM>, and <NUM> can comprise software instructions stored on memory <NUM> and executed by processor(s) <NUM>. IDE system <NUM> may also interact with other hardware and/or software components not depicted in <FIG>. For example, processor(s) <NUM> may interact with one or more external user interface devices, such as a keyboard, a mouse, a display monitor, a touchscreen, or other such interface devices.

User interface component <NUM> can be configured to receive user input and to render output to the user in any suitable format (e.g., visual, audio, tactile, etc.). In some embodiments, user interface component <NUM> can be configured to communicatively interface with an IDE client that executes on a client device (e.g., a laptop computer, tablet computer, smart phone, etc.) that is communicatively connected to the IDE system <NUM> (e.g., via a hardwired or wireless connection). The user interface component <NUM> can then receive user input data and render output data via the IDE client. In other embodiments, user interface component <NUM> can be configured to generate and serve suitable interface screens to a client device (e.g., program development screens), and exchange data via these interface screens. Input data that can be received via various embodiments of user interface component <NUM> can include, but is not limited to, programming code, industrial design specifications or goals, engineering drawings, AR/VR input, DSL definitions, video or image data, or other such input. Output data rendered by various embodiments of user interface component <NUM> can include program code, programming feedback (e.g., error and highlighting, coding suggestions, etc.), programming and visualization development screens, etc..

Project generation component <NUM> can be configured to create a system project comprising one or more project files based on design input received via the user interface component <NUM>, as well as industrial knowledge, predefined code modules, and automation objects <NUM> maintained by the IDE system <NUM>. Project deployment component <NUM> can be configured to commission the system project created by the project generation component to appropriate industrial devices (e.g., controllers, HMI terminals, motor drives, AR/VR systems, etc.) for execution. To this end, project deployment component <NUM> can identify the appropriate target devices to which respective portions of the system project should be sent for execution, translate these respective portions to formats understandable by the target devices, and deploy the translated project components to their corresponding devices.

Editor definition component <NUM> can be configured to receive DSL definition data that defines or modifies programming aspects of the industrial DSL, and to configure the DSL editor in accordance with the DSL definition data. DSL programming features that can be configured via the editor definition component <NUM> can include, but are not limited to, the DSL syntax, types of programming feedback and conditions under which the feedback is provided (e.g., error highlighting, syntax highlighting, coding recommendations, etc.), available automation objects, namespace definitions, or other such features.

The one or more processors <NUM> can perform one or more of the functions described herein with reference to the systems and/or methods disclosed. Memory <NUM> can be a computer-readable storage medium storing computer-executable instructions and/or information for performing the functions described herein with reference to the systems and/or methods disclosed.

<FIG> is a diagram illustrating a generalized architecture of the industrial IDE system <NUM> according to one or more embodiments. Industrial IDE system <NUM> can implement a common set of services and workflows spanning not only design, but also commissioning, operation, and maintenance. In terms of design, the IDE system <NUM> can support not only industrial controller programming and HMI development, but also sizing and selection of system components, device/system configuration, AR/VR visualizations, and other features. The IDE system <NUM> can also include tools that simplify and automate commissioning of the resulting project and assist with subsequent administration of the deployed system during runtime.

Embodiments of the IDE system <NUM> that are implemented on a cloud platform also facilitate collaborative project development whereby multiple developers <NUM> contribute design and programming input to a common automation system project <NUM>. Collaborative tools supported by the IDE system can manage design contributions from the multiple contributors and perform version control of the aggregate system project <NUM> to ensure project consistency.

Based on design and programming input from one or more developers <NUM>, IDE system <NUM> generates a system project <NUM> comprising one or more project files. The system project <NUM> encodes control programming; HMI, AR, and/or VR visualizations; device or sub-system configuration data (e.g., drive parameters, vision system configurations, telemetry device parameters, safety zone definitions, etc.); or other such aspects of an industrial automation system being designed. IDE system <NUM> can identify the appropriate target devices <NUM> on which respective aspects of the system project <NUM> should be executed (e.g., industrial controllers, HMI terminals, variable frequency drives, safety devices, etc.), translate the system project <NUM> to executable files that can be executed on the respective target devices, and deploy the executable files to their corresponding target devices <NUM> for execution, thereby commissioning the system project <NUM> to the plant floor for implementation of the automation project.

To support enhanced development capabilities, some embodiments of IDE system <NUM> can be built on an object-based data model rather than a tag-based architecture. Automation objects <NUM> serve as the building block for this object-based development architecture. <FIG> is a diagram illustrating several example automation object properties that can be leveraged by the IDE system <NUM> in connection with building, deploying, and executing a system project <NUM>. Automation objects <NUM> can be created and augmented during design, integrated into larger data models, and consumed during runtime. These automation objects <NUM> provide a common data structure across the IDE system <NUM> and can be stored in an object library (e.g., part of memory <NUM>) for reuse. The object library can store predefined automation objects <NUM> representing various classifications of real-world industrial assets <NUM>, including but not limited to pumps, tanks, values, motors, motor drives (e.g., variable frequency drives), industrial robots, actuators (e.g., pneumatic or hydraulic actuators), or other such assets. Automation objects <NUM> can represent elements at substantially any level of an industrial enterprise, including individual devices, machines made up of many industrial devices and components (some of which may be associated with their own automation objects <NUM>), and entire production lines or process control systems.

An automation object <NUM> for a given type of industrial asset can encode such aspects as 2D or 3D visualizations, alarms, control coding (e.g., logic or other type of control programming), analytics, startup procedures, testing protocols, validation reports, simulations, schematics, security protocols, and other such properties associated with the industrial asset <NUM> represented by the object <NUM>. Automation objects <NUM> can also be geotagged with location information identifying the location of the associated asset. During runtime of the system project <NUM>, the automation object <NUM> corresponding to a given real-world asset <NUM> can also record status or operational history data for the asset. In general, automation objects <NUM> serve as programmatic representations of their corresponding industrial assets <NUM>, and can be incorporated into a system project <NUM> as elements of control code, a 2D or 3D visualization, a knowledgebase or maintenance guidance system for the industrial assets, or other such aspects.

<FIG> is a diagram illustrating example data flows associated with creation of a system project <NUM> for an automation system being designed using IDE system <NUM> according to one or more embodiments. A client device <NUM> (e.g., a laptop computer, tablet computer, desktop computer, mobile device, wearable AR/VR appliance, etc.) executing an IDE client application <NUM> can access the IDE system's project development tools and leverage these tools to create a comprehensive system project <NUM> for an automation system being developed. Through interaction with the system's user interface component <NUM>, developers can submit design input <NUM> to the IDE system <NUM> in various supported formats, including industry-specific control programming (e.g., control logic, structured text, sequential function charts, etc.) and HMI screen configuration input. Based on this design input <NUM> and information stored in an industry knowledgebase (predefined code modules <NUM> and visualizations <NUM>, guardrail templates <NUM>, physics-based rules <NUM>, etc.), user interface component <NUM> renders design feedback <NUM> designed to assist the designer in connection with developing a system project <NUM> for configuration, control, and visualization of an industrial automation system.

In addition to control programming and visualization definitions, some embodiments of IDE system <NUM> can be configured to receive digital engineering drawings (e.g., computer-aided design (CAD) files) as design input <NUM>. In such embodiments, project generation component <NUM> can generate portions of the system project <NUM> - e.g., by automatically generating control and/or visualization code - based on analysis of existing design drawings. Drawings that can be submitted as design input <NUM> can include, but are not limited to, P&ID drawings, mechanical drawings, flow diagrams, or other such documents. For example, a P&ID drawing can be imported into the IDE system <NUM>, and project generation component <NUM> can identify elements (e.g., tanks, pumps, etc.) and relationships therebetween conveyed by the drawings. Project generation component <NUM> can associate or map elements identified in the drawings with appropriate automation objects <NUM> corresponding to these elements (e.g., tanks, pumps, etc.) and add these automation objects <NUM> to the system project <NUM>. The device-specific and asset-specific automation objects <NUM> include suitable code and visualizations to be associated with the elements identified in the drawings. In general, the IDE system <NUM> can examine one or more different types of drawings (mechanical, electrical, piping, etc.) to determine relationships between devices, machines, and/or assets (including identifying common elements between the drawings) and intelligently associate these elements with appropriate automation objects <NUM>, code modules <NUM>, and visualizations <NUM>. The IDE system <NUM> can leverage physics-based rules <NUM> as well as pre-defined code modules <NUM> and visualizations <NUM> as necessary in connection with generating code or project data for system project <NUM>.

The IDE system <NUM> can also determine whether pre-defined visualization content is available for any of the objects discovered in the drawings and generate appropriate HMI screens or AR/VR content for the discovered objects based on these pre-defined visualizations. To this end, the IDE system <NUM> can store industry-specific, asset-specific, and/or application-specific visualizations <NUM> that can be accessed by the project generation component <NUM> as needed. These visualizations <NUM> can be classified according to industry or industrial vertical (e.g., automotive, food and drug, oil and gas, pharmaceutical, etc.), type of industrial asset (e.g., a type of machine or industrial device), a type of industrial application (e.g., batch processing, flow control, web tension control, sheet metal stamping, water treatment, etc.), or other such categories. Predefined visualizations <NUM> can comprise visualizations in a variety of formats, including but not limited to HMI screens or windows, mashups that aggregate data from multiple pre-specified sources, AR overlays, VR objects representing 3D virtualizations of the associated industrial asset, or other such visualization formats. IDE system <NUM> can select a suitable visualization for a given object based on a predefined association between the object type and the visualization content.

In another example, markings applied to an engineering drawing by a user can be understood by some embodiments of the project generation component <NUM> to convey a specific design intention or parameter. For example, a marking in red pen can be understood to indicate a safety zone, two circles connected by a dashed line can be interpreted as a gearing relationship, and a bold line may indicate a camming relationship. In this way, a designer can sketch out design goals on an existing drawing in a manner that can be understood and leveraged by the IDE system <NUM> to generate code and visualizations. In another example, the project generation component <NUM> can learn permissives and interlocks (e.g., valves and their associated states) that serve as necessary preconditions for starting a machine based on analysis of the user's CAD drawings. Project generation component <NUM> can generate any suitable code (ladder, function blocks, etc.), device configurations, and visualizations based on analysis of these drawings and markings for incorporation into system project <NUM>. In some embodiments, user interface component <NUM> can include design tools for developing engineering drawings within the IDE platform itself, and the project generation component <NUM> can generate this code as a background process as the user is creating the drawings for a new project. In some embodiments, project generation component <NUM> can also translate state machine drawings to a corresponding programming sequence, yielding at least skeletal code that can be enhanced by the developer with additional programming details as needed.

Also, or in addition, some embodiments of IDE system <NUM> can support goal-based automated programming. For example, the user interface component <NUM> can allow the user to specify production goals for a system being designed (e.g., specifying that a bottling plant being designed must be capable of producing at least <NUM> bottles per second during normal operation) and any other relevant design constraints applied to the design project (e.g., budget limitations, available floor space, available control cabinet space, etc.). Based on this information, the project generation component <NUM> will generate portions of the system project <NUM> to satisfy the specified design goals and constraints. Portions of the system project <NUM> that can be generated in this manner can include, but are not limited to, device and equipment selections (e.g., definitions of how many pumps, controllers, stations, conveyors, drives, or other assets will be needed), associated device configurations (e.g., tuning parameters, network settings, drive parameters, etc.), control coding, or HMI screens suitable for visualizing the automation system being designed.

Some embodiments of project generation component <NUM> can also monitor customer-specific design approaches for commonly programmed functions (e.g., pumping applications, batch processes, etc.) and generate recommendations for design modules (e.g., code modules <NUM>, visualizations <NUM>, etc.) that the user may wish to incorporate into a current design project based on an inference of the designer's goals and learned approaches to achieving the goal. For example, given a set of industrial equipment being programmed, user interface component <NUM> can render recommended development steps or code modules <NUM> the designer may wish to use based on how the designer typically configures and programs this equipment.

In some embodiments, IDE system <NUM> can also store and implement guardrail templates <NUM> that define design guardrails intended to ensure the project's compliance with internal or external design standards. Based on design parameters defined by one or more selected guardrail templates <NUM>, user interface component <NUM> can provide, as a subset of design feedback <NUM>, dynamic recommendations or other types of feedback during project development designed to keep the developer's system project <NUM> within compliance of internal or external requirements or standards (e.g., certifications such as TUV certification, in-house design standards, industry-specific or vertical-specific design standards, etc.). This feedback <NUM> can take the form of text-based recommendations (e.g., recommendations to rewrite an indicated portion of control code to comply with a defined programming standard), syntax highlighting, error highlighting, auto-completion of code snippets, or other such formats. In this way, IDE system <NUM> can customize design feedback <NUM> - including programming recommendations, recommendations of predefined code modules <NUM> or visualizations <NUM>, the types and format of error and syntax highlighting, etc. - in accordance with the type of industrial system being developed and any applicable in-house design standards.

Guardrail templates <NUM> can also be designed to maintain compliance with global best practices applicable to control programming or other aspects of project development. For example, user interface component <NUM> may generate and render an alert if a developer's control programing is deemed to be too complex as defined by criteria specified by one or more guardrail templates <NUM>. Since different verticals (e.g., automotive, pharmaceutical, oil and gas, food and drug, marine, etc.) must adhere to different standards and certifications, the IDE system <NUM> can maintain a library of guardrail templates <NUM> for different internal and external standards and certifications, including customized user-specific guardrail templates <NUM>. These guardrail templates <NUM> can be classified according to industrial vertical, type of industrial application, plant facility (in the case of custom in-house guardrail templates <NUM>) or other such categories. During development, project generation component <NUM> can select and apply a subset of guardrail templates <NUM> determined to be relevant to the project currently being developed, based on a determination of such aspects as the industrial vertical to which the project relates, the type of industrial application being programmed (e.g., flow control, web tension control, a certain batch process, etc.), or other such aspects. Project generation component <NUM> can leverage guardrail templates <NUM> to implement rules-based programming, whereby programming feedback such as dynamic intelligent autocorrection, type-aheads, or coding suggestions are rendered based on industry expertise and best practices (e.g., identifying inefficiencies in code being developed and recommending appropriate corrections).

Users can also run their own internal guardrail templates <NUM> against code provided by outside vendors (e.g., OEMs) to ensure that this code complies with in-house programming standards. In such scenarios, vendor-provided code can be submitted to the IDE system <NUM>, and user interface component <NUM> can analyze this code in view of in-house coding standards specified by one or more custom guardrail templates <NUM>. Based on results of this analysis, user interface component <NUM> can indicate portions of the vendor-provided code (e.g., using highlights, overlaid text, etc.) that do not conform to the programming standards set forth by the guardrail templates <NUM>, and display suggestions for modifying the code in order to bring the code into compliance. As an alternative or in addition to recommending these modifications, some embodiments of project generation component <NUM> can be configured to automatically modify the code in accordance with the recommendations to bring the code into conformance.

In making coding suggestions, project generation component <NUM> can invoke selected code modules <NUM> stored in a code module database (e.g., on memory <NUM>). These code modules <NUM> comprise standardized coding segments for common industrial tasks or applications (e.g., palletizing, flow control, web tension control, pick-and-place applications, etc.). In some embodiments, code modules <NUM> can be categorized according to one or more of an industrial vertical (e.g., automotive, food and drug, oil and gas, textiles, marine, pharmaceutical, etc.), an industrial application, or a type of machine or device to which the code module <NUM> is applicable. In some embodiments, project generation component <NUM> can infer a programmer's current programming task or design goal based on programmatic input being provided by a the programmer, and determine, based on this task or goal, whether one of the pre-defined code modules <NUM> may be appropriately added to the control program being developed to achieve the inferred task or goal. For example, project generation component <NUM> may infer that the programmer is currently developing control code for transferring material from a first tank to another tank, and in response, recommend inclusion of a predefined code module <NUM> comprising standardized code for controlling the valves, pumps, or other assets necessary to achieve the material transfer.

Customized guardrail templates <NUM> can also be defined to capture the nuances of a customer site that should be taken into consideration in the project design. For example, a guardrail template <NUM> could record the fact that the automation system being designed will be installed in a region where power outages are common, and will factor this consideration when generating design feedback <NUM>; e.g., by recommending implementation of backup uninterruptable power supplies and suggesting how these should be incorporated, as well as recommending associated programming or control strategies that take these outages into account.

IDE system <NUM> can also use guardrail templates <NUM> to guide user selection of equipment or devices for a given design goal; e.g., based on the industrial vertical, type of control application (e.g., sheet metal stamping, die casting, palletization, conveyor control, web tension control, batch processing, etc.), budgetary constraints for the project, physical constraints at the installation site (e.g., available floor, wall or cabinet space; dimensions of the installation space; etc.), equipment already existing at the site, etc. Some or all of these parameters and constraints can be provided as design input <NUM>, and user interface component <NUM> can render the equipment recommendations as a subset of design feedback <NUM>. In some embodiments, project generation component <NUM> can also determine whether some or all existing equipment can be repurposed for the new control system being designed. For example, if a new bottling line is to be added to a production area, there may be an opportunity to leverage existing equipment since some bottling lines already exist. The decision as to which devices and equipment can be reused will affect the design of the new control system. Accordingly, some of the design input <NUM> provided to the IDE system <NUM> can include specifics of the customer's existing systems within or near the installation site. In some embodiments, project generation component <NUM> can apply artificial intelligence (AI) or traditional analytic approaches to this information to determine whether existing equipment specified in design in put <NUM> can be repurposed or leveraged. Based on results of this analysis, project generation component <NUM> can generate, as design feedback <NUM>, a list of any new equipment that may need to be purchased based on these decisions.

In some embodiments, IDE system <NUM> can offer design recommendations based on an understanding of the physical environment within which the automation system being designed will be installed. To this end, information regarding the physical environment can be submitted to the IDE system <NUM> (as part of design input <NUM>) in the form of 2D or 3D images or video of the plant environment. This environmental information can also be obtained from an existing digital twin of the plant, or by analysis of scanned environmental data obtained by a wearable AR appliance in some embodiments. Project generation component <NUM> can analyze this image, video, or digital twin data to identify physical elements within the installation area (e.g., walls, girders, safety fences, existing machines and devices, etc.) and physical relationships between these elements. This can include ascertaining distances between machines, lengths of piping runs, locations and distances of wiring harnesses or cable trays, etc. Based on results of this analysis, project generation component <NUM> can add context to schematics generated as part of system project <NUM>, generate recommendations regarding optimal locations for devices or machines (e.g., recommending a minimum separation between power and data cables), or make other refinements to the system project <NUM>. At least some of this design data can be generated based on physics-based rules <NUM>, which can be referenced by project generation component <NUM> to determine such physical design specifications as minimum safe distances from hazardous equipment (which may also factor into determining suitable locations for installation of safety devices relative to this equipment, given expected human or vehicle reaction times defined by the physics-based rules <NUM>), material selections capable of withstanding expected loads, piping configurations and tuning for a given flow control application, wiring gauges suitable for an expected electrical load, minimum distances between signal wiring and electromagnetic field (EMF) sources to ensure negligible electrical interference, or other such design features that are dependent on physical rules.

In an example use case, relative locations of machines and devices specified by physical environment information submitted to the IDE system <NUM> can be used by the project generation component <NUM> to generate design data for an industrial safety system. For example, project generation component <NUM> can analyze distance measurements between safety equipment and hazardous machines and, based on these measurements, determine suitable placements and configurations of safety devices and associated safety controllers that ensure the machine will shut down within a sufficient safety reaction time to prevent injury (e.g., in the event that a person runs through a light curtain).

In some embodiments, project generation component <NUM> can also analyze photographic or video data of an existing machine to determine inline mechanical properties such as gearing or camming and factor this information into one or more guardrail templates <NUM> or design recommendations.

In some embodiments, user interface component <NUM> is associated with a domain-specific language (DSL) editor <NUM> that can allow users to program their own development interfaces for interacting with the IDE system <NUM> and populating the system project <NUM>, as will be discussed in more detail below.

As noted above, the system project <NUM> generated by IDE system <NUM> for a given automaton system being designed can be built upon an object-based architecture that uses automation objects <NUM> as building blocks. <FIG> is a diagram illustrating an example system project <NUM> that incorporates automation objects <NUM> into the project model. In this example, various automation objects <NUM> representing analogous industrial devices, systems, or assets of an automation system (e.g., a process, tanks, valves, pumps, etc.) have been incorporated into system project <NUM> as elements of a larger project data model <NUM>. The project data model <NUM> also defines hierarchical relationships between these automation objects <NUM>. According to an example relationship, a process automation object representing a batch process may be defined as a parent object to a number of child objects representing devices and equipment that carry out the process, such as tanks, pumps, and valves. Each automation object <NUM> has associated therewith object properties or attributes specific to its corresponding industrial asset (e.g., those discussed above in connection with <FIG>), including executable control programming for controlling the asset (or for coordinating the actions of the asset with other industrial assets) and visualizations that can be used to render relevant information about the asset during runtime.

At least some of the attributes of each automation object <NUM> are default properties defined by the IDE system <NUM> based on encoded industry expertise pertaining to the asset represented by the objects. Other properties can be modified or added by the developer as needed (via design input <NUM>) to customize the object <NUM> for the particular asset and/or industrial application for which the system projects <NUM> is being developed. This can include, for example, associating customized control code, HMI screens, AR presentations, or help files associated with selected automation objects <NUM>. In this way, automation objects <NUM> can be created and augmented as needed during design for consumption or execution by target control devices during runtime.

Once development on a system project <NUM> has been completed, commissioning tools supported by the IDE system <NUM> can simplify the process of commissioning the project in the field. When the system project <NUM> for a given automation system has been completed, the system project <NUM> can be deployed to one or more target control devices for execution. <FIG> is a diagram illustrating commissioning of a system project <NUM>. Project deployment component <NUM> can compile or otherwise translate a completed system project <NUM> into one or more executable files or configuration files that can be stored and executed on respective target industrial devices of the automation system (e.g., industrial controllers <NUM>, HMI terminals <NUM> or other types of visualization systems, motor drives <NUM>, telemetry devices, vision systems, safety relays, etc.).

Conventional control program development platforms require the developer to specify the type of industrial controller (e.g., the controller's model number) on which the control program will run prior to development, thereby binding the control programming to a specified controller. Controller-specific guardrails are then enforced during program development which limit how the program is developed given the capabilities of the selected controller. By contrast, some embodiments of the IDE system <NUM> can abstract project development from the specific controller type, allowing the designer to develop the system project <NUM> as a logical representation of the automation system in a manner that is agnostic to where and how the various control aspects of system project <NUM> will run. Once project development is complete and system project <NUM> is ready for commissioning, the user can specify (via user interface component <NUM>) target devices on which respective aspects of the system project <NUM> are to be executed. In response, an allocation engine of the project deployment component <NUM> will translate aspects of the system project <NUM> to respective executable files formatted for storage and execution on their respective target devices.

For example, system project <NUM> may include - among other project aspects - control code, visualization screen definitions, and motor drive parameter definitions. Upon completion of project development, a user can identify which target devices- including an industrial controller <NUM>, an HMI terminal <NUM>, and a motor drive <NUM> - are to execute or receive these respective aspects of the system project <NUM>. Project deployment component <NUM> can then translate the controller code defined by the system project <NUM> to a control program file <NUM> formatted for execution on the specified industrial controller <NUM> and send this control program file <NUM> to the controller <NUM> (e.g., via plant network <NUM>). Similarly, project deployment component <NUM> can translate the visualization definitions and motor drive parameter definitions to a visualization application <NUM> and a device configuration file <NUM>, respectively, and deploy these files to their respective target devices for execution and/or device configuration. In general, project deployment component <NUM> performs any conversions necessary to allow aspects of system project <NUM> to execute on the specified devices. Any inherent relationships, handshakes, or data sharing defined in the system project <NUM> are maintained regardless of how the various elements of the system project <NUM> are distributed. In this way, embodiments of the IDE system <NUM> can decouple the project from how and where the project is to be run. This also allows the same system project <NUM> to be commissioned at different plant facilities having different sets of control equipment. That is, some embodiments of the IDE system <NUM> can allocate project code to different target devices as a function of the particular devices found on-site. IDE system <NUM> can also allow some portions of the project file to be commissioned as an emulator or on a cloud-based controller.

As an alternative to having the user specify the target control devices to which the system project <NUM> is to be deployed, some embodiments of IDE system <NUM> can actively connect to the plant network <NUM> and discover available devices, ascertain the control hardware architecture present on the plant floor, infer appropriate target devices for respective executable aspects of system project <NUM>, and deploy the system project <NUM> to these selected target devices. As part of this commissioning process, IDE system <NUM> can also connect to remote knowledgebases (e.g., web-based or cloud-based knowledgebases) to determine which discovered devices are out of date or require firmware upgrade to properly execute the system project <NUM>. In this way, the IDE system <NUM> can serve as a link between device vendors and a customer's plant ecosystem via a trusted connection in the cloud.

Copies of system project <NUM> can be propagated to multiple plant facilities having varying equipment configurations using smart propagation, whereby the project deployment component <NUM> intelligently associates project components with the correct industrial asset or control device even if the equipment on-site does not perfectly match the defined target (e.g., varying pump types at different sites). For target devices that do not perfectly match the expected asset, project deployment component <NUM> can calculate the estimated impact of running the system project <NUM> on non-optimal target equipment and generate warnings or recommendations for mitigating expected deviations from optimal project execution.

Returning briefly to <FIG>, as an alternative to entering control programming in a graphical industry-standard format such as ladder logic (as a portion of design input <NUM>), some embodiments of user interface component <NUM> can support entry of control programming as a scripted, text-based syntax. In some such embodiments, the scripted language may be a domain-specific language (DSL) customized for industrial control programming. <FIG> is a diagram illustrating control programming using an industrial DSL and compilation of the DSL programming to yield executable industrial code <NUM>. According to these embodiments, user interface component <NUM> is associated with a DSL editor <NUM> that renders a DSL programming interface for entry of industrial DSL script <NUM>. The DSL editor <NUM> also supports associated editor tools <NUM> that provide dynamic assistance during programming. Writing control code using a text-based DSL syntax - allowing programming objects to be described through text - can be preferable to programming with ladder logic or other graphical programming platforms typically used to program automation systems, since experienced programmers can generate code more quickly using text-based programming syntax and associated editor tools <NUM> that require fewer mouse clicks. Editor tools <NUM> supported by the DSL editor <NUM> can include, but are not limited to, error highlighting, syntax highlighting, code snippet management, type-ahead or autocomplete functionality, intelligent programming suggestions, and other such tools. Some or all of these programming services can be provided by a language server <NUM> associated with the DSL editor <NUM>.

In some embodiments, the industrial DSL can reference a logical model defining a hierarchical organization of automation objects, which serves as a namespace for the automation objects and the elements contained within the automation objects. <FIG> is an example automation object namespace hierarchy <NUM> that can be supported by some embodiments of the industrial DSL. This example hierarchical structure of automation objects may comprise a plant level, an area level, a line level, a machine level, and a device level. Under this namespace, an automation object representing a particular tank of a mixing line located within a batching area of a plant can be referenced using the following example name scope: myFaetory. batchingArea. mixingLine. tank101 (assumingtypesformatted using the camel case naming convention). In general, each automation object <NUM> within the hierarchy defines a unique name scope, which is the union of the object's name plus the names of its parent automation objects.

In addition to automation objects <NUM> representing devices (e.g., industrial controllers, drives, HMI terminals, optical safety devices, etc.), machines, production areas, or other industrial assets, IDE system <NUM> can also support automation objects <NUM> representing elements of a control program, including but not limited to the program itself as well as add-on instructions, data tags, ladder logic routines or rungs, or other such programmatic elements within the program. For example, a control program that facilitates control of a tank (tank101) within a specified production area (Area1) may be referenced within the DSL namespace as Areal. tankProgram.

Similarly, automation objects <NUM> can be defined that represent visualizations elements, such as HMI screens, pop-up windows, augmented reality overlays, etc. Such visualization automation objects <NUM> can be bound to a parent automaton object <NUM> representing the industrial asset with which the visualization is to be associated. For example, a screen automation object <NUM> representing an HMI screen for visualizing a tank can be defined within the DSL namespace as a child object of the tank's (parent) automation object. The HMI screen automation object <NUM> can be written to define the dimensions, colors (e.g., background color, font color, etc.), text, or other such properties of the screen.

Any type of application that can be deployed to an industrial device - e.g., control programs, HMI applications, motor drive applications, batch control applications, etc. - can be associated with its own automation object <NUM> defined within the DSL namespace and bound to its appropriate parent automation object (representing the target device or asset on which the application will run). In some embodiments, elements within an application - e.g., tags, rungs, routines, tasks, HMI graphical elements, etc. - can be referenced using a different namespace than that used for physical industrial assets, or using a nested namespace within the greater asset namespace. For example, <FIG> is another example automation object namespace hierarchy <NUM> for control application elements, which can be supported by some embodiments of the namespace DSL. This example control application namespace comprises a control device level. a task level, a program level, and a tag level. Under this namespace, an automation object representing a tag (e.g., tagA) defined in a control program can be referenced using the following example name scope: myController1. mainProgram. The application namespace <NUM> can be nested within the asset namespace <NUM> in some embodiments, such that automation objects <NUM> for an application element defined in namespace <NUM> can be associated with a device defined in namespace <NUM>.

Automation objects <NUM> can also represent other elements of a control system or industrial environment, such as control loops, safety zones, lot traceability systems, or other such elements.

Some or all of these automation objects <NUM> can be defined by the logical model associated with the industrial DSL and can therefore be referenced via the DSL's hierarchical namespace. DSL editor <NUM> can also allow users to define custom automation objects <NUM> and incorporate these custom objects <NUM> into the editor's logical model (e.g., at specified locations within the namespace hierarchy).

A given automation object definition can define the inputs, logic (e.g., inline logic definitions or externally specified logic), outputs, and any of the properties or attributes described above in connection with <FIG>. These properties and attributes may be specified inline or may be linked to the automation object via a scripted link to an external source (e.g. a support document for an industrial asset represented by the automation object). These object definitions can be written and called within the industrial DSL editor <NUM>.

In addition to intrinsic data types such as integers, double integers, Boolean, floating point, etc., DSL editor <NUM> can also support definition of data types specific to industrial automation applications, including but not limited to screens (representing HMI screens), add-on graphics, automation objects, devices (e.g., automation devices such as controllers, drives, telemetry devices, etc.), projects, models, applications (e.g., applications that can be deployed to a device for execution, such as control logic, analytics applications, power monitoring applications, etc.), programs, parameter connections, tasks, tags (e.g., controller tags), or other such data types. The DSL editor <NUM> allows instances of these types to be created for inclusion in a system project <NUM>. Instances of each type may have certain properties or members that are a function of the type.

The industrial DSL supported by the DSL editor <NUM> can provide programmatic guardrails based on known relationships between industrial entities represented by automation objects (e.g., controllers, tags, HMIs, motor drives, tanks, valves, etc.), and editor tools <NUM> can guide the project development workflow based on these known relationships. This can include, for example, identifying when a parent automation object <NUM> (e.g., a tank automation object) has been invoked within the DSL program and rendering possible child automation objects <NUM> (e.g., valves, pumps, etc.) associated with the parent object that the user may wish to reference.

DSL editor <NUM> allows a user to program any aspects of the system project <NUM> using a customizable industrial DSL script <NUM>. The DSL editor's parser <NUM> can then parse this DSL script <NUM> to yield a hierarchical model (e.g., an abstract syntax tree or another model format) of the program. The DSL editor's compiler <NUM> can then translate this hierarchical model to industrial code <NUM> (including any automation objects <NUM> defined by the DSL script <NUM>) that is understandable and executable by an industrial control device (e.g., a programmable logic controller or another type of industrial control device). The resulting industrial code <NUM> can then be added to system project <NUM> or deployed directly to the target control device. In general, the DSL editor <NUM> can map the industrial DSL to a structured language understandable by the target industrial control equipment.

In some embodiments, IDE system <NUM> can include application programming interfaces (APIs) that allow third parties - such as OEMs, system integrators, industrial asset owners, or other such users - to program their own development interfaces and customize their own DSLs for interacting with the IDE system's development platform and populating a system project <NUM>. <FIG> is a diagram illustrating customization of the IDE system's programming interface according to one or more embodiments. In this example, the user interface component <NUM> and DSL editor <NUM> can be associated with an editor definition component <NUM> that can modify the DSL editor's programming interfaces based on DSL definitions <NUM> submitted by a user. The editor definition component <NUM> allows the user to define or modify the syntax of the industrial DSL supported by the DSL editor <NUM>, define objects (e.g., automation objects) to be included in the DSL's logical model as well as relationships between these objects, define one or more of the editor tools <NUM> for guiding the developer through the programming workflow, or define other such features of the programming interface. Editor definition component <NUM> can update the DSL editor <NUM> based on these DSL definitions <NUM> to thereby customize the IDE's development interface in accordance with user requirements or preferences. In this way, the industrial DSL can be used to extend the IDE platform to third-party users, allowing users to define their own language script that can be translated and compiled into industrial code <NUM> that can be executed on industrial equipment. By allowing users to define the syntax and editor tools <NUM> (error highlights, syntax highlighting, automated recommendation, guardrails, etc.), the look and feel of the DSL editor's interface for generating industrial control code can be customized by end users.

<FIG> is a block diagram illustrating components of an example editor definition component <NUM> according to one or more embodiments. In an example implementation, a software development kit (SDK) <NUM> and/or associated libraries <NUM> can be licensed that allows users (e.g., OEMs or system integrators) to build their own DSL editor <NUM>, build extensions, access the logical model, and add to system projects <NUM>. The APIs <NUM> can allow users to create their own language script as a customized industrial DSL, which can then be parsed and compiled (e.g., by parser <NUM> and compiler <NUM> of the DSL editor <NUM>) to executable control code that is understandable and executable by industrial control devices. A translator <NUM> between the APIs <NUM> and the IDE development platform can expose the system project <NUM> and allow users to write their own control code and customize the DSL editor <NUM>.

In some embodiments, the IDE system <NUM> can also allow a user to install a plug-in for a known programming language - such as Python, C, structured text, etc. - and allow the user to develop industrial code in this language. In such scenarios, the plug-in can map the selected programming language to control code understandable and executable by industrial controllers, HMIs, or other industrial devices. In this way, the DSL editor <NUM> allows the user to develop industrial control code in a preferred programming language, and can compile the customer's code into a form that the IDE system <NUM> - and an industrial control device - can understand.

In some embodiments, IDE system <NUM> can support industrial programming languages such as ladder logic, and editor definition component <NUM> can allow users to customize the ladder logic development environment according to their preferences. This can include altering the native nomenclature of the ladder logic editor to preferred nomenclature preferred by the user. For example, DSL definitions <NUM> submitted by the user can include nomenclature mapping definitions that map the ladder logic editor's native nomenclature to preferred nomenclature specified by the user. In an example scenario, the function for moving a data value from a source register to a destination register may be referred to as a MOV command in the editor's native nomenclature. To add this functionality to a control program, users must select and add a MOV function block to a rung output of their ladder logic program. Since the name of this function block may be considered ambiguous to some programmers, a user may wish to change the name of this function block to MOVE to more explicitly convey the function associated with this command. Accordingly, the editor definition component <NUM> can allow the user to change the name of this command from MOV to MOVE by submitting DSL definitions <NUM> that define this nomenclature mapping. Once this mapping has been defined, all instances of the MOV command will be labeled MOVE within the ladder logic editing environment. Other aspects of the ladder logic editor, including but not limited to text or rung colors, function block dimensions or sizes, locations and visibility of toolbars, or other such features can also be customized in this manner.

As noted above, some embodiments of IDE system <NUM> can be embodied on a cloud platform. <FIG> is a diagram illustrating an example architecture in which cloud-based IDE services <NUM> are used to develop and deploy industrial applications to a plant environment. In this example, the industrial environment includes one or more industrial controllers <NUM>, HMI terminals <NUM>, motor drives <NUM>, servers <NUM> running higher level applications (e.g., ERP, MES, etc.), and other such industrial assets. These industrial assets are connected to a plant network <NUM> (e.g., a common industrial protocol network, an Ethernet/IP network, etc.) that facilitates data exchange between industrial devices on the plant floor. Plant network <NUM> may be a wired or a wireless network. In the illustrated example, the high-level servers <NUM> reside on a separate office network <NUM> that is connected to the plant network <NUM> (e.g., through a router <NUM> or other network infrastructure device).

In this example, IDE system <NUM> resides on a cloud platform <NUM> and executes as a set of cloud-based IDE service <NUM> that are accessible to authorized remote client devices <NUM>. Cloud platform <NUM> can be any infrastructure that allows shared computing services (such as IDE services <NUM>) to be accessed and utilized by cloud-capable devices. Cloud platform <NUM> can be a public cloud accessible via the Internet by devices <NUM> having Internet connectivity and appropriate authorizations to utilize the IDE services <NUM>. In some scenarios, cloud platform <NUM> can be provided by a cloud provider as a platform-as-a-service (PaaS), and the IDE services <NUM> can reside and execute on the cloud platform <NUM> as a cloud-based service. In some such configurations, access to the cloud platform <NUM> and associated IDE services <NUM> can be provided to customers as a subscription service by an owner of the IDE services <NUM>. Alternatively, cloud platform <NUM> can be a private cloud operated internally by the industrial enterprise (the owner of the plant facility). An example private cloud platform can comprise a set of servers hosting the IDE services <NUM> and residing on a corporate network protected by a firewall.

Cloud-based implementations of IDE system <NUM> can facilitate collaborative development by multiple remote developers who are authorized to access the IDE services <NUM>. When a system project <NUM> is ready for deployment, the project <NUM> can be commissioned to the plant facility via a secure connection between the office network <NUM> or the plant network <NUM> and the cloud platform <NUM>. As discussed above, the industrial IDE services <NUM> can translate system project <NUM> to appropriate executable files - control program files <NUM>, visualization applications <NUM>, device configuration files <NUM>, system configuration files <NUM> - and deploy these files to the appropriate devices in the plant facility to facilitate implementation of the automation project.

Although features of the industrial DSL have been described herein in the context of IDE systems <NUM> having features discussed in connection with <FIG>, it is to be appreciated that the DSL editor <NUM> and associated editor definition component <NUM> described herein can be components of other types of IDEs that omit some or all of the features described in connection with <FIG>. That is, any IDE for development of industrial control code that supports the use of industrial DSLs, and customization thereof, is within the scope of one or more embodiments of this disclosure.

The industrial DSL and associated DSL editor and editor definition component render development of industrial control code more efficient relative to ladder logic platforms or other industrial development platforms, allowing programmers to generate industrial control code using a script-based DSL requiring fewer mouse clicks relative to traditional control programming environments. Dynamic feedback provided by the IDE's editing tools associated can guide the developer through the process of developing control code that is in compliance with industry or in-house standards.

<FIG> illustrate various methodologies in accordance with one or more embodiments of the subject application. While, for purposes of simplicity of explanation, the one or more methodologies shown herein are shown and described as a series of acts, it is to be understood and appreciated that the subject innovation is not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the innovation. Furthermore, interaction diagram(s) may represent methodologies, or methods, in accordance with the subject disclosure when disparate entities enact disparate portions of the methodologies. Further yet, two or more of the disclosed example methods can be implemented in combination with each other, to accomplish one or more features or advantages described herein.

<FIG> illustrates an example methodology <NUM> for developing industrial control programming. In some embodiments methodology <NUM> can be implemented on an industrial IDE that provides a development platform for designing and programming industrial control projects. Initially, at <NUM>, industrial control programming is received as an industrial domain-specific language (DSL). The industrial DSL can be, for example, a scripted language that supports creation of automation objects representing industrial processes, assets, devices, machines, etc., and having relationships defined by an automation object namespace hierarchy. At <NUM>, programing suggestions are rendered in accordance with industry-specific guardrails as the industrial control programming is received. Example suggestions can include, for example, suggested automation objects to be added to the project based on an inference of the programmer's intentions (e.g., recommending addition of a pump automation object at an appropriate location in the program if the developer is scripting a flow control application), auto-completing sections of code by adding predefined vertical-specific or application-specific code modules for common control operations, enforcing preferred in-house or industry-standard coding practices via error highlighting or syntax highlighting, or other such suggestions.

At <NUM>, a determination is made as to whether programming is complete. This determination may be made, for example, in response to an indication from the programmer that the industrial DSL program is ready to be parsed and compiled. If the programming is not complete (NO at step <NUM>) the methodology returns to step <NUM>. Steps <NUM> and <NUM> are repeated until programming is complete (YES at step <NUM>), at which time the methodology proceeds to step <NUM>.

At <NUM>, the industrial DSL programming received at step <NUM> is parsed to yield a hierarchical model of the industrial program. At <NUM>, the hierarchical model obtained at step <NUM> is compiled to yield industrial control programming having a format that can be executed on one or more industrial control devices. At <NUM>, the industrial control programming obtained at step <NUM> is deployed to the one or more industrial control devices for execution of the control project.

<FIG> illustrates an example methodology <NUM> for customizing a programming interface of an industrial IDE. At <NUM>, DSL definition data defining an industrial DSL for use in developing industrial control projects is received. The DSL definition data can specify, for example, a syntax of the industrial DSL, definitions of automation objects that can be called within the industrial DSL (e.g., automation objects representing industrial assets such as machines, processes, controllers, drives, control programs, controller tags, etc.), parent-child relationships between the automation objects, namespaces, mapping of programming nomenclature, programming guardrails, code modules for frequently programmed control tasks or applications (e.g., pumping applications, conveyor control applications, web tension control applications, etc.), or other such aspects of the industrial DSL. At <NUM>, the development interface of the industrial IDE is customized in accordance with the DSL definition data received at step <NUM>. The methodology can then proceed to methodology <NUM> described above in connection with <FIG>, with steps <NUM> and <NUM> carried out in accordance with the customized industrial DSL defined by methodology <NUM>. That is, the industrial DSL received at step <NUM> and programming suggestions rendered at step <NUM> can be defined at least in part by the DSL definition data received at step <NUM>.

Embodiments, systems, and components described herein, as well as control systems and automation environments in which various aspects set forth in the subject specification can be carried out, can include computer or network components such as servers, clients, programmable logic controllers (PLCs), automation controllers, communications modules, mobile computers, on-board computers for mobile vehicles, wireless components, control components and so forth which are capable of interacting across a network. Computers and servers include one or more processors-electronic integrated circuits that perform logic operations employing electric signals-configured to execute instructions stored in media such as random access memory (RAM), read only memory (ROM), a hard drives, as well as removable memory devices, which can include memory sticks, memory cards, flash drives, external hard drives, and so on.

Similarly, the term PLC or automation controller as used herein can include functionality that can be shared across multiple components, systems, and/or networks. As an example, one or more PLCs or automation controllers can communicate and cooperate with various network devices across the network. This can include substantially any type of control, communications module, computer, Input/Output (I/O) device, sensor, actuator, and human machine interface (HMI) that communicate via the network, which includes control, automation, and/or public networks. The PLC or automation controller can also communicate to and control various other devices such as standard or safety-rated I/O modules including analog, digital, programmed/intelligent I/O modules, other programmable controllers, communications modules, sensors, actuators, output devices, and the like.

The network can include public networks such as the internet, intranets, and automation networks such as control and information protocol (CIP) networks including DeviceNet, ControlNet, safety networks, and Ethernet/IP. Other networks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus, Profibus, CAN, wireless networks, serial protocols, and so forth. In addition, the network devices can include various possibilities (hardware and/or software components). These include components such as switches with virtual local area network (VLAN) capability. LANs, WANs, proxies, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, and/or other devices.

In order to provide a context for the various aspects of the disclosed subject matter, <FIG> and <FIG> as well as the following discussion are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter may be implemented. While the embodiments have been described above in the general context of computer-executable instructions that can run on one or more computers, those skilled in the art will recognize that the embodiments can be also implemented in combination with other program modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other computer system configurations, including single-processor or multiprocessor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like. each of which can be operatively coupled to one or more associated devices.

The illustrated embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which can include computer-readable storage media, machine-readable storage media, and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media or machine-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable or machine-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can include, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD), Blu-ray disc (BD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, solid state drives or other solid state storage devices, or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms "tangible" or "non-transitory" herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and includes any information delivery or transport media. The term "modulated data signal" or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media include wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to <FIG>, the example environment <NUM> for implementing various embodiments of the aspects described herein includes a computer <NUM>, the computer <NUM> including a processing unit <NUM>, a system memory <NUM> and a system bus <NUM>. The system bus <NUM> couples system components including, but not limited to, the system memory <NUM> to the processing unit <NUM>. The processing unit <NUM> can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit <NUM>.

The system bus <NUM> can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus. and a local bus using any of a variety of commercially available bus architectures. The system memory <NUM> includes ROM <NUM> and RAM <NUM>. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer <NUM>, such as during startup. The RAM <NUM> can also include a highspeed RAM such as static RAM for caching data.

The computer <NUM> further includes an internal hard disk drive (HDD) <NUM> (e.g., EIDE, SATA), one or more external storage devices <NUM> (e.g., a magnetic floppy disk drive (FDD) <NUM>, a memory stick or flash drive reader, a memory card reader, etc.) and an optical disk drive <NUM> (e.g., which can read or write from a CD-ROM disc, a DVD, a BD, etc.). While the internal HDD <NUM> is illustrated as located within the computer <NUM>, the internal HDD <NUM> can also be configured for external use in a suitable chassis (not shown). Additionally, while not shown in environment <NUM>, a solid state drive (SSD) could be used in addition to, or in place of, an HDD <NUM>. The HDD <NUM>, external storage device(s) <NUM> and optical disk drive <NUM> can be connected to the system bus <NUM> by an HDD interface <NUM>, an external storage interface <NUM> and an optical drive interface <NUM>, respectively. The interface <NUM> for external drive implementations can include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) <NUM> interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer <NUM>, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to respective types of storage devices, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, whether presently existing or developed in the future, could also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM <NUM>, including an operating system <NUM>, one or more application programs <NUM>, other program modules <NUM> and program data <NUM>. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM <NUM>. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

Computer <NUM> can optionally comprise emulation technologies. For example, a hypervisor (not shown) or other intermediary can emulate a hardware environment for operating system <NUM>, and the emulated hardware can optionally be different from the hardware illustrated in <FIG>. In such an embodiment, operating system <NUM> can comprise one virtual machine (VM) of multiple VMs hosted at computer <NUM>. Furthermore, operating system <NUM> can provide runtime environments, such as the Java runtime environment or the. NET framework, for application programs <NUM>. Runtime environments are consistent execution environments that allow application programs <NUM> to run on any operating system that includes the runtime environment. Similarly, operating system <NUM> can support containers, and application programs <NUM> can be in the form of containers, which are lightweight, standalone, executable packages of software that include, e.g., code, runtime, system tools, system libraries and settings for an application.

Further, computer <NUM> can be enable with a security module, such as a trusted processing module (TPM). For instance with a TPM, boot components hash next in time boot components, and wait for a match of results to secured values, before loading a next boot component. This process can take place at any layer in the code execution stack of computer <NUM>, e.g., applied at the application execution level or at the operating system (OS) kernel level, thereby enabling security at any level of code execution.

A user can enter commands and information into the computer <NUM> through one or more wired/wireless input devices, e.g., a keyboard <NUM>, a touch screen <NUM>, and a pointing device, such as a mouse <NUM>. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, or other remote control, a joystick, a virtual reality controller and/or virtual reality headset, a game pad, a stylus pen, an image input device, e.g., camera(s), a gesture sensor input device, a vision movement sensor input device, an emotion or facial detection device, a biometric input device, e.g., fingerprint or iris scanner, or the like. These and other input devices are often connected to the processing unit <NUM> through an input device interface <NUM> that can be coupled to the system bus <NUM>, but can be connected by other interfaces, such as a parallel port, an IEEE <NUM> serial port, a game port, a USB port, an IR interface, a BLUETOOTH® interface, etc..

A monitor <NUM> or other type of display device can be also connected to the system bus <NUM> via an interface, such as a video adapter <NUM>. In addition to the monitor <NUM>, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc..

The computer <NUM> can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) <NUM>. The remote computer(s) <NUM> can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer <NUM>, although, for purposes of brevity, only a memory/storage device <NUM> is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN) <NUM> and/or larger networks, e.g., a wide area network (WAN) <NUM>. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer <NUM> can be connected to the local network <NUM> through a wired and/or wireless communication network interface or adapter <NUM>. The adapter <NUM> can facilitate wired or wireless communication to the LAN <NUM>, which can also include a wireless access point (AP) disposed thereon for communicating with the adapter <NUM> in a wireless mode.

When used in a WAN networking environment, the computer <NUM> can include a modem <NUM> or can be connected to a communications server on the WAN <NUM> via other means for establishing communications over the WAN <NUM>, such as by way of the Internet. The modem <NUM>, which can be internal or external and a wired or wireless device, can be connected to the system bus <NUM> via the input device interface <NUM>. In a networked environment, program modules depicted relative to the computer <NUM> or portions thereof, can be stored in the remote memory/storage device <NUM>. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

When used in either a LAN or WAN networking environment, the computer <NUM> can access cloud storage systems or other network-based storage systems in addition to, or in place of, external storage devices <NUM> as described above. Generally, a connection between the computer <NUM> and a cloud storage system can be established over a LAN <NUM> or WAN <NUM> e.g., by the adapter <NUM> or modem <NUM>, respectively. Upon connecting the computer <NUM> to an associated cloud storage system, the external storage interface <NUM> can, with the aid of the adapter <NUM> and/or modem <NUM>, manage storage provided by the cloud storage system as it would other types of external storage. For instance, the external storage interface <NUM> can be configured to provide access to cloud storage sources as if those sources were physically connected to the computer <NUM>.

The computer <NUM> can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, store shelf, etc.), and telephone. This can include Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

<FIG> is a schematic block diagram of a sample computing environment <NUM> with which the disclosed subject matter can interact. The sample computing environment <NUM> includes one or more client(s) <NUM>. The client(s) <NUM> can be hardware and/or software (e.g., threads, processes, computing devices). The sample computing environment <NUM> also includes one or more server(s) <NUM>. The server(s) <NUM> can also be hardware and/or software (e.g., threads, processes, computing devices). The servers <NUM> can house threads to perform transformations by employing one or more embodiments as described herein, for example. One possible communication between a client <NUM> and servers <NUM> can be in the form of a data packet adapted to be transmitted between two or more computer processes. The sample computing environment <NUM> includes a communication framework <NUM> that can be employed to facilitate communications between the client(s) <NUM> and the server(s) <NUM>. The client(s) <NUM> are operably connected to one or more client data store(s) <NUM> that can be employed to store information local to the client(s) <NUM>. Similarly, the server(s) <NUM> are operably connected to one or more server data store(s) <NUM> that can be employed to store information local to the servers <NUM>.

What has been described above includes examples of the subject innovation. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the disclosed subject matter, but one of ordinary skill in the art may recognize that many further combinations and permutations of the subject innovation are possible. Accordingly, the disclosed subject matter is intended to embrace all such alterations, modifications, and variations that fall within the scope of the appended claims.

In particular and in regard to the various functions performed by the above described components, devices, circuits, systems and the like, the terms (including a reference to a "means") used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., a functional equivalent), even though not structurally equivalent to the disclosed structure, which performs the function in the herein illustrated exemplary aspects of the disclosed subject matter. In this regard, it will also be recognized that the disclosed subject matter includes a system as well as a computer-readable medium having computer-executable instructions for performing the acts and/or events of the various methods of the disclosed subject matter.

In addition, while a particular feature of the disclosed subject matter may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms "includes," and "including" and variants thereof are used in either the detailed description or the claims, these terms are intended to be inclusive in a manner similar to the term "comprising.

In this application, the word "exemplary" is used to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion.

Claim 1:
A system for developing industrial control programming, comprising:
a memory (<NUM>) that stores executable components; and
a processor (<NUM>), operatively coupled to the memory, that is configured to execute the executable components, the executable components comprising:
a user interface component (<NUM>) configured to receive (<NUM>) industrial control programming formatted as an industrial domain-specific language, DSL, and to render (<NUM>) programming feedback in response to receipt of the industrial control programming, wherein the user interface component is configured to generate the programming
feedback based on industry-specific guardrail definitions, and wherein the programming feedback comprises at least one of a programming recommendation, an auto-completion, an error highlight, or a syntax highlight that facilitates compliance of the industrial control programming with an industry-specific standard defined by the industry-specific guardrail definitions; and
a DSL editor (<NUM>) configured to parse (<NUM>) the industrial control programming, formatted as the industrial DSL, to yield a hierarchical model of the industrial control programming and to compile (<NUM>) the hierarchical model to yield industrial control code that is executable on an industrial control device (<NUM>), wherein the DSL editor (<NUM>) is configured to select, from a library of pre-defined code modules (<NUM>), a code module inferred to be relevant to an inferred current programming task, the current programming task being inferred based on the received industrial control programming, and
wherein the programming feedback further comprises a recommendation to add the code module to the industrial control programming based on the inference of the current programming task.