Abstract: An automation control system is provided that includes a distributed automation component that receives and processes delta scripts describing state changes to one or more objects of a persistent object model.

Abstract: Aspects describe multiple interface support that provides dynamic switching between new and old interface revisions. A first interface application is selected from a set of alternative interface applications for an industrial automation system. Support for each interface application included in the set of alternative interface applications is provided. A second interface application is downloaded and associated with the first interface application. The second interface application is enabled during runtime. If needed, the second interface application can be selectively disabled and an operation resumed with the first interface application.

Abstract: An automation control system is provided that includes a distributed automation component that receives and processes delta scripts describing state changes to one or more objects of a persistent object model.

Abstract: An automation control system is provided that includes delta scripts that describe one or more changes of the stored state information. The delta scripts may be useful to enable one or more other components of the control system and the one or more other components apply the one or more delta scripts to update state information stored on the one or more other components based upon the one or more changes.

Abstract: An automation control and monitoring system is provided that includes chainable plug-ins that may work in combination with one another to transform data or generate events. Resources of the automation control and monitoring system may be polymorphically defined based upon a generalized object model. The chainable plug-ins may be chained to make use of and/or affect a resource of any type.

Abstract: An automation control system is provided that includes a first component that stores state information of an object of the automation control system. Additionally, the first component generates one or more delta scripts that describe one or more changes of the stored state information. Further, the first component transmits the one or more delta scripts to one or more other components of the control system and the one or more other components apply the one or more delta scripts to update state information stored on the one or more other components based upon the one or more changes.

Abstract: A control and monitoring system is provided that includes an automation controller. The system includes a distributed model stored on the automation controller. Changes to the distributed model are provided via delta scripts that define only the changes to the model. Further, the control and monitoring system 24 includes distributed execution engines that execute commands based upon trigger events determined in the system. a plurality of automation control components networked together and with the automation controller, wherein the plurality of automation control components are capable of load balancing among the plurality of automation control components in response to performance demands of the control and monitoring system. These features of the control and monitoring system enable load balancing, data and processing redundancy, and collaborative design within the control and monitoring system.

Abstract: Aspects describe multiple machine interfaces that provide automated implementations of a host that executes at least one service. The service comprises internal aspects, which include a reusable definition and a specification, which are hidden from a user or selectively exposed but not modifiable by the user. Functional connections and controls are provided for the automated implementations of the host. Platform configurations, which include the at least one service, interact with the automated implementation of the host. One or more functionalities of the functional connections can be selectively exposed based on a user credential. The automated implementation of the host comprises execution of the at least one service.

Abstract: System(s), apparatus(es) and method(s) are provided for to managing and developing an industrial system included in the industrial environment. Intelligence related to a configuration of the industrial system is collected and processed to generate information related to operational condition(s) of the industrial system. Intelligence can be collected actively or passively: In active collection, a platform that collects the intelligence retrieves configuration record(s) from the industrial system, whereas in passive collection, the platform received one or more configuration records from the industrial automation system. Collected intelligence is cast into a set of configuration units that defines industrial system and functionality thereof. In addition, a set of services configured to convey specific functionality associated with at least one configuration unit is composed.

Abstract: Aspects describe an apparatus, method and system for constructing an application in an industrial automation system. An identification component can receive at least one requirement of the application. Based upon the at least one requirement, the identification component can select at least one service that satisfies the at least one requirement. The at least one service can be associated with at least one operational requirement. The identification component can match at least one host to the at least one service by matching the at least one operational requirement with at least one capability of the at least one service.

Abstract: Aspects describe multiple interface support that provides dynamic switching between new and old interface revisions. A first interface application is selected from a set of alternative interface applications for an industrial automation system. Support for each interface application included in the set of alternative interface applications is provided. A second interface application is downloaded and associated with the first interface application. The second interface application is enabled during runtime. If needed, the second interface application can be selectively disabled and an operation resumed with the first interface application.

Abstract: Aspects describe multiple interface support that provides dynamic switching between new and old interface revisions. A first interface application is selected from a set of alternative interface applications for an industrial automation system. Support for each interface application included in the set of alternative interface applications is provided. A second interface application is downloaded and associated with the first interface application. The second interface application is enabled during runtime. If needed, the second interface application can be selectively disabled and an operation resumed with the first interface application.

Abstract: System(s) and method(s) are provided for implementing a set of interface components across a set of layers of an industrial environment, and for managing at least one interface component or at least one layer of the industrial environment. To implement an interface component in at least one layer in the set of layers, a specification that defines the interface component is acquired and, based at least on the specification, a service is generated. Execution of the service implements the interface component. The managing includes deploying or discovering the at least one interface component or the at least one layer of the industrial environment. The managing also includes indexing specific functional feature(s) of the at least one interface component and searching across the set of layers for one or more interface components that satisfy specific functional criteria. Moreover, the managing can include supplying metadata related to interface component(s) or layer(s).

Abstract: System(s) and method(s) are provided for implementing a set of interface components across a set of layers of an industrial environment, and for managing at least one interface component or at least one layer of the industrial environment. To implement an interface component in at least one layer in the set of layers, a specification that defines the interface component is acquired and, based at least on the specification, a service is generated. Execution of the service implements the interface component. The managing includes deploying or discovering the at least one interface component or the at least one layer of the industrial environment. The managing also includes indexing specific functional feature(s) of the at least one interface component and searching across the set of layers for one or more interface components that satisfy specific functional criteria. Moreover, the managing can include supplying metadata related to interface component(s) or layer(s).

Abstract: System(s), apparatus(es) and method(s) are provided for to managing and developing an industrial system included in the industrial environment. Intelligence related to a configuration of the industrial system is collected and processed to generate information related to operational condition(s) of the industrial system. Intelligence can be collected actively or passively: In active collection, a platform that collects the intelligence retrieves configuration record(s) from the industrial system, whereas in passive collection, the platform received one or more configuration records from the industrial automation system. Collected intelligence is cast into a set of configuration units that defines industrial system and functionality thereof. In addition, a set of services configured to convey specific functionality associated with at least one configuration unit is composed.

Abstract: Aspects describe multiple interface support that provides dynamic switching between new and old interface revisions. A first interface application is selected from a set of alternative interface applications for an industrial automation system. Support for each interface application included in the set of alternative interface applications is provided. A second interface application is downloaded and associated with the first interface application. The second interface application is enabled during runtime. If needed, the second interface application can be selectively disabled and an operation resumed with the first interface application.

Abstract: Aspects describe multiple machine interfaces that provide automated implementations of a host that executes at least one service. The service comprises internal aspects, which include a reusable definition and a specification, which are hidden from a user or selectively exposed but not modifiable by the user. Functional connections and controls are provided for the automated implementations of the host. Platform configurations, which include the at least one service, interact with the automated implementation of the host. One or more functionalities of the functional connections can be selectively exposed based on a user credential. The automated implementation of the host comprises execution of the at least one service.

Abstract: Aspects describe an apparatus, method and system for constructing an application in an industrial automation system. An identification component can receive at least one requirement of the application. Based upon the at least one requirement, the identification component can select at least one service that satisfies the at least one requirement. The at least one service can be associated with at least one operational requirement. The identification component can match at least one host to the at least one service by matching the at least one operational requirement with at least one capability of the at least one service.