System Model Smart Object Configuration

Abstract

The present invention provides a system model intelligent object configuration. An industrial integrated development environment (IDE) provides a development framework for designing, programming, and configuring multiple aspects of industrial automation systems using a general design environment and a data model. Projects created using an implementation of the IDE system can be built on an object-based model instead of being built on a tag-based architecture; or in addition to projects created using an implementation of the IDE system being built on a tag-based architecture, projects created using an implementation of the IDE system can also be built on an object-based model. To this end, the IDE system can support the use of automation objects used as building blocks of the object-based development structure. A project data model that defines a collection of automation objects and their functional relationships can be stored in a model library for selective inclusion in a system project.

Description

Technical Field

[0001] The subject matter disclosed herein relates generally to industrial automation systems and, for example, to industrial programming development platforms. Background Art

[0002] The need to use separate configuration tools to program and configure different aspects of industrial automation systems has led to a fragmented design approach, whereby different but related or overlapping aspects of the automation system are designed, configured, and programmed separately on different development environments. For example, a motion control system may require the use of a control logic programming platform to program the industrial controller and tune the control loops, another configuration platform to configure the motor drive, and a visualization development platform to program the associated HMI. Related peripheral systems - such as vision systems, safety systems, etc. - may also need to be configured using separate programming or development applications.

[0003] This separate development approach may also require considerable testing and debugging efforts to ensure proper integration of the separately configured system aspects. In this regard, the expected data interfaces or coordinated actions between the different system aspects may require extensive debugging due to failure to properly coordinate the different programming efforts. Summary of the invention

[0004] A simplified overview is presented below to provide a basic understanding of some aspects described herein. This overview is not an extensive review, nor is it intended to identify key / important elements or to describe the scope of various aspects described herein. Its sole purpose is to present some concepts in a simplified form as a prelude to a more detailed description presented later.

[0005] In one or more embodiments, a system for developing industrial applications is provided, the system comprising: a memory storing a library of executable components and automation objects representing corresponding industrial assets, the automation objects having corresponding programming properties associated with the industrial assets; a user interface component configured to: present an integrated development environment (IDE) interface and receive industrial design inputs defining various aspects of an industrial automation project via interaction with the IDE interface; and a project generation component configured to generate system project data based on the industrial design inputs, wherein the system project data defines a system project, the system project comprising at least one of an executable industrial control program, an industrial visualization application, or industrial equipment configuration data, and the system project data comprises a project data model corresponding to an industrial machine or process, the project data model defining a subset of automation objects corresponding to the industrial assets constituting the industrial machine or process and functional relationships between the subsets of automation objects.

[0006] In addition, one or more embodiments provide a method for developing industrial applications, the method comprising: presenting an integrated development environment (IDE) interface on a client device by a system including a processor; receiving industrial design inputs defining various aspects of an industrial control and monitoring project by the system via interaction with the IDE interface; and generating system project data by the system based on the industrial design inputs, the system project data comprising at least one of an executable industrial control program, an industrial visualization application, or industrial equipment configuration data, wherein the system project data comprises a project data model corresponding to an industrial machine or process, the project data model defines a collection of automation objects representing industrial assets constituting the industrial machine or process and functional relationships between the collection of automation objects, and the automation objects in the collection of automation objects have programming properties associated with their corresponding industrial assets.

[0007] In addition, according to one or more embodiments, a non-transitory computer-readable medium is provided, on which instructions are stored, and the instructions, in response to execution, cause the system to perform operations, the operations including: presenting an integrated development environment (IDE) interface on a client device; receiving industrial design input that defines control design aspects of an industrial automation project from the client device via interaction with the IDE interface; and generating system project data based on the industrial design input, wherein the generation includes: generating at least one of an executable industrial control program, an industrial visualization application, or industrial equipment configuration data, the system project data including a project data model, the project data model represents an industrial machine or process based on a collection of automation objects and functional relationships between the collection of automation objects, the collection of automation objects representing industrial assets that constitute the industrial machine or process; and the automation objects in the collection of automation objects have programming properties associated with their corresponding industrial assets.

[0008] To achieve the aforementioned and related purposes, certain illustrative aspects are described herein in conjunction with the following description and accompanying drawings. These aspects indicate various ways in which they can be practiced, all of which are intended to be included herein. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 is a block diagram of an example industrial control environment.

[0010] Figure 2 is a block diagram of an example integrated development environment (IDE) system.

[0011] Figure 3 is a diagram showing the general architecture of an industrial IDE system.

[0012] Figure 4is a diagram illustrating several example automation object properties that may be utilized by an industrial IDE system in connection with building, deploying, and executing system projects.

[0013] Figure 5 is a diagram illustrating an example data flow associated with using an industrial IDE system to create a system project for an automation system being designed.

[0014] Figure 6 is a diagram of an example system project that illustrates incorporating automation objects into a project model.

[0015] Figure 7 It is a diagram showing debugging of a system item.

[0016] Figure 8 is a diagram illustrating an example architecture in which a cloud-based IDE service is used to develop and deploy industrial applications to a factory environment.

[0017] Fig. 9 is a diagram of an example automation object that has been integrated into the project data model of a system project.

[0018] Fig.10 is a diagram showing testing of an example system project by a project test component of an IDE system using a test script bundled with an automation object.

[0019] Fig.11 is a diagram illustrating submission of automation object editing to an IDE system.

[0020] Fig.12 is a diagram illustrating modification of an instance of an automation object according to edits submitted to a master version of the automation object stored in a library.

[0021] Fig.13 is a diagram illustrating downloading a copy of a system project from an industrial IDE system to a local client device.

[0022] Fig.14 is a diagram illustrating propagation of automation object edits to a locally stored copy of a system project.

[0023] Fig.15 is a diagram illustrating selection of a predefined project data model from a model library.

[0024] Fig.16 is a diagram illustrating the creation and storage of a custom data model.

[0025] Fig.17 is a flow chart of an example method for creating and storing a project data model that defines an arrangement of automation objects representing an industrial machine or process, which can be incorporated into an industrial system project.

[0026] Fig.18 is a flow chart of an example method for selectively integrating a system data model into an industrial system project based on inferences about the industrial machine or process for which the project is being developed.

[0027] Fig.19 is a sample computing environment.

[0028] Fig. 20 is a sample networking environment. DETAILED DESCRIPTION

[0029] The present disclosure is now described with reference to the accompanying drawings, in which similar reference numerals are used to refer to similar elements throughout. In the following description, for illustrative purposes, many specific details are set forth to provide a thorough understanding of the present disclosure. However, it is apparent that the present disclosure can be practiced without these specific details. In other examples, known structures and devices are shown in block diagram form to facilitate description thereof.

[0030] 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 as a part of an operating device having one or more specific functions, wherein such an entity can be hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to: a process running on a processor, a processor, a hard drive, a plurality of storage drives (optical storage media or magnetic storage media) including fixed (e.g., fixed with screws or bolts) or removable fixed solid-state storage drives; an object; an executable file; a thread of execution; a computer executable program and / or a computer. As an illustration, a server and an application running on a server can be a component. One or more components can reside within an executing process and / or thread, and a component can be located on one computer and / or distributed between two or more computers. In addition, the components described herein can be executed from various computer-readable storage media having various data structures stored thereon. These components can communicate via local and / or remote processes, for example, according to a signal with one or more data packets (e.g., data from a component that interacts with another component in a local system, a distributed system, and / or interacts with other systems via a signal through a network such as the Internet). As another example, a component can be a device with a specific function provided by a mechanical component operated by an electrical or electronic circuit system, which is operated by a software or firmware application executed by a processor, wherein the processor can be inside or outside the device and execute at least a part of the software or firmware application. As another example, a component can be a device that provides a specific function by an electronic component rather than a mechanical component, in which the electronic component can include a processor to execute software or firmware that at least partially provides the function of the electronic component. As another example, (one or more) interfaces may include input / output (I / O) components and associated processors, applications, or application programming interface (API) components. Although the aforementioned examples are directed to various aspects of components, the illustrated aspects or features may also be applied to systems, platforms, interfaces, layers, controllers, terminals, etc.

[0031] As used herein, the terms "infer" and "inference" generally refer to the process of reasoning or inferring the state of a system, environment, and / or user based on a set of observations captured via events and / or data. For example, inference can be used to identify a specific context or action, or a probability distribution of states can be generated. Inference can be probabilistic, that is, a probability distribution of states of interest is calculated based on a consideration of data and events. Inference can also refer to techniques for composing higher-level events from a set of events and / or data. Such inferences result in the construction of new events or actions from a set of observed events and / or stored event data, regardless of whether the events are closely related in temporal proximity, and regardless of whether the events and data come from one or several event and data sources.

[0032] Additionally, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless specified otherwise or clear from the context, the phrase "X employs A or B" is intended to mean any of the natural inclusive permutations. That is, the phrase "X employs A or B" is satisfied by any of the following: X employs A; X employs B; or X employs both A and B. Furthermore, the articles "a" and "an" as used in this application and the appended claims should generally be construed to mean "one or more" unless specified otherwise or clear from the context that the article refers to the singular.

[0033] Furthermore, the term "set" as used herein excludes an empty set, e.g., a set with no elements therein. Thus, a "set" in the present 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 used herein refers to a collection of one or more entities, e.g., a set of nodes refers to one or more nodes.

[0034] Various aspects or features will be presented in terms of systems that may include multiple devices, components, modules, etc. It should 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 conjunction with the figures. Combinations of these methods may also be used.

[0035] Figure 11 is a block diagram of an example industrial control environment 100. In this example, multiple industrial controllers 118 are deployed throughout the industrial plant environment to monitor and control corresponding industrial systems or processes related to product manufacturing, processing, motion control, batch processing, material handling, or other such industrial functions. The industrial controller 118 typically executes a corresponding control program to facilitate monitoring and control of industrial devices 120 (e.g., industrial machines) that constitute the controlled industrial assets or systems. One or more industrial controllers 118 may also include a soft controller executed on a personal computer or other hardware platform or on a cloud platform. Some hybrid devices may also combine controller functions with other functions (e.g., visualization). The control program executed by the industrial controller 118 may include substantially any type of code capable of processing input signals read from the industrial device 120 and controlling output signals generated by the industrial controller 118, including but not limited to ladder logic, sequential function charts, function block diagrams, or structured text.

[0036] Industrial devices 120 may include input devices that provide data related to the controlled industrial system to industrial controller 118, and output devices that respond to control signals generated by industrial controller 118 for controlling aspects of the industrial system. Example input devices may include telemetry devices (e.g., temperature sensors, flow meters, level sensors, pressure sensors, etc.), manual operator control devices (e.g., 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, robotic control inputs, valves, pumps, etc.

[0037] The industrial controller 118 can be communicatively interfaced with the industrial device 120 via a hardwired connection or a networked connection. For example, the industrial controller 118 can be equipped with local hardwired inputs and outputs that communicate with the industrial device 120 to achieve control of these devices. The local controller I / O may include: digital I / O, which sends discrete voltage signals to and receives discrete voltage signals from field devices; or analog I / O, which sends analog voltage or current signals to and receives analog voltage or current signals from devices. The controller I / O can communicate with the controller's processor through a backplane so that digital signals and analog signals can be read into and controlled by the control program. The industrial controller 118 can also communicate with the industrial device 120 through a network using, for example, a communication module or an integrated networking port. Exemplary networks may include the Internet, an intranet, Ethernet, DeviceNet, ControlNet, Data Highway and Data Highway Plus (DH / DH+), remote I / O, fieldbus, Modbus, Profibus, wireless network, serial protocol, etc. The industrial controller 118 may also store persistent data values ​​that may be referenced by its associated control program and used for control decisions, including but not limited to: measured or calculated values ​​representing the operating state of the controlled machine or process (e.g., tank level, position, alarm, etc.) or captured time series data collected during operation of the automation system (e.g., state information at multiple points in time, diagnostic occurrences, etc.). Similarly, some smart devices, including but not limited to motor drives, instruments, or condition monitoring modules, may store data values ​​for controlling and / or visualizing operating states. Such devices may also capture time series data or events on a log for later retrieval and viewing.

[0038] Industrial automation systems typically include one or more human machine interfaces (HMIs) 114 that enable plant personnel to view telemetry and status data associated with the automation system and control some aspects of the system's operation. The HMI 114 can communicate with one or more of the industrial controllers 118 via a plant network 116 and exchange data with the industrial controllers to facilitate visualization of information related to the controlled industrial process on one or more pre-developed operator interface screens. The HMI 114 can also be configured to enable an operator to submit data to a specified data tag or memory address of the industrial controller 118, thereby providing a means for the operator to issue commands to the controlled system (e.g., cycle start commands, equipment actuation commands, etc.), modify set point values, etc. The HMI 114 can generate one or more display screens through which the operator interacts with the industrial controller 118 to interact with the controlled process and / or system. The example display screens may use graphical representations of processes that display metered or calculated values ​​to visualize the current state of an industrial system or its associated equipment, employ color or position animations based on the state, present alarm notifications, or employ other such techniques to present relevant data to an operator. The data presented in this manner is read by the HMI 114 from the industrial controller 118 and presented on one or more of the display screens according to the display format selected by the HMI developer. The HMI may include a fixed location device or a mobile device with a user-installed or pre-installed operating system and a user-installed or pre-installed graphical application software.

[0039] Some industrial environments may also include other systems or devices related to specific aspects of the controlled industrial system. These systems or devices may include, for example, a data historian 110 that aggregates and stores production information collected from industrial controllers 118 or other data sources, an equipment document repository containing electronic documentation of the various industrial devices that make up the controlled industrial system, an inventory tracking system, a work order management system, a repository for machine or process drawings and documentation, a supplier product document repository, a supplier knowledge base, an internal knowledge base, a work scheduling application, or other such systems, some or all of which may reside on the industrial environment's office network 108.

[0040] Higher-level systems 126 may perform functions that are less directly related to the control of industrial automation systems at the plant site and are instead directed to long-term planning, advanced supervisory control, analysis, reporting, or other such advanced functions. These systems 126 may reside on an office network 108 at an external location relative to the plant facility, or on a cloud platform that can access the office network and / or the plant network. Higher-level systems 126 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 the analysis may be fed back to an operator at the control system or directly fed back to a controller 118 or device 120 in the control system.

[0041] The various control, monitoring and analysis devices that make up the industrial environment must be programmed or configured using corresponding configuration applications specific to each device. For example, industrial controllers 118 are typically configured and programmed using control programming development applications such as ladder logic editors (e.g., executed on client devices 124). Using such a development platform, a designer can write a control program (e.g., ladder logic, structured text, functional block diagram, etc.) for implementing a desired industrial sequence or process and download the resulting program file to the controller 118. Separately, a developer designs a visualization screen and an associated navigation structure for the HMI 114 using an HMI development platform (e.g., executed on client devices 122), and downloads the resulting visualization file to the HMI 114. Some industrial devices 120, such as motor drives, telemetry devices, safety input devices, etc., may also need to be configured using a separate device configuration tool (e.g., executed on client devices 128) that is specific to the device being configured. Such a device configuration tool can be used to set device parameters or operating modes (e.g., high / low limits, output signal formats, scaling factors, energy consumption modes, etc.).

[0042] The need to use separate configuration tools to program and configure different aspects of industrial automation systems has led to a fragmented design approach, whereby different but related or overlapping aspects of the automation system are designed, configured, and programmed separately on different development environments. For example, a motion control system may require the use of a control logic programming platform to program the industrial controller and tune the control loops, another configuration platform to configure the motor drive, and a visualization development platform to program the associated HMI. Related peripheral systems - such as vision systems, safety systems, etc. - may also need to be configured using separate programming or development applications.

[0043] This separate development approach may also require considerable testing and debugging efforts to ensure proper integration of the separately configured system aspects. In this regard, the expected data interfaces or coordinated actions between the different system aspects may require extensive debugging due to failure to properly coordinate the different programming efforts.

[0044] To address at least some of these or other problems, one or more embodiments described herein provide an integrated development environment (IDE) for designing, programming, and configuring multiple aspects of industrial automation systems 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 manner, thereby facilitating integrated, multidisciplinary programming of control, visualization, and other aspects of control systems.

[0045] Typically, industrial IDEs support features spanning the entire automation lifecycle, including design (e.g., equipment selection and sizing, controller programming, visualization development, device configuration, testing, etc.); installation, configuration, and commissioning; operation, improvement, and management; as well as troubleshooting, expansion, and upgrades.

[0046] Implementations of industrial IDEs may include modular code and visualization libraries specific to industrial vertical markets and common industrial applications within these vertical markets. These code and visualization modules can simplify development and shorten development cycles while also supporting consistency and reuse across industrial enterprises.

[0047] To support enhanced development capabilities, projects created using implementations of the IDE system can be built on an object-based model rather than a tag-based architecture; or in addition to projects created using implementations of the IDE system being built on a tag-based architecture, projects created using implementations of the IDE system can also be built on an object-based model. To this end, the IDE system can support the use of automation objects used as building blocks of the object-based development structure. In order to ensure consistency within and between projects, and to ensure that a given industrial project is dynamically updated to reflect changes in the properties of industrial assets (e.g., control code, visualization definition, test scripts, analysis code, etc.), an implementation of the IDE system can use automation object inheritance features to propagate changes made to automation object definitions to all instances of automation objects used throughout the control project. In addition, a collection of automation objects and the hierarchical or functional relationships between these objects can be defined as a system model and can be used by developers to include in their system projects.

[0048] Figure 22 is a block diagram of an example integrated development environment (IDE) system 202 according to one or more implementations of the present disclosure. Aspects of the systems, devices, or processes described in the present disclosure may constitute machine-executable components contained within a machine, such as machine-executable components contained in one or more computer-readable media associated with one or more machines. Such components, when executed by one or more machines, such as computers, computing devices, automation devices, virtual machines, etc., may cause the machines to perform the described operations.

[0049] IDE system 202 may include: a user interface component 204 including an IDE editor 224, a project generation component 206, a project deployment component 208, a project test component 210, a collaboration management component 212, one or more processors 218, and a memory 220. In various embodiments, one or more of the user interface component 204, the project generation component 206, the project deployment component 208, the project test component 210, the collaboration management component 212, the one or more processors 218, and the memory 220 may be electrically and / or communicatively coupled to each other to perform one or more of the functions of IDE system 202. In some embodiments, components 204, 206, 208, 210, and 212 may include software instructions stored on the memory 220 and executed by the processor 218. IDE system 202 may also communicate with Figure 2 The processor 218 may interact with other hardware and / or software components not shown in the figure. For example, the processor 218 may interact with one or more external user interface devices such as a keyboard, a mouse, a display monitor, a touch screen, or other such interface devices.

[0050] The user interface component 204 can be configured to receive user input and present output to the user in any suitable format (e.g., visual, audio, tactile, etc.). In some embodiments, the user interface component 204 can be configured to communicate with an IDE client executed on a client device (e.g., a laptop, a tablet computer, a smart phone, etc.), which is communicatively connected to the IDE system 202 (e.g., via a hardwired connection or a wireless connection). Then, the user interface component 204 can receive user input data via the IDE client and present output data. In other embodiments, the user interface component 204 can be configured to generate a suitable interface screen (e.g., a program development screen) and provide it to the client device, and exchange data via these interface screens. The input data that can be received via various embodiments of the user interface component 204 may include, but is not limited to, programming code, industrial design instructions or targets, engineering drawings, AR / VR input, DSL definitions, video or image data, project test scripts, or other such inputs. Output data presented by various embodiments of user interface component 204 may include program code, programming feedback (eg, errors and highlighting, coding suggestions, etc.), programming and visual development screens, project testing results, and the like.

[0051] The project generation component 206 can be configured to create a system project including one or more project files based on the design input received via the user interface component 204 and the industrial knowledge, predefined code modules and visualization and automation objects 222 maintained by the IDE system 202. The project deployment component 208 can be configured to delegate the system project created by the project generation component 206 to appropriate industrial devices (e.g., controllers, HMI terminals, motor drives, AR / VR systems, etc.) for execution. To this end, the project deployment component 208 can identify the appropriate target device to which the corresponding parts of the system project should be sent for execution, convert these corresponding parts into a format understandable to the target device, and deploy the converted project components to their corresponding devices.

[0052] The project testing component 210 can be configured to execute test scripts associated with the automation objects 222 or other elements of the system project to verify the correct execution of various aspects of the project. The collaboration management component 212 can be configured to track instances of the system project that have been downloaded to the local client device so that these local versions of the project can be updated as needed in response to modifications submitted to the cloud-based IDE system.

[0053] The one or more processors 218 may perform one or more of the functions described herein with reference to the systems and / or methods disclosed. The memory 220 may 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.

[0054] Figure 3 is a diagram illustrating a general architecture of an industrial IDE system 202 according to one or more embodiments. The industrial IDE system 202 can implement a general set of services and workflows that span not only design but also debugging, operation, and maintenance. In terms of design, the IDE system 202 can support not only industrial controller programming and HMI development, but also sizing and selection of system components, device / system configuration, AR / VR visualization, and other features. The IDE system 202 can also include tools that simplify and automate the debugging of the resulting project and assist in the subsequent management of the deployed system during runtime.

[0055] Embodiments of the IDE system 202 implemented on a cloud platform also facilitate collaborative project development, whereby multiple developers 304 contribute design and programming input to a common automation system project 302. Collaboration tools supported by the IDE system can manage design contributions from multiple contributors and perform version control of the aggregate system project 302 to ensure project consistency.

[0056] Based on the design and programming input from one or more developers 304, the IDE system 202 generates a system project 302 including one or more project files. The system project 302 encodes one or more of the following: a control program; HMI, AR and / or VR visualization; device or subsystem configuration data (e.g., drive parameters, visual system configuration, telemetry device parameters, safety zone definitions, etc.); or other such aspects of the industrial automation system being designed. The IDE system 202 can identify the appropriate target device 306 (e.g., industrial controller, HMI terminal, variable frequency drive, safety device, etc.) on which the corresponding aspects of the system project 302 should be executed, convert the system project 302 into an executable file that can be executed on the corresponding target device, and deploy the executable file to its corresponding target device 306 for execution, thereby delegating the system project 302 to the plant floor to implement the automation project.

[0057] To support enhanced development capabilities, some embodiments of the IDE system 202 may be built on an object-based data model instead of or in addition to a tag-based architecture. Automation objects 222 serve as building blocks of the object-based development architecture. Figure 4 2 is a diagram illustrating several example automation object properties that may be utilized by the IDE system 202 in conjunction with building, deploying, and executing system projects 302. Automation objects 222 may be created and augmented during design, may be integrated into larger data models, and consumed during runtime. These automation objects 222 provide a common data structure across the IDE system 202 and may be stored in an object library (e.g., a portion of the memory 220) for reuse. The object library may store predefined automation objects 222 representing various classifications of real-world industrial assets 402, including but not limited to pumps, tanks, valves, motors, motor drives (e.g., variable frequency drives), industrial robots, actuators (e.g., pneumatic or hydraulic actuators), or other such assets. Automation objects 222 may represent elements of substantially any level of an industrial enterprise, including individual devices, machines consisting of many industrial devices and components (some of which may be associated with their own automation objects 222), and entire production lines or process control systems.

[0058] The automation object 222 for a given type of industrial asset may encode aspects such as 2D or 3D visualization, alarms, control coding (e.g., logic or other types of control programs), analysis, startup procedures, test protocols and scripts, validation reports, simulations, diagrams, safety protocols, and other such attributes associated with the industrial asset 402 represented by the object 222. The automation object 222 may also be geotagged with location information identifying the location of the associated asset. During the runtime of the system project 302, the automation object 222 corresponding to a given real-world asset 402 may also record status or operational history data for the asset. In general, the automation object 222 serves as a programmatic representation of its corresponding industrial asset 402 and may be incorporated into the system project 302 as an element of control code, 2D or 3D visualization, a knowledge base or maintenance guidance system for the industrial asset, or other such aspects. In addition, as will be discussed in more detail below, the automation object 222 may support inheritance so that changes to any of the attributes of the automation object 222 discussed above are automatically propagated to instances of the automation object used throughout the system project 302.

[0059] Figure 5is a diagram illustrating an example data flow associated with creating a system project 302 for an automation system being designed using an IDE system 202 according to one or more embodiments. A client device 504 (e.g., a laptop, tablet, desktop, mobile device, wearable AR / VR device, etc.) executing an IDE client application 514 can access the project development tools of the IDE system and utilize these tools to create a comprehensive system project 302 for the automation system being developed. Through interaction with the user interface component 204 of the system, developers can submit design input 512 to the IDE system 202 in various supported formats, including industry-specific control programs (e.g., control logic, structured text, sequential function charts, etc.) and HMI screen configuration input. Based on the design input 512 and information stored in the industry knowledge base (predefined code modules 508 and visualizations 510, guardrail templates 506, physics-based rules 516, etc.), the user interface component 204 presents design feedback 518 designed to assist developers in developing a system project 302 for configuration, control, and visualization of an industrial automation system.

[0060] In addition to control programs and visualization definitions, some embodiments of the IDE system 202 may be configured to receive digital engineering drawings (e.g., computer-aided design (CAD) files) as design input 512. In such embodiments, the project generation component 206 may generate portions of the system project 302 based on analysis of existing design drawings, for example, by automatically generating control and / or visualization code. Drawings that may be submitted as design input 512 may include, but are not limited to, P&ID drawings, mechanical drawings, flow charts, or other such documents. For example, a P&ID drawing may be imported into the IDE system 202, and the project generation component 206 may identify elements (e.g., tanks, pumps, etc.) conveyed by the drawing and the relationships between them. The project generation component 206 may associate or map the elements identified in the drawing with appropriate automation objects 222 corresponding to the elements (e.g., tanks, pumps, etc.), and add the automation objects 222 to the system project 302. The equipment-specific and asset-specific automation objects 222 include appropriate code and visualization to be associated with the elements identified in the drawing. In general, the IDE system 202 can examine one or more different types of (mechanical, electrical, piping, etc.) drawings to determine relationships between devices, machines, and / or assets (including identifying common elements across different drawings), and intelligently associate these elements with appropriate automation objects 222, code modules 508, and / or visualizations 510. The IDE system 202 can utilize physics-based rules 516 and predefined code modules 508 and visualizations 510 as needed in conjunction with generating code or project data for the system project 302.

[0061] The IDE system 202 may also determine whether predefined visualization content is available for any object found in the drawing, and generate appropriate HMI screens or AR / VR content for the found objects based on these predefined visualizations. To this end, the IDE system 202 may store industry-specific, asset-specific, and / or application-specific visualizations 510 that can be accessed on demand by the project generation component 206. These visualizations 510 may be classified according to industry or industrial vertical markets (e.g., automotive, food and drug, oil and gas, pharmaceuticals, etc.), types of industrial assets (e.g., types of machines or industrial equipment), types of industrial applications (e.g., batch processing, flow control, web tension control, sheet metal stamping, water treatment, etc.), or other such categories. The predefined visualizations 510 may include visualizations in various formats, including but not limited to HMI screens or windows, mashups that aggregate data from multiple pre-specified sources, AR overlays, VR objects that represent 3D virtualization of associated industrial assets, or other such visualization formats. The IDE system 202 may select an appropriate visualization for a given object based on a predefined association between an object type and visualization content.

[0062] In another example, the marks applied to the engineering drawing by the user can be understood by some embodiments of the project generation component 206 to convey specific design intent or parameters. For example, the mark of the red pen can be understood to indicate a safe area, the two circles connected by the dotted line can be interpreted as a gear relationship, and the thick line can indicate a cam relationship. In this way, the designer can draft the design goals on the existing drawing in a way that the IDE system 202 can understand and utilize to generate code and visualization. In another example, the project generation component 206 can learn the permissions and interlocks (e.g., valves and their associated states) that serve as necessary prerequisites for starting the machine based on the analysis of the user's CAD drawing. The project generation component 206 can generate any suitable code (ladder logic, function blocks, etc.), equipment configuration and visualization based on the analysis of these drawings and marks to be incorporated into the system project 302. In some embodiments, the user interface component 204 can include a design tool for developing engineering drawings within the IDE platform itself, and the project generation component 206 can generate the code as a background process when the user creates a drawing for a new project. In some implementations, project generation component 206 can also convert the state machine diagram into a corresponding programming sequence, thereby generating at least skeleton code that can be enhanced with additional programming details as desired by the developer.

[0063] Alternatively or additionally, some embodiments of the IDE system 202 may support target-based automation programming. For example, the user interface component 204 may allow a user to specify a production target for the automation system being designed (e.g., specifying that the bottling plant being designed must be able to produce at least 5,000 bottles per second during normal operation) and any other relevant design constraints that apply to the design project (e.g., budget constraints, available field space, available control cabinet space, etc.). Based on this information, the project generation component 206 will generate some parts of the system project 302 to meet the specified design targets and constraints. Some parts of the system project 302 that can be generated in this manner may include, but are not limited to: equipment and equipment selection (e.g., how many pumps, controllers, stations, conveyors, drives, or other assets will need to be defined to meet the specified targets), associated equipment configurations (e.g., tuning parameters, network settings, drive parameters, etc.), control coding, or HMI screens suitable for visualizing the automation system being designed.

[0064] Some embodiments of the project generation component 206 can also generate at least some of the project code for the system project 302 based on knowledge of the parts that have been ordered for the project being developed. This can involve accessing the customer's account information maintained by the equipment supplier to identify the equipment that has been purchased for the project. Based on this information, the project generation component 206 can add the appropriate automation objects 222 and associated code modules 508 corresponding to the purchased assets, thereby providing a starting point for project development.

[0065] Some embodiments of the project generation component 206 may also monitor customer-specific design methods for commonly programmed functions (e.g., pumping applications, batch processing, palletizing operations, etc.), and generate recommendations for design modules (e.g., code modules 508, visualizations 510, etc.) that the user may wish to incorporate into the current design project based on inferences about the designer's goals and learned methods to achieve the goals. To this end, some embodiments of the project generation component 206 may be configured to monitor design inputs 512 over time and learn, based on the monitoring, correlations between certain design actions (e.g., adding certain code modules or code segments to the design project, selecting certain visualizations, etc.) and the type of industrial asset, industrial sequence, or industrial process being designed. The project generation component 206 may record these learned correlations and generate recommendations based on these correlations during subsequent project development sessions. For example, if the project generation component 206 determines, based on an analysis of the design inputs 512, that the designer is currently developing a control project in a repetitive, predictable manner involving an industrial equipment that has been programmed and / or visualized in the past, the project generation component 206 can instruct the user interface component 204 to present recommended development steps or code modules 508 that the designer may wish to incorporate into the system project 302 based on how the equipment was configured and / or programmed in the past.

[0066] In some embodiments, the IDE system 202 may also store and implement guardrail templates 506 that define design guardrails intended to ensure that the project complies with internal or external design standards. Based on the design parameters defined by one or more selected guardrail templates 506, the user interface component 204 may provide dynamic recommendations or other types of feedback as a subset of design feedback 518, which are designed to guide the developer in a manner to ensure that the system project 302 complies with internal or external requirements or standards (e.g., certifications such as TUV certification, internal design standards, industry-specific or vertical market-specific design standards, etc.). This feedback 518 may take the form of text-based recommendations (e.g., recommendations to rewrite indicated portions of control code to comply with defined programming standards), syntax highlighting, error highlighting, automatic completion of code segments, or other such formats. In this manner, the IDE system 202 may customize the design feedback 518, including programming recommendations, recommendations for predefined code modules 508 or visualizations 510, error highlighting, syntax highlighting, etc., according to the type of industrial system being developed and any applicable internal design standards.

[0067] Guardrail templates 506 may also be designed to maintain compliance with global best practices applicable to other aspects of control program or project development. For example, if a developer's control program is deemed too complex (as defined by the standards specified by one or more guardrail templates 506), the user interface component 204 may generate and present an alert. Because different vertical markets (e.g., automotive, pharmaceutical, oil and gas, food and drug, marine, etc.) must comply with different standards and certifications, the IDE system 202 may maintain a library of guardrail templates 506 for different internal and external standards and certifications, including customized user-specific guardrail templates 506. These guardrail templates 506 may be categorized according to industrial vertical market, type of industrial application, plant facility (in the case of customized internal guardrail templates 506), or other such categories. During development, the project generation component 206 may select and apply a subset of guardrail templates 506 determined to be relevant to the project currently being developed based on a determination of aspects such as the industrial vertical market associated with the project, the type of industrial application being programmed (e.g., flow control, web tension control, a specific batch process, etc.), or other such aspects. The project generation component 206 can utilize guardrail templates 506 to implement rule-based programming, thereby presenting programming feedback (a subset of design feedback 518) such as dynamic intelligent auto-correction, type-ahead, or coding suggestions based on industry expertise and best practices in coding (e.g., identifying inefficiencies in the code being developed and recommending appropriate corrections).

[0068] Users can also run their own internal guardrail templates 506 against code provided by an external supplier (e.g., an OEM) to ensure that the code complies with internal programming standards. In such a scenario, the code provided by the supplier can be submitted to the IDE system 202, and the project generation component 206 can analyze the code in view of the internal coding standards specified by one or more customized guardrail templates 506. Based on the results of the analysis, the user interface component 204 can indicate (e.g., using highlighting, overlay text, etc.) some portions of the code provided by the supplier that do not comply with the programming standards set forth by the guardrail template 506, and display suggestions for modifying the code to make the code comply with the standards. As an alternative to recommending these modifications or in addition to recommending these modifications, some embodiments of the project generation component 206 can be configured to automatically modify the code according to the recommendations to make the code comply with the standards.

[0069] When making coding suggestions as part of the design feedback 518, the project generation component 206 can call a selected code module 508 stored in the code module database or a selected automation object 222 stored in the automation object library 502 (e.g., on the memory 220). The code module 508 includes standardized coding segments for controlling common industrial tasks or applications (e.g., palletizing, flow control, web tension control, pick and place applications, conveyor control, etc.). Similarly, the automation objects 222 representing corresponding industrial assets can have associated therewith standardized control codes for monitoring and controlling their corresponding assets. In some embodiments, the code modules 508 and / or automation objects 222 can be classified according to one or more of an industrial vertical market (e.g., automotive, food and drug, oil and gas, textiles, marine, pharmaceuticals, etc.), an industrial application, or a type of machine or equipment for which the code module 508 or automation object 222 is applicable.

[0070] In some embodiments, the project generation component 206 can infer the programmer's current programming task or design goal based on the program input provided by the programmer (as a subset of the design input 512), and determine whether one of the predefined code modules 508 or automation objects 222 can be appropriately added to the control program being developed to achieve the inferred task or goal based on the task or goal. For example, the project generation component 206 can infer based on the analysis of the design input 512 that the programmer is currently developing control code for transferring material from a first tank to another tank, and in response, recommend including: a predefined code module 508 containing standardized or frequently utilized code for controlling a valve, pump, or other asset required to achieve the material transfer. Similarly, the project generation component 206 can recommend including an automation object 222 that represents one of the tanks or other industrial assets (e.g., a valve, pump, etc.) involved in transferring the material, wherein the recommended automation object 222 includes associated control code for controlling its associated asset and a visualization object that can be used to visualize the asset on an HMI application or another visualization application.

[0071] Customized guardrail templates 506 may also be defined to capture nuances of a customer site that should be considered in the project design. For example, a guardrail template 506 may record the fact that the automation system being designed will be installed in an area where power outages are common, and this factor will be taken into account when generating design feedback 518, such as by recommending the implementation of backup uninterruptible power supplies and suggesting how these power supplies should be combined and recommending associated programming or control strategies that account for these outages.

[0072] The IDE system 202 can also use the guardrail template 506 to guide the user in selecting equipment or devices for a given design goal, for example, based on the following: industrial vertical market, type of control application (e.g., sheet metal stamping, die casting, pallet packaging, conveyor control, web tension control, batch processing, etc.), budget constraints of the project, physical constraints of the installation site (e.g., available floor, wall or cabinet space; size 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 512, and the user interface component 204 can present equipment recommendations as a subset of design feedback 518. In conjunction with the equipment recommendations, the project generation component 206 can also recommend corresponding automation objects 222 representing the recommended equipment for inclusion in the system project 302.

[0073] In some embodiments, the project generation component 206 can also determine whether some or all of the existing equipment can be readjusted 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 utilize existing equipment because some bottling lines already exist. The decision about which equipment and equipment can be reused will affect the design of the new control system. Therefore, some of the design inputs provided to the design input 512 of the IDE system 202 may include details of the customer's existing systems in or near the installation site. In some embodiments, the project generation component 206 can apply artificial intelligence (AI) or traditional analysis methods to this information to determine whether the existing equipment specified in the design input 512 can be readjusted or utilized. Based on the results of this analysis, the project generation component 206 can generate a list of any new equipment that may need to be purchased based on these decisions as design feedback 518.

[0074] In some embodiments, the IDE system 202 can provide design recommendations based on an understanding of the physical environment in which the automation system being designed will be installed. To this end, information about the physical environment can be submitted to the IDE system 202 (as part of the design input 512) in the form of a 2D or 3D image or video of the factory environment. In some embodiments, the environmental information can also be obtained from an existing digital twin of the factory, or by analyzing scanned environmental data obtained by a wearable AR device. The project generation component 206 can analyze the image, video, or digital twin data to identify physical elements (e.g., walls, beams, safety fences, existing machines and equipment, etc.) within the installation area and the physical relationships between these elements. This can include: finding out the distance between machines, the length of pipe laying, the location and distance of wire harnesses or cable trays, etc. Based on the results of the analysis, the project generation component 206 can add the environment to the generated schematic as part of the system project 302, generate recommendations for the optimal location of equipment or machines (e.g., recommending the minimum spacing between power cables and data cables), or make other improvements to the system project 302. At least some of this design data may be generated based on physics-based rules 516, which may be referenced by the project generation component 206 to determine such physical design specifications as minimum safe distances from hazardous equipment (which may also be factored in determining appropriate locations for installation of safety devices relative to the equipment, given expected human or vehicle reaction times defined by the physics-based rules 516), selection of materials capable of withstanding expected loads, piping configurations and adjustments for specified flow control applications, wiring specifications appropriate for expected electrical loads, minimum distances between signal wiring and electromagnetic field (EMF) sources to ensure negligible electrical interference with data signals, or other such design features that rely on physical rules.

[0075] In an example use case, the relative locations of machines and equipment specified by the physical environment information submitted to the IDE system 202 can be used by the project generation component 206 to generate design data for an industrial safety system. For example, the project generation component 206 can analyze distance measurements between safety equipment and hazardous machines and, based on these measurements, determine appropriate placement and configuration of safety devices and associated safety controllers that ensure (e.g., in the event that a person passes through a light curtain) that the machine will shut down within sufficient safety reaction time to prevent damage.

[0076] In some embodiments, the project generation component 206 may also analyze photographic data or video data of existing machines to determine inline mechanical features such as gears or cams and factor that information into one or more guardrail templates 506 or design recommendations.

[0077] As described above, the system project 302 generated by the IDE system 202 for a given automation system being designed may be built on an object-based architecture using the automation objects 222 as building blocks. Figure 6 6 is a diagram illustrating an example system project 302 incorporating automation objects 222 into a project model. In this example, various automation objects 222 representing assets of similar industrial equipment, systems, or automation systems (e.g., processes, tanks, valves, pumps, etc.) have been incorporated into the system project 302 as elements of a larger project data model 602. The project data model 602 also defines hierarchical relationships between these automation objects 222. According to the example relationship, a process automation object representing a batch process can be defined as a parent object of multiple child objects representing equipment and equipment that performs the process, such as tanks, pumps, and valves. Each automation object 222 has object attributes or properties associated with it that are specific to its corresponding industrial asset (e.g., the above combined Figure 4 Those discussed herein), including executable control programs for controlling the asset (or for coordinating the actions of the asset with other industrial assets) and visualizations that can be used to present relevant information about the asset during runtime.

[0078] At least some of the properties of each automation object 222 are default properties defined by the IDE system 202 based on coding industry expertise related to the asset represented by the object. These default properties may include, for example, industry standard or recommended control codes for monitoring and controlling the asset represented by the automation object 222, 2D or 3D graphical objects that can be used to visualize the operation or statistical data of the asset, alarm conditions associated with the asset, analysis or reporting scripts designed to generate actionable insights into the behavior of the asset, or other such properties. Developers can modify or add other properties as needed (via design input 512) to customize the automation object 222 for the specific asset and / or industrial application for which the system project 302 is being developed. This may include, for example, associating customized control codes, HMI screens, AR demonstrations, or help files associated with the selected automation object 222. In this way, the automation object 222 can be created and expanded as needed during design for consumption or execution by the target control device during runtime.

[0079] Once the development and testing of the system project 302 is completed, the debugging tools supported by the IDE system 202 can simplify the process of debugging the project in the field. When the system project 302 for a given automation system has been completed, the system project 302 can be deployed to one or more target control devices for execution. Figure 7 is a diagram illustrating debugging of a system project 302. The project deployment component 208 can compile or otherwise convert the completed system project 302 into one or more executable or configuration files that can be stored and executed on corresponding target industrial devices of the automation system (e.g., industrial controllers 118, HMI terminals 114 or other types of visualization systems, motor drives 710, telemetry devices, vision systems, safety relays, etc.).

[0080] Conventional control program development platforms require developers to specify the type of industrial controller (e.g., the model of the controller) on which the control program will run before development, thereby binding the control program to the specified controller. Controller-specific guardrails are then imposed during program development, which limit the way the program is developed given the capabilities of the selected controller. In contrast, some embodiments of the IDE system 202 can abstract project development based on specific controller types, thereby enabling designers to develop system projects 302 as logical representations of automation systems in a manner that is agnostic of where and how the various control aspects of the system project 302 will run. Once project development is completed and the system project 302 is ready for debugging, the user can specify (via the user interface component 204) the target device on which the corresponding aspects of the system project 302 are to be executed. In response, the distribution engine of the project deployment component 208 converts the aspects of the system project 302 into corresponding executable files formatted for storage and execution on their corresponding target devices.

[0081] For example, the system project 302 may include control code, visualization screen definitions, and motor drive parameter definitions, among other project aspects. After completing project development, the user may identify which target devices, including the industrial controller 118, the HMI terminal 114, and the motor drive 710, will execute or receive these respective aspects of the system project 302. The project deployment component 208 may then convert the controller code defined by the system project 302 into a control program file 702 formatted for execution on the specified industrial controller 118 and send the control program file 702 to the controller 118 (e.g., via the plant network 116). Similarly, the project deployment component 208 may convert the visualization definition and the motor drive parameter definition into a visualization application 704 and a device configuration file 708, respectively, and deploy these files to their respective target devices for execution and / or device configuration.

[0082] Typically, the project deployment component 208 performs any conversion necessary to enable the aspects of the system project 302 to be performed on a specified device. No matter how the various elements of the system project 302 are distributed, any inherent relationship, handshake or data sharing defined in the system project 302 will be maintained. In this way, the embodiment of the IDE system 202 can separate the project from how and where the project will run. This also enables the same system project 302 to be debugged at different factory facilities with different control equipment sets. In other words, some embodiments of the IDE system 202 can distribute project code to different target devices according to the specific equipment found on site. The IDE system 202 can also enable some parts of the project file to be debugged as an emulator or debugged on a cloud-based controller.

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

[0084] Intelligent propagation can be used to propagate copies of the system project 302 to multiple plant facilities with different equipment configurations, so that even if the field equipment does not perfectly match the defined target (for example, if different pump types are found at different locations), the project deployment component 208 intelligently associates the project components with the correct industrial assets or control devices. For target equipment that does not perfectly match the expected asset, the project deployment component 208 can calculate the estimated impact of running the system project 302 on the non-optimal target equipment and generate warnings or recommendations for mitigating expected deviations from optimal project execution.

[0085] As described above, some embodiments of the IDE system 202 may be implemented on a cloud platform. Figure 8 802 is a diagram showing an example architecture in which a cloud-based IDE service 802 is used to develop industrial applications and deploy industrial applications to a factory environment. In this example, the industrial environment includes one or more industrial controllers 118, HMI terminals 114, motor drivers 710, servers 801 running higher-level applications (e.g., ERP, MES, etc.), and other such industrial assets. These industrial assets are connected to a factory network 116 (e.g., a general industrial protocol network, an Ethernet / IP network, etc.), which facilitates data exchange between industrial devices on the factory site. The factory network 116 can be a wired or wireless network. In the example shown, an advanced server 810 resides on a separate office network 108 connected to the factory network 116 (e.g., via a router 808 or other network infrastructure device).

[0086] In this example, the IDE system 202 resides on a cloud platform 806 and is executed as a collection of cloud-based IDE services 802 that can be accessed by authorized remote client devices 504. The cloud platform 806 can be any infrastructure that enables shared computing services (e.g., IDE services 802) to be accessed and utilized by devices that can connect to the cloud. The cloud platform 806 can be a public cloud that can be accessed via the Internet by devices 504 that have Internet connectivity and appropriate authorization to utilize the IDE services 802. In some scenarios, the cloud platform 806 can be provided by a cloud provider as a platform as a service (PaaS), and the IDE services 802 can reside on the cloud platform 806 and execute on the cloud platform 806 as a cloud-based service. In some such configurations, the owner of the IDE services 802 can provide access to the cloud platform 806 and the associated IDE services 802 as a subscription service to customers. Alternatively, the cloud platform 806 can be a private cloud operated internally by an industrial enterprise (owner of a factory facility). An example private cloud platform may include a collection of servers that host the IDE service 802 and reside on a corporate network protected by a firewall.

[0087] The cloud-based implementation of the IDE system 202 can facilitate collaborative development by multiple remote developers who are authorized to access the IDE service 802. When the system project 302 is ready for deployment, the project 302 can be delegated to the factory facility via a secure connection between the office network 108 or the factory network 116 and the cloud platform 806. As discussed above, the industrial IDE service 802 can convert the system project 302 into one or more appropriate executable files - control program files 702, visualization applications 704, device configuration files 708, system configuration files 812 - and deploy these files to appropriate devices in the factory facility to facilitate the implementation of the automation project.

[0088] As described above, the system project 302 generated by an embodiment of the industrial IDE system 202 may include the plurality of automation objects 222 . Fig. 9 is a diagram of an example automation object 222 that has been integrated into the project data model 602 of the system project 302. Figure 4 and Figure 6 As discussed, the system items 302 may incorporate instances of automation objects 222 that serve as programmatic representations of industrial assets or processes. Assets that may be represented by a given automation object 222 may include equipment-level assets (e.g., motor drives, valves, pumps, etc.) as well as machine-level assets (presses, tanks, tool stations, etc.). The automation objects 222 may represent off-the-shelf industrial equipment or machines provided by equipment or equipment suppliers, or may include custom automation objects 222 that represent custom machines provided by an OEM or another type of machine manufacturer.

[0089] The project data model 602 may define hierarchical relationships between a plurality of automation objects 222 that are integrated as part of the system project 302. These hierarchical relationships may represent physical and / or functional relationships between the represented assets. According to example relationships, a process automation object 222 representing a batch process may be defined as a parent object of a plurality of child automation objects 222 representing equipment and equipment such as tanks, pumps, and valves that perform the process. In another example, an automation object 222 representing a machine or production line may be defined as a parent object under which a plurality of child automation objects 222 representing workstations or sub-machines within the machine or production line are defined. These child automation objects 222 may themselves have a plurality of child automation objects 222 representing the equipment-level assets that make up these workstations or sub-machines.

[0090] Each automation object 222 may provide functionality similar to a data tag that serves as a container for input data received from and output data sent to its corresponding industrial asset (e.g., digital and analog data values ​​received from an asset to be processed by the system item 302, and digital and analog values ​​generated by the system item 302 and sent to an asset). In addition, each automation object 222 includes a plurality of programming attributes related to the represented industrial asset, which may be used in conjunction with the above. Figure 4 Examples of which are discussed. These properties may include, for example, control logic that may be executed as part of system project 302 to monitor and control the represented asset. The associated control logic may be pre-developed to exchange input and output data with its associated industrial asset via defined input and output tags corresponding to the asset's physical inputs and outputs (i.e., the asset's digital and analog I / O). During execution of control project 302, the object's control logic may process inputs received from the asset and generate outputs for the asset based on the results of the processing.

[0091] In addition, the control logic associated with various different automation objects 222 defined by the project data model 602 as having a hierarchical relationship with each other can interact or cooperate based on these defined relationships. For example, based on the defined hierarchical relationship between a first automation object 222 representing a tank (defined as a parent object) and a second automation object 222 representing a valve associated with the tank (defined as a child object of the first object), the system project 302 can link two sets of control logic associated with the first automation object and the second automation object 222, respectively, so that the control logic associated with the two automation objects 222 performs coordinated monitoring and control of the machine. Linking the two sets of control logic in this manner can include, for example, linking data tags of the child object 222 with corresponding data tags of the parent object 222 according to the hierarchical relationship defined by the model 602. In general, the project generation component 206 can generate at least a portion of the industrial control programming of the system project based on the aggregate control code associated with the automation objects 222 defined by the project data model 602 and the relationships between the objects 222 defined by the model 602.

[0092] The automation objects 222 may also include associated HMI objects that may be used by a visualization system (e.g., an HMI application, a 2D or 3D augmented reality or virtual reality system, etc.) to present animated graphical representations of the assets. These HMI objects may include one or more HMI interface screens designed to present information about the assets (e.g., a report screen presenting statistical or operational data for the assets, a screen presenting animated graphical representations of the assets, etc.), individual graphical objects representing the assets that may be imported into an industrial visualization application, or other such objects. If the project data model 602 defines functional relationships between a collection of automation objects 222, the project generation component 206 may generate an aggregated visual representation as part of the system project 302 based on a combination of the visualization properties defined by the objects 222 and the defined relationships between those objects.

[0093] The automation object 222 may also include an analysis script designed to analyze data generated by the asset to generate insights into the performance or health of the asset. Example analyses that may be performed by the analysis script of the automation object may include, but are not limited to, an assessment of the current health and predicted future health of the asset (e.g., determining a predicted failure time for an asset), determining when an asset requires maintenance, or other such metrics. As with the control logic of the automation object, the analysis script may be designed to interface with known data items generated by the industrial asset (e.g., data tags specific to the asset) so that data associated with those data items may be processed by the script.

[0094] The automation object 222 may also define alarm information associated with the industrial asset. The alarm information may include a definition of a condition that triggers an alarm (e.g., when a specified data item representing an operational metric of an asset falls outside a defined range of normal behavior, when the state of a specified digital tag satisfies an alarm condition, etc.) and an alarm message to be presented in response to the alarm trigger. The alarm information may be referenced by a visualization system (e.g., an HMI application, an augmented reality or virtual reality system, etc.), which may present an alarm message for the industrial asset based on the alarm definition defined by the automation object 222.

[0095] Some embodiments of the automation object 222 may also define test properties as part of the global test framework supported by the IDE system 202. These test properties may include object-specific test scripts designed to test and debug associated aspects of the automation object 222 and the system project 302 of the reference object 222. The test properties of the object may also include object-specific test scenario definitions, which define one or more test scenarios that can be advantageously run against the associated project elements of the automation object 222 and the reference object 222. The test scenario definitions may be pre-designed based on industry expertise about the industrial asset or process represented by the automation object 222. The test properties associated with the automation object 222 may alleviate the need to write test scripts for testing and debugging the system project 302.

[0096] Fig.10 2 is a diagram showing the use of test scripts 1002 bundled with automation objects 222 by the project test component 210 of the IDE system to test an example system project 302. The automation object 222 may be provided with a pre-bundled test script 1002 and / or a definition of a test scenario 1004 specific to the type of industrial asset represented by the automation object 222. During or after the development of the system project 302 as described above, the project test component 210 of the IDE system may execute the test scripts 1002 associated with one or more selected automation objects 222 in a timely manner to verify the correct response of the system project 302, thereby verifying the project. To this end, the test script 1002 may define simulated test inputs 1012 to be provided to the automation object 222 and / or the associated project code using the object 222, and the expected response of the automation object 222 and its associated project code to the simulated inputs 1012.

[0097] According to the example test procedure, the project test component 210 can execute one or more test scripts 1002 associated with the corresponding one or more automation objects 222 for the system project 302. The execution of the test script 1002 can include, for example, feeding simulated test inputs 1012 to control code or other elements of the system project 302 according to a sequence defined by the test script 1002, setting the values ​​of digital or analog program variables defined by the system project 302 according to a defined sequence, initiating control routines of the system project 302 according to a defined sequence, testing animated objects or other visualization elements defined by the system project 302, verifying data connections between control routines, verifying relationships between program elements and drawing elements, confirming that device configuration settings or parameter values ​​are appropriate for a given industrial application executed by the system project 302, or otherwise interacting with the system project 302 according to the test procedure defined by the test script 1002. During testing, the project test component 210 can monitor the test results 1006 or responses of the system project 302 to the test interactions defined by the test script 1002 and determine whether these test results 1006 match the expected results defined by the test script 1002. In this way, the correct operation of the system project 302 can be verified before deployment without the need to develop custom test scripts to debug the system project code.

[0098] In some testing scenarios, the test script 1002 may define a test sequence that is applied in a holistic manner to the system project 302 as a whole, rather than to a specific control program or routine. For example, the project test component 210 may execute a test script 1002 that verifies connections or relationships across design platforms that may not otherwise be tested, such as control code, visualization applications, electrical drawings, panel layout definitions, wiring schedules, piping diagrams, etc.

[0099] If the test results 1006 indicate improper operation of one or more aspects of the system project 302, the project test component 210 can generate and present one or more design recommendations 1008 indicating possible modifications to the system project 302 that will correct the operation of the project. These design recommendations 1008 can include, for example, control code modifications or replacements, recommended corrections to data tag addresses, recommended corrections to HMI graphic object references, recommended corrections to mechanical or electrical drawings for consistency with control code (e.g., adding missing output devices to the electrical drawing corresponding to the output devices referenced by the control programming), recommended modifications to configuration parameters of industrial equipment, or other such corrections.

[0100] The test characteristics of some automation objects 222 can define multiple test scenarios 1004 that should be run on the object 222 and its corresponding control code and project elements to ensure comprehensive testing of the object 222 and related code. These scenarios 1004 are based on pre-learned industrial expertise related to the industrial assets or processes represented by the automation objects and their related project elements. In some implementations, each defined test scenario 1004 can have its own associated test script 1002, or a specific way to apply the test script 1002 can be defined (e.g., which routines of the control code of the system project are verified, which other project elements should be cross-referenced for verification purposes, etc.). During the testing of the system project 302, the project test component 210 can execute one or more test scripts 1002 in sequence according to each defined test scenario 1004 to comprehensively verify the correct operation of the system project 302 across all platforms (control programming, visualization configuration, mapping, equipment configuration, etc.).

[0101] In some embodiments, the project test component 210 may also be configured to generate a verification checklist based on the analysis of the system project 302 and output the verification checklist via the user interface component 204. The verification checklist may provide instructions regarding field tests and checks that should be performed in conjunction with commissioning the automation system for which the system project 302 was developed. These may include tests that should be performed on the automation system hardware and electrical connections that cannot be performed solely via testing of the system project 302. An example verification checklist may include a list of I / O points whose connectivity should be verified, instructions to visually inspect equipment with panels installed, a sequence of manual operator panel interactions that should be performed to verify proper machine operation, or other such information.

[0102] Return to Fig. 9 , the automation object 222 may also include a history configuration as an attribute, the history configuration defining data generated by the corresponding industrial asset to be archived in the data historian. The history configuration may be referenced by a data historian system or application executing a portion of the system project 302 to facilitate configuring the data historian system to collect and archive the data items defined by the configuration. As with other attributes of the automation object 222, the history configuration attribute may specify a subset of available data generated by the corresponding industrial asset that is known to be relevant to an assessment of the performance or health of the asset based on relevant industrial expertise encoded into the object 222.

[0103] Some embodiments of the automation object 222 may also define security features or protocols associated with the associated industrial asset. These security features may include, but are not limited to, definition of user roles that are permitted to perform certain operations associated with the industrial asset, encryption protocols to be applied to data generated by the asset, network security protocols to be implemented on the asset, or other such security features. The security information defined by these embodiments of the automation object 222 may be used by the system item 302 to manage access to specified functions of the industrial asset (e.g., as a function of the user role), to configure network devices to support specified network security protocols, or to configure other security-related devices.

[0104] Embodiments of the IDE system 202 may support a development framework whereby changes made to an automation object 222 stored in the automation object library 502 are propagated to instances of the automation object 222 used in the system project 302 . Fig.11 1 is a diagram illustrating submitting an automation object edit 1102 to the IDE system 202. As described above, the automation objects 222 are maintained in the automation object library 502 (which may be part of the memory 220). Through interaction with the user interface component 204 and the associated IDE editor 224, the developer may add the automation objects 222 selected from the library 502 to the system project 302 as instances of these automation objects 222. Fig.11 In the example shown, object 222a is an instance of automation object 222 that has been selected by a developer and added to system project 302. In some scenarios, project generation component 206 can also automatically select and add automation object 222 to project 302 based on inferences about the automation system for which project 302 is being developed (e.g., based on design goals or engineering drawings submitted to system 202).

[0105] The IDE editor 224 may allow a user to modify the properties of a selected automation object 222 stored in the library 502. To this end, the user interface component 204 may generate a user interface and transmit the user interface to the client device 504 (e.g., via the IDE client 514), which allows the user to browse the available automation objects 222 and submit edits 1102 to the selected object 222. Fig. 9 Any of the properties described may be modified in this manner for any defined automation object 222. For example, a designer may wish to modify the control code associated with a particular industrial asset (e.g., a pump, tank, press, etc.) having a defined automation object 222 stored in the library 502. Accordingly, the user may submit an edit 1102 that updates the control code for the associated automation object 222. Such an edit may be used to update the operating sequence or control behavior of the associated industrial asset.

[0106] Similarly, a user may submit an edit 1102 to update the visual properties of a selected automation object 222; for example, to replace or edit the graphical representation of the corresponding asset. An edit 1102 may also be submitted to add or remove an alarm to or from a list of alarm definitions associated with an object 222, or to edit an existing alarm definition. Security features, test scripts, and analysis code associated with an automation object 222 may also be modified by submitting appropriate edits 1102.

[0107] These edits 1102 are to automation object definitions maintained in the automation object library 502. Upon receiving object edits 1102 (submitted via the user interface component 204) to a selected automation object 222, the project generation component 206 updates the target automation object 222 according to the received edits 1102 to produce an updated automation object 222. The updated automation object 222 replaces the previous version of the automation object 222 in the library 502.

[0108] The project generation component 206 can also update all instances of the automation object 222 found within the project 302 if an instance of the automation object 222 subject to the edit 1102 had been added to an existing system project 302 prior to receiving the edit 1102 . Fig.12 1102 is a diagram illustrating modification of an instance 222a of an automation object according to an edit 1102 submitted to a master version of an automation object 222 stored in a library 502. When an automation object 222 in a library 502 has been modified as described above, the project generation component 206 identifies all instances 222a of the automation object used throughout any system project 302 that uses the object 222 and propagates the modification to those instances. This may include updating control code, visualization, analysis code, security features, or other properties to reflect the modification defined by the edit 1102. In this manner, all instances 222a of the automation object automatically inherit the modifications made to the master version of the automation object 222 stored in the library 502.

[0109] Fig.12 The system project 302 is depicted as being stored on the IDE system 202 itself (e.g., if the IDE system 202 is implemented as a cloud service, the system project 302 is stored on cloud-based storage, such as Figure 8 However, in some implementations, the IDE system 202 may also propagate the automation object edits to the system project that has been deployed to the local client device for local editing. Fig.13is a diagram showing downloading a copy of a system project 302 from an IDE system 202 to a local client device 504. In this example, the client device 504 executes an IDE client 514 that allows the client device 504 to access the project development tools and environment of the IDE system. The IDE client 514 can be provided to the client device 504 by the IDE system 202, or can be a client application installed on the client device 504 and configured to interface with the IDE system 202. The user can interact with the IDE client 514 to copy a version 3021 of the system project 302 from the cloud-based IDE system 202 to the local storage of the client device for local viewing and development. After the local version 3021 is copied, the master copy of the system project 302 is maintained on the IDE system 202.

[0110] Once copied to the client device 504, the developer can view and edit the local version 3021 using the project development tools supported by the IDE client 514. At least some of these development tools may be similar to those supported by the IDE system 202 described above (see, e.g., Figure 5 ). For example, some embodiments of the IDE client 514 may support the use of design guardrails to ensure that local edits made to the local version 3021 of the project - e.g., control program changes, HMI modifications, changes to device configuration parameters, modifications to automation objects, etc. - comply with internal or external design standards. As in the previous example, various embodiments of the IDE client 514 may allow a user to submit edits to the local version 3021 of the project as one or more of control programming (e.g., ladder logic, DLS programming, sequential function charts, structured text, function block diagrams, etc.), design changes to a visualization application such as an HMI (e.g., addition, removal, or repositioning of graphical objects), industrial device configuration parameter values, or other such design inputs.

[0111] In an example scenario, a developer may choose to modify an existing system project 302 so that the project 302 is suitable for deployment on an automation system that has characteristics that deviate from a typical installation and requires modifications to the system project 302. For example, the system project 302 may be designed to program and configure a standardized automation system that is constructed to perform a specific industrial function and is installed at multiple locations or facilities of an industrial enterprise. A new installation of such an automation system may deviate from the standard installation of the system in a variety of ways, including but not limited to replacing one or more devices of the automation system with devices provided by an alternative supplier, adding or omitting a workstation, installing modifications to accommodate physical constraints of the installation location, special control requirements that deviate from standard requirements (e.g., differences in product design, control modifications to accommodate differences in materials or components used to manufacture a product), or other such deviations. In order to accommodate these changes, a developer may download a local version 3021 of the system project 302 and implement necessary modifications to the local version 3021.

[0112] Fig.14 302 is a diagram illustrating propagation of automation object edits to a locally stored copy of a system project 302. In this example scenario, a user at a client device 504b has downloaded a local version 3021 of the system project 302, as described above in connection with Fig.13 The automation object library 502 containing the master version of the automation object 222 is maintained and stored in the cloud platform in association with the IDE system 202. In this way, any authorized developer can access the object library 502 to not only add the selected automation object 222 to the system project 302, but also modify the selected automation object 222 as part of the project development, or to reflect the modification of the corresponding industrial asset represented by the object 222. Fig.14 In the example shown, a developer at a client device 504a submits a set of edits 1102 (e.g., updating the object's control code, visual representation, test script, etc.) to a selected automation object 222 stored on the library 502. In response to receiving these edits 1102, the project generation component 206 ( Fig.14 ) updates the master version of the selected automation object 222 stored in the library 502 based on the edit 1102.

[0113] In addition, when editing has been implemented on the selected automation object 222, the project generation component 206 also identifies all locally stored and remotely stored versions of any system project 302 that have incorporated an instance of the selected automation object 222. This includes identifying any system project 302 stored on cloud storage associated with the IDE system 202, as well as any version 3021 of the system project 302 that has been downloaded to a local client device (e.g., client device 504b) for local development. In this regard, the collaboration management component 212 can track all instances of the system project 302 that have been downloaded to the local client device so that these local versions of the project 302 can be updated as needed in response to modifications submitted to the cloud-based IDE system 202.

[0114] In response to the submission of the object edit 1102 and the corresponding modification of the master version of the automation object 222 targeted by the edit 1102, the project generation component 206 also distributes the automation object update 1402 to all IDE clients 514b on which local versions 3021 of the system project 302 that use the automation object 222 are stored. The update 1402 reflects the automation object edit 1102 submitted by the developer using the client device 504a and, when executed by the local IDE client 514b, updates all instances of the automation object 222 according to the edit 1102. In this manner, updates to the automation object 222 on the object repository 502 are automatically broadcast to all instances of the object 222 currently used in the system project 302.

[0115] In some embodiments, a local developer at a client device 504b may be provided with an option to allow the update 1402 to be merged into its local version 3021 of the system project 302 or to reject the implementation of the update 1402. Thus, before updating the local version of the automation object 222, the user interface component 204 may present information about the object edit 1102 on the user's client device 504b, and may also present a prompt for the developer to approve the local implementation of the edit. The information about the edit 1102 may include, for example, the identification of the automation object 222 affected by the edit, and a summary of each modification to the object 222 that will be implemented by the edit (e.g., an indication of which object properties will be modified and how these properties will be changed). Based on a review of these edits, the local developer may choose to implement the update 1402 on its local version 3021, or alternatively, reject the edit and prevent the update 1402 from being implemented on its local version 3021 of the project 302.

[0116] As described above, the system project 302 may include one or more project data models 602 that define a collection of automation objects 222 and hierarchical relationships between the objects 222. In some development scenarios, a designer may create a project data model 602 by selecting the automation objects 222 to be included in the system project 302 (e.g., based on the physical industrial assets that make up the automation system to be monitored and controlled) and the relationships or dependencies between these automation objects 222, which may reflect the real-world functional and / or physical relationships between the corresponding industrial assets of the automation system. Alternatively, in some embodiments, the project generation component 206 may automatically select and arrange appropriate automation objects 222 to be included in the system project 302 based on the design input 512 (e.g., design goals, engineering drawings, etc.) submitted by the developer. Since certain types of automation systems, machines, or processes are commonly used in different industrial enterprises, one or more embodiments of the industrial IDE system 202 may also maintain a library of predefined project data models 602 that represent collections and configurations of industrial assets that are frequently used at industrial facilities.

[0117] Fig.15 1 is a diagram showing the selection of a predefined project data model 602 from a model library 1502. In some embodiments, the model library 1502 may be included as part of an industrial knowledge base of an IDE system, where guardrail templates 506, code models 508, visualizations 510, etc. are also stored (see Figure 5 ). The predefined project data models 602 stored in the library 1502 can represent a similar collection of industrial assets that make up a type of automated system, machine, or process; for example, a type of batch process, a type of stamping press, a water treatment process, an extrusion process, a palletizer, a die casting process, a conveyor control system, a paper feeder, a flow control process, or other such system or process. The project data model 602 representing a type of industrial machine or process defines a collection of automation objects 222 representing the industrial assets (e.g., tanks, pumps, valves, motor drives, conveyors, etc.) that make up the machine or process, and the hierarchical or functional relationships between these objects 222, which reflect the physical or functional relationships between their corresponding physical industrial assets as described above.

[0118] The model library 1502 may categorize the predefined project data models 602 according to any suitable categories to assist the designer in locating and selecting appropriate data models 602 for inclusion in the system project 302. For example, the library 1502 may categorize the data models 602 according to the type of industry or industrial vertical market (e.g., automotive, food and drug, oil and gas, pharmaceuticals, textiles, mining, etc.), the type of industrial asset (e.g., the type of machine or industrial equipment), the type of industrial machine or process, or other such categories. In some embodiments, the user interface component 204 may present a browsable interface on the client device 504 that allows the developer to browse the model classification scheme and view the available project data models 602 under the corresponding different model classifications or categories, and submit a model selection input (part of the design input 512) that selects one or more available data models 602a to include in the system project 302. When a predefined project data model 602 a is selected from the library for inclusion in the system project 302 , the project generation component 206 integrates both the selected data model 602 a and any automation objects 222 defined by the selected model 602 into the current system project 302 .

[0119] In some embodiments, as an alternative to manually selecting data models 602 to include in the system project 302, the project generation component 206 can automatically select and recommend one or more suitable data models 602 to include in the system project 302 based on inferences drawn from the user's design input 512. For example, similar to the example described above, the project generation component 206 can be configured to monitor the design input 512 submitted for the system project 302 over time, and based on the monitoring, learn the correlation between certain design actions (e.g., adding certain code modules or code segments to the system project 302, selecting certain visualizations, etc.) and the type of industrial machine or process being designed. The project generation component 206 can record these learned correlations and generate recommendations based on these correlations during subsequent project development. For example, during project development, the project generation component 206 can infer based on the user's design input 512 that the user is in the process of generating a system project 302 for monitoring and controlling a specific type of industrial machine or process. Based on this inference, the project generation component 206 can generate and present a recommendation to integrate the predefined data model 602 a and its associated automation objects 222 into the system project 302 .

[0120] In general, the project generation component 206 can infer the current programming task or design goal of the project developer based on the design input 512 provided to the IDE system 202, and determine whether one of the predefined data models 602a can be appropriately added to the system project 302 being developed based on the task or goal. For example, the project generation component 206 can infer based on the analysis of the design input 512 that the programmer is currently configuring a project 302 for monitoring and controlling a sheet metal stamping press. In response to this determination, and a determination that the model library 1502 includes a data model 602a corresponding to a similar type of stamping press, the project generation component 206 can recommend that the data model 602a and any automation objects 222 defined by the data model 602a be integrated into the system project 302. The recommendation can be presented by the user interface component 204 on the client device 504.

[0121] Any predefined data model 602a integrated into the system project 302 may also be modified or customized by the developer, if necessary, to capture any design deviations between the physical automation system or process being designed and the system or process configuration defined by the data model 602a. For example, a predefined data model 602a for a given type of wastewater treatment system may specify a different type of pump than that used in the actual system being designed, or may specify a different arrangement of industrial assets that make up the system. In such a case, the developer may make the necessary modifications to the data model 602; for example, by editing or replacing any automation object 222 defined by the model 602, or by modifying any relationship between the objects 222 defined by the model 602. Alternatively, in some embodiments, the project generation component 206 may infer and automatically implement modifications to the selected data model 602a so that the model 602a is consistent with the physical system for which the project 302 is being designed. In an example scenario, such an inference may be based on a comparison between the project data model 602a representing the automation system or process and the engineering drawing submitted by the developer as part of the design input 512. In this case, the project generation component 206 can identify the devices that make up the system being designed and the physical or functional relationships between the devices based on the analysis of the drawings.

[0122] In some implementations, an authorized entity may submit a custom data model 602 to the IDE system 202 for storage in the model library 1502 and distribution to end users. For example, an OEM entity may create a project data model 602 and any associated automation objects 222 designed to operate in conjunction with a custom machine provided by the OEM. The OEM may submit the data model 602 (and associated automation objects 222 that are not already available in the automation object library 502) to the IDE system 202, which stores the submitted model 602 in the model library 1502. As part of the model submission process, the OEM may indicate a classification for the submitted model 602, which indicates how the IDE system 202 should classify the model in the library 1502. This may include, for example, identifying the relevant industrial vertical market for the model, the type of machine or industrial application, the scenarios in which the model 602 may be appropriately applied, and the like. The OEM may also impose restrictions on the end users that are allowed to incorporate the submitted data model 602 into their system project 302; for example, by only allowing the OEM's customers to access the submitted model 602. The IDE system 202 will manage the distribution of the submitted data model 602 based on these security definitions.

[0123] In some implementations, users may also create project data models 602 as part of their system projects 302 and, if desired, store these custom data models 602 to the model library 1502 . Fig.16 is a diagram illustrating the creation and storage of a custom data model 602. As described in the previous example, a user can generate a system project 302 by submitting design input 512 to the IDE system 202 in various formats (e.g., design goals, explicit control programming, engineering drawings, AR / VR interactions, etc.). The generated system project 302 may include various automation objects 222, which have functional relationships with each other as defined by the project developer. The selection of automation objects 222 and their functional relationships can reflect the corresponding arrangement of industrial assets that constitute the automation system or process for which the system project 302 is being developed. These defined relationships can determine how the properties of the automation objects 222 are related to each other; for example, how their associated control code properties are linked to produce composite control programming, how their visualization properties are aggregated to produce a composite presentation of the automation system or process, etc. The identification of the automation objects 222 included in the project 302 and their defined relationships together define the project data model 602.

[0124] In some embodiments, at least a portion of the project data model 602 can be automatically generated by the project generation component 206 based on an analysis of engineering drawings submitted by a developer as part of the design input 512. For example, based on an analysis of a P&ID drawing of an industrial system for which the system project 302 is being developed, the project generation component 206 can identify industrial assets (e.g., tanks, pumps, motor drives, conveyors, etc.) and the relationships between the industrial assets represented in the drawing. Industrial assets can also be identified from other types of drawings, including but not limited to I / O drawings, mechanical drawings, or other types of engineering drawings. The project generation component 206 can then associate or map the elements identified in the drawing with corresponding automation objects 222 representing these identified assets and add these automation objects 222 to the system project 302. The project generation component 206 can also define physical or functional relationships between these automation objects to reflect the relationships between their corresponding assets as determined from the engineering drawings.

[0125] If desired, the developer may choose to save the resulting data model 602 to the model library 1502 for use by other developers or integration into other system projects 302. To this end, a model archive command 1602 may be submitted to the system 202 via the user interface component 204, the model archive command 1602 instructing the project generation component 206 to initiate archiving of the developer's project data model 602 to the model library 1502. In some scenarios, the archive command 1602 may include classification information indicating how the project generation component 206 should classify the copy of the data model 602a in the library 1502. The classification information may specify one or more categories or subcategories under which the data model 602a should be classified (e.g., the industrial vertical market in which the data model 602a is used, the type of industrial machine or process represented by the data model 602a, etc.). The archive command 1602 may also specify access permissions that define users, user roles, or entities that are allowed to retrieve and use the data model 602a in their system projects 302.

[0126] The predefined data models 602 described herein define meaningful configurations and arrangements of automation objects 222 that are commonly applicable in many industrial enterprises and applications. These predefined data models 602 can be categorized and provided to end users to selectively include in their system projects 302, thereby reducing development time and simplifying the process of building appropriate system projects 302.

[0127] Fig.17 and Fig.18An example method according to one or more embodiments of the present application is shown. Although for the purpose of simplifying the description, the method shown herein is shown and described as a series of actions, it should be understood and appreciated that the present invention is not limited to the order of the actions, because according to the present invention, some actions can occur in an order different from the order shown and described herein and / or occur simultaneously with other actions. For example, those skilled in the art will understand and appreciate that the method can be alternatively represented as a series of interrelated states or events such as in a state diagram. In addition, not all the actions shown are necessary to realize the method according to the present invention. In addition, when different entities formulate different parts of the method, (one or more) interaction diagrams can represent the methodology or method according to the present disclosure. In addition, two or more of the disclosed example methods can be implemented in combination with each other to realize one or more features or advantages described herein.

[0128] Fig.17 An example method 1700 for creating and storing a project data model is shown, which defines an arrangement of automation objects representing an industrial machine or process, which can be incorporated into an industrial system project. Initially, at 1702, industrial design data is received via interaction with an industrial IDE system. The industrial design data can be submitted in the form of one or more of the following: industrial controller programming (e.g., ladder logic, sequential function chart, script control code such as industrial DSL, etc.), HMI screen development input, industrial equipment or equipment selection, engineering drawing input, etc. In some embodiments, the industrial design data can also include complete engineering drawings (e.g., P&ID diagrams, electrical diagrams, mechanical diagrams, etc.), which can be parsed and analyzed by the industrial IDE to identify the components being designed in the industrial automation system (e.g., industrial equipment, machines, equipment, conduits, pipes, etc.) and the functional and physical relationships between these components.

[0129] In some embodiments, the design data may also include images or videos. For example, an image or video of the installation site where the industrial automation system being designed will be installed may be submitted to the industrial IDE, which may analyze the image or video to identify physical elements (e.g., walls, beams, safety fences, existing machines and equipment, etc.) within the installation area and the physical relationships between these elements (e.g., the distance between machines or other physical elements, the length of pipeline laying, the location and distance of wire harnesses or cable trays, etc.). Based on the results of the mapping or image / video analysis, the industrial IDE may add components to the engineering schematic, generate control programming or visualization for the components identified in the mapping or image, generate appropriate device parameter settings, generate recommendations for optimal locations of equipment or machines, etc.

[0130] For implementations of the Industrial IDE that support target-based programming, the design data may also include indications of desired design goals and associated design constraints; for example, in terms of desired product or material output rates, maximum total energy consumption rates, constraints on installation space (which may be obtained based on images or videos of the installation site, as described above), or other such parameters. Based on these design goals and constraints, the Industrial IDE may generate at least a portion of an automation system project, including one or more of the following: equipment or device selection, control code, mapping, visualization, or device parameters that are capable of satisfying the specified design goals in view of the specified constraints.

[0131] At 1704, an industrial automation system project is generated based on the design data received at step 1702. As part of the project generation process, a project data model is generated that defines instances of automation objects representing various industrial assets and functional relationships between automation objects. Automation objects are building blocks for industrial automation system projects and represent various types of real-world industrial assets or processes, including but not limited to pumps, tanks, valves, motors, motor drives (e.g., variable frequency drives), industrial robots, actuators (e.g., pneumatic or hydraulic actuators), or other such assets. Automation objects are associated with various attributes or characteristics (e.g., control code, visualization objects or interfaces, test scripts, security features or protocols, etc.) according to the assets or processes they represent. In addition to defining the automation objects to be included in the system project, the data model also defines functional relationships between automation objects, which can reflect functional or physical relationships between similar industrial assets that make up the industrial system for which the system project is being developed.

[0132] At 1706, it is determined whether an instruction has been received to archive the system data model in a model repository for access by other developers or integration into other system projects. If such an instruction has been received ("yes" at step 1706), the method proceeds to step 1708, where a copy of the project data model is stored in the model repository for selective integration into other system projects. The project data model may be stored in the repository along with other available project data models classified according to a hierarchical classification schema. Example classification categories in which the data model may be stored may include, but are not limited to, the industrial vertical market to which the data model relates, the type of industrial machine or process, the industrial application, the scenario to which the project data model may be relevant, or other such categories.

[0133] Fig.18An example method 1800 is shown for selectively integrating a system data model into an industrial system project based on inferences about the industrial machine or process for which the project is being developed. Initially, at 1802, industrial design data for the industrial system project is received via interaction with an industrial IDE system (similar to step 1702 of method 1700). At 1804, based on an analysis of the industrial design data received at step 1802, inferences are made about the industrial machine or process for which the industrial system project is being designed. Such inferences may be based on any subset of the submitted design data, including but not limited to engineering drawings or bills of materials submitted to the IDE system, control programming submitted by a designer, or other such design input.

[0134] At 1806, it is determined whether a predefined project data model is available for the industrial machine or process inferred at step 1804. The project data model may be stored in a model library along with other project data models representing a series of industrial machines or processes. Each of the project data models defines a set of automation objects and their corresponding industrial machines or processes and functional relationships between the automation objects. If the predefined project data model is available for the inferred industrial machine or asset ("yes" at step 1806), the method proceeds to step 1808, where the project data model is integrated into the industrial system project.

[0135] The embodiments, systems and components described herein, as well as control systems and automation environments that can implement various aspects set forth in this specification, may include computer or network components, such as servers, clients, programmable logic controllers (PLCs), automation controllers, communication modules, mobile computers, onboard computers for mobile vehicles, wireless components, control components, etc. that can interact across a network. Computers and servers include one or more processors (electronic integrated circuits that use electrical signals to perform logical operations), and the one or more processors are configured to execute instructions stored in media such as random access memory (RAM), read-only memory (ROM), hard drives, and removable memory devices, which may include memory sticks, memory cards, flash drives, external hard drives, etc.

[0136] Similarly, the term PLC or automatic controller used herein may include functions that can be shared across multiple components, systems and / or networks. As an example, one or more PLCs or automation controllers may communicate and collaborate with various network devices across networks. This may include substantially any type of controller, communication module, computer, input / output (I / O) device, sensor, actuator and human-machine interface (HMI) that communicate via a network, the network including a control network, an automation network and / or a public network. PLC or automation controllers may also communicate with and control various other devices, such as analog modules, digital modules, standard or safety-grade I / O modules, other programmable controllers, communication modules, sensors, actuators, output devices, etc., through programming modules / intelligent I / O modules.

[0137] The network may 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, etc. In addition, network devices may include various possibilities (hardware components and / or software components). These include components such as switches with virtual local area network (VLAN) capabilities, LANs, WANs, agents, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, and / or other devices.

[0138] To provide context for various aspects of the disclosed subject matter, Fig.19 and Fig. 20 The following discussion is intended to provide a brief, general description of a suitable environment in which various aspects of the disclosed subject matter can be implemented. Although various embodiments have been described above in the general context of computer-executable instructions that can be run on one or more computers, those skilled in the art will recognize that various embodiments can also be implemented in conjunction with other program modules and / or as a combination of hardware and software.

[0139] Generally, program modules include routines, programs, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In addition, those skilled in the art will appreciate that the methods of the present invention can be practiced with other computer system configurations, including single-processor or multi-processor computer systems, minicomputers, mainframe computers, Internet of Things (IoT) devices, distributed computing systems, and personal computers, handheld computing devices, microprocessor-based or programmable consumer electronics, etc., each of which can be operably coupled to one or more associated devices.

[0140] The embodiments shown in this article can also be practiced in distributed computing environments, in which 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.

[0141] Computing devices typically include various media, which may include computer-readable storage media, machine-readable storage media, and / or communication media, which terms are used differently from each other in this article as follows. Computer-readable storage media or machine-readable storage media can be any available storage media that can be accessed by a computer, and include both volatile and non-volatile 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 conjunction with any method or technology for storing information such as computer-readable or machine-readable instructions, program modules, structured data, or unstructured data.

[0142] Computer-readable storage media may 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 disk (BD) or other optical disk storage, 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 that may be used to store the desired information. In this regard, the terms "tangible" or "non-transitory" as applied to storage, memory, or computer-readable media herein should be understood as excluding only the propagation of transient signals themselves as a modifier, and not as a disclaimer of all standard storage, memory, or computer-readable media that propagate more than just transient signals themselves.

[0143] Computer-readable storage media can be accessed by one or more local computing devices or remote computing devices, such as via access requests, queries, or other data retrieval protocols, to perform various operations on the information stored by the media.

[0144] Communication media typically embodies computer readable instructions, data structures, program modules, or other structured or unstructured data in a data signal such as a modulated data signal such as a carrier wave or other transmission mechanism, and includes any information transfer or transmission media. The term "modulated data signal" or signal refers to a signal that sets or changes one or more of its characteristics in a manner that encodes 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.

[0145] Refer again Fig.19 , an example environment 1900 for implementing various embodiments of various aspects described herein includes a computer 1902, which includes a processing unit 1904, a system memory 1906, and a system bus 1908. The system bus 1908 couples system components including, but not limited to, the system memory 1906 to the processing unit 1904. The processing unit 1904 can be any of a variety of commercially available processors. Dual microprocessors and other multi-processor architectures can also be used as the processing unit 1904.

[0146] The system bus 1908 may be any of several types of bus structures that may also 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 1906 includes ROM 1910 and RAM 1912. A basic input / output system (BIOS) containing the basic routines that help to transfer information between elements within the computer 1902, such as during startup, may be stored in a nonvolatile memory such as a ROM, an erasable programmable read-only memory (EPROM), or an EEPROM. RAM 1912 may also include a high-speed RAM such as a static RAM for caching data.

[0147] The computer 1902 also includes an internal hard disk drive (HDD) 1914 (e.g., EIDE, SATA), one or more external storage devices 1916 (e.g., a magnetic floppy disk drive (FDD) 1916, a memory stick or flash drive reader, a memory card reader, etc.), and an optical drive 1920 (e.g., which can read from or write to a CD-ROM disk, DVD, BD, etc.). Although the internal HDD 1914 is shown as being located within the computer 1902, the internal HDD 1914 can also be configured for external use in a suitable rack (not shown). In addition, although not shown in the environment 1900, a solid state drive (SSD) can be used in addition to the HDD 1914, or a solid state drive (SSD) can be used instead of the HDD 1914. The HDD 1914, external storage device(s) 1916, and optical drive 1920 can be connected to the system bus 1908 via a HDD interface 1924, an external storage interface 1926, and an optical drive interface 1928, respectively. The interface 1924 for external drive implementations may include at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

[0148] The drive and its associated computer-readable storage media provide non-volatile storage of data, data structures, computer-executable instructions, etc. For the computer 1902, the drive and storage media accommodate the storage of any data in a suitable digital format. Although the above description of computer-readable storage media relates to corresponding types of storage devices, it should be understood by those skilled in the art that other types of computer-readable storage media may also be used in the example operating environment, whether the storage media currently exists or is to be developed in the future, and further, any such storage media may contain computer-executable instructions for performing the methods described herein.

[0149] A number of program modules may be stored in the drives and RAM 1912, including an operating system 1930, one or more application programs 1932, other program modules 1934, and program data 1936. All or portions of the operating system, applications, modules, and / or data may also be cached in RAM 1912. The systems and methods described herein may be implemented using various commercially available operating systems or combinations of operating systems.

[0150] Computer 1902 may optionally include emulation technology. For example, a hypervisor (not shown) or other intermediary may emulate a hardware environment for operating system 1930, and the emulated hardware may optionally communicate with the operating system 1930. Fig.191902. In such an embodiment, operating system 1930 may include one of multiple virtual machines (VMs) hosted at computer 1902. In addition, operating system 1930 may provide a runtime environment, such as a Java runtime environment or a .NET framework, for application 1932. The runtime environment is a consistent execution environment that enables application 1932 to run on any operating system that includes the runtime environment. Similarly, operating system 1930 may support containers, and application 1932 may be in the form of a container, which is a lightweight, independent, executable software package that includes, for example, code, runtime, system tools, system libraries, and settings about the application.

[0151] In addition, the computer 1902 can be enabled with a security module such as a trusted processing module (TPM). For example, with respect to the TPM, the boot component hashes the boot component immediately preceding it in time and waits for the result to match a security value before loading the next boot component. This process can occur at any layer in the code execution stack of the computer 1902, for example, being applied at the application execution level or at the operating system (OS) kernel level, thereby enabling security at any code execution level.

[0152] A user may enter commands and information into the computer 1902 through one or more wired / wireless input devices such as a keyboard 1938, a touch screen 1940, and a pointing device such as a mouse 1942. Other input devices (not shown) may 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 a virtual reality headset, a game pad, a stylus, an image input device (e.g., (one or more) cameras), a gesture sensor input device, a visual movement sensor input device, an emotion or facial detection device, a biometric input device (e.g., a fingerprint or iris scanner), etc. These input devices and other input devices are typically connected to the processing unit 1904 through an input device interface 1944 that can be coupled to the system bus 1908, but may also be connected through other interfaces such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR interface, Interface, etc.

[0153] A monitor 1944 or other type of display device may also be connected to the system bus 1908 via a video adapter 1946, such as a video adapter. In addition to the monitor 1944, computers typically include other peripheral output devices (not shown), such as speakers, printers, and the like.

[0154] The computer 1902 can operate in a networked environment using logical connections via wired and / or wireless communications to one or more remote computers, such as remote computer(s) 1948. The remote computer(s) 1948 can be a workstation, server computer, router, personal computer, portable computer, microprocessor-based entertainment device, peer device, or other general network node, and typically includes many or all of the elements described with respect to the computer 1902, although only a memory / storage device 1950 is shown for simplicity. The depicted logical connections include wired / wireless connections to a local area network (LAN) 1952 and / or a larger network, such as a wide area network (WAN) 1954. Such LAN and WAN networking environments are common in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communications network, such as the Internet.

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

[0156] When used in a WAN networking environment, the computer 1902 may include a modem 1958 or may be connected to a communication server on the WAN 1954, such as through the Internet, via other means for establishing communications over the WAN 1954. The modem 1958, which may be internal or external and may be a wired device or a wireless device, may be connected to the system bus 1908 via the input device interface 1942. In a networking environment, program modules described with respect to the computer 1902 or portions thereof may be stored in the remote memory / storage device 1950. It should be appreciated that the network connections shown are examples and other means of establishing a communications link between the computers may be used.

[0157] When used in a LAN or WAN networking environment, the computer 1902 may access a cloud storage system or other network-based storage system in addition to or in lieu of the external storage devices 1916 as described above. Typically, a connection between the computer 1902 and the cloud storage system may be established through the LAN 1952 or WAN 1954, for example, through an adapter 1956 or a modem 1958, respectively. When the computer 1902 is connected to the associated cloud storage system, the external storage interface 1926 may manage the storage provided by the cloud storage system as other types of external storage with the aid of the adapter 1956 and / or the modem 1958. For example, the external storage interface 1926 may be configured to provide access to cloud storage sources as if those sources were physically connected to the computer 1902.

[0158] The computer 1902 is operable to communicate with any wireless device or entity operatively arranged in wireless communications, such as printers, scanners, desktop and / or portable computers, portable data assistants, communication satellites, any equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, newsstand, store shelf, etc.), and telephones. This may include Wireless Fidelity (Wi-Fi) and Wireless technology. Thus, the communication may be a predefined structure like a conventional network or simply an ad hoc communication between at least two devices.

[0159] Fig. 202000 is a schematic block diagram of a sample computing environment 2000 with which the disclosed subject matter can interact. The sample computing environment 2000 includes one or more clients 2002. The client 2002 can be hardware and / or software (e.g., a thread, a process, a computing device). The sample computing environment 2000 also includes one or more servers 2004. The server 2004 can also be hardware and / or software (e.g., a thread, a process, a computing device). The server 2004 can accommodate threads to perform transformations by adopting one or more embodiments described herein, for example. A possible communication between the client 2002 and the server 2004 can be in the form of a data packet suitable for transmission between two or more computer processes. The sample computing environment 2000 includes a communication framework 2006 that can be used to facilitate communication between the client 2002 and the server 2004. The client 2002 is operably connected to one or more client data storage devices 2008 that can be used to store local information of the client 2002. Similarly, the server 2004 is operably connected to one or more server data storage devices 2010 that can be used to store information local to the server 2004 .

[0160] The above description includes examples of the present invention. Of course, it is not possible to describe every conceivable combination of components or methods for the purpose of describing the disclosed subject matter, but one of ordinary skill in the art will recognize that many additional combinations and arrangements of the present invention are possible. Therefore, the disclosed subject matter is intended to cover all such changes, modifications and variations that fall within the spirit and scope of the appended claims.

[0161] In particular, with respect to the various functions performed by the components, devices, circuits, systems, etc. described above, unless otherwise indicated, the terms used to describe such components (including references to "means") are intended to correspond to any component (e.g., any component that is functionally equivalent) that performs the specified functions of the described components, even if not structurally equivalent to the disclosed structures, which performs the functions in the exemplary aspects of the disclosed subject matter shown herein. In this regard, it should also be recognized that the disclosed subject matter includes systems as well as computer-readable media having computer-executable instructions for performing the actions and / or events of the various methods of the disclosed subject matter.

[0162] Furthermore, while particular features of the disclosed subject matter may be disclosed for only one of several implementations, such features may be combined with one or more other features of other implementations as may be desired and advantageous for any given application or particular applications. Furthermore, to the extent the terms "includes" and "including" and variations thereof are used in the specification or claims, these terms are intended to be inclusive in a manner similar to the term "consisting of".

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

[0164] The various aspects or features described herein may be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program that can be accessed from any computer-readable device, carrier, or medium. For example, a computer-readable medium may include, but is not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips, ...), optical disks [e.g., compact disks (CDs), digital versatile disks (DVDs) ...], smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

Claims

1. A system for developing industrial applications, comprising: a memory storing executable components, a model library storing project data models corresponding to respective industrial machines or processes, and a library of automation objects representing respective industrial assets, the automation objects having respective programming attributes associated with the industrial assets; as well as A processor, the processor being operably coupled to the memory, the processor executing the executable component, the executable component comprising: A user interface component configured to: present an integrated development environment (IDE) interface and receive industrial design input via interaction with the IDE interface, the industrial design input comprising a model selection input that selects one of the project data models; and a project generation component configured to generate system project data, the project generation component configured to: in response to selection of one of the project data models by the industrial design input, integrate one of the project data models into the system project data, in, The system project data defines a system project, wherein the system project includes at least one of an executable industrial control program, an industrial visualization application, or industrial equipment configuration data, the programming attributes of the automation object in the automation object include a test script configured to verify the operation of the automation object within the system project, one of the project data models defines subsets of automation objects corresponding to industrial assets constituting the industrial machine or process and functional relationships between the subsets of automation objects, One of the project data models defines a hierarchical relationship between an instance of a first automation object in the subset of automation objects and an instance of a second automation object in the subset of automation objects, The properties of the first automation object include a first control logic, and the properties of the second automation object include a second control logic, and The project generation component is configured to associate a first data tag of the first control logic with a second data tag of the second control logic according to a hierarchical relationship defined by one of the project data models.

2. The system according to claim 1, wherein: generating one of the project data models based on a subset of the industrial design inputs defining the project data model, and The project generation component is further configured to, in response to receiving an instruction to archive one of the project data models, store a copy of one of the project data models in the model repository.

3. The system according to claim 1, wherein: The model library classifies the project data models according to a classification pattern, and The classification categories of the classification schema include at least one of an industrial vertical market, an industrial machine, an industrial process, or an industrial application.

4. The system according to claim 1, wherein: The programming attributes of the automation object in the automation object include at least one of the following: control code for monitoring and controlling an industrial asset represented by the automation object, a visualization object defining a graphical visualization of the industrial asset, an alarm definition for the industrial asset, a security feature of the industrial asset, a security protocol for the industrial asset, or an analysis script configured to perform analysis on data generated by the industrial asset.

5. The system according to claim 1, wherein: The automation object represents at least one of an industrial process, a controller, a control program, a tag within the control program, a machine, a motor, a motor drive, a telemetry device, a tank, a valve, a pump, an industrial safety device, an industrial robot, or an actuator as the industrial asset.

6. A method for developing an industrial application, comprising: storing, by a system including a processor, an item data model in a model repository, the item data model representing a corresponding industrial machine or process; The system presents an integrated development environment IDE interface on a client device; receiving, by the system via interaction with the IDE interface, industrial design input including a model selection input that selects one of the project data models; as well as generating, by the system, system project data, wherein generating the system project data comprises: integrating one of the project data models into the system project data in response to selection of one of the project data models by the industrial design input, the system project data comprising at least one of an executable industrial control program, an industrial visualization application, or industrial equipment configuration data, in, One of the project data models defines a set of automation objects representing industrial assets constituting the industrial machine or process and functional relationships between the set of automation objects, the automation objects in the set of automation objects having programming properties associated with the industrial assets to which the automation objects correspond, the programming properties of the automation objects in the set of automation objects include test scripts configured to verify the operation of the automation objects within the system project data, One of the project data models defines a hierarchical relationship between an instance of a first automation object in the set of automation objects and an instance of a second automation object in the set of automation objects, The properties of the first automation object include a first control logic, and the properties of the second automation object include a second control logic, and Generating the system project data includes associating a first data tag of the first control logic with a second data tag of the second control logic according to a hierarchical relationship defined by one of the project data models.

7. The method according to claim 6, further comprising: generating, by the system, one of the project data models based on a subset of the industrial design input, and storing, by the system in response to receiving an instruction to archive the project data model, a copy of one of the project data models in the model repository; or Archiving the project data model includes classifying the project data model according to a classification schema, and the classification category of the classification schema includes at least one of the following: an industrial vertical market, an industrial machine, an industrial process, or an industrial application.

8. The method according to any one of claims 6 to 7, wherein: The programming properties of the automation objects in the set of automation objects include at least one of the following: control code for monitoring and controlling the industrial asset represented by the automation object, a visualization object defining a graphical visualization of the industrial asset, an alarm definition for the industrial asset, a security feature of the industrial asset, a security protocol for the industrial asset, or an analysis script configured to perform analysis on data generated by the industrial asset.

9. The method according to any one of claims 6 to 7, wherein: The collection of automation objects represents at least one of an industrial process, a controller, a control program, a tag within the control program, a machine, a motor, a motor drive, a telemetry device, a tank, a valve, a pump, an industrial safety device, an industrial robot, or an actuator as the industrial asset.

10. A non-transitory computer readable medium having instructions stored thereon, the instructions in response to being executed causing a system including a processor to perform operations comprising: Presenting an integrated development environment IDE interface on a client device; receiving industrial design input from the client device via interaction with the IDE interface, the industrial design input comprising a model selection input that selects one of the project data models from a library of project data models; as well as generating system project data, wherein generating the system project data comprises: in response to a selection of one of the project data models by the industrial design input, integrating one of the project data models into the system project data, in, Generating system project data includes: generating at least one of an executable industrial control program, an industrial visualization application, or industrial equipment configuration data, One of the project data models defines a set of automation objects representing functional relationships between the set of automation objects and the industrial assets constituting the industrial machine or process, An automation object in the set of automation objects has a programming attribute associated with an industrial asset corresponding to the automation object, and the programming properties of the automation objects in the set of automation objects include test scripts configured to verify the operation of the automation objects within the system project data, One of the project data models defines a hierarchical relationship between an instance of a first automation object in the set of automation objects and an instance of a second automation object in the set of automation objects, The properties of the first automation object include a first control logic, and the properties of the second automation object include a second control logic, and Generating the system project data includes associating a first data tag of the first control logic with a second data tag of the second control logic according to a hierarchical relationship defined by one of the project data models.

11. The non-transitory computer readable medium of claim 10, wherein: The generating system project data includes selecting one of the project data models from a library of project data models, the library of project data models being categorized in a model library.

Images