Service-oriented automation device and method for specifying a service-oriented automation device

• US 8,527,077 B2
• Filed: 02/20/2009
• Issued: 09/03/2013
• Est. Priority Date: 02/22/2008
• Status: Active Grant

• Current Assignee: Schneider Electric Automation GmbH (Schneider Electric SE)
• Original Assignee: Schneider Electric Automation GmbH (Schneider Electric SE)
• Inventors: Colombo, Armando Walter, Mendes, Joao Marco
• Primary Examiner(s): KASENGE, CHARLES R
• Application Number:
  US12/918,824
• Publication Number:
  US 20110066268A1
• Time in Patent Office: 1,656 Days
• Field of Search: 700/28, 700/29, 700/31, 700/95, 700/96, 700/97, 700/99, 700/100
• US Class Current: 700/96
• CPC Class Codes: G05B 19/056 Programming the PLC
• CPC Class Codes: G05B 2219/31196 SOAP, describes available services and how to call them remotely
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A method for specifying the behavior of autonomous and collaborative automation devices in manufacturing plants with a service-oriented architecture and to a service-oriented automation device. In order to describe the operating behavior of such devices, the invention proposes the steps of original setting-up of the automation device, including configuration, depiction of services, establishment of connections to other automation devices and transfer of the set-up to waiting original status, receiving the events through service operations, internal device interfaces of inputs/outputs and/or generated directly from the controls, evaluating the received events, executing the events and changing the state of the model-based middleware shell, wherein the system achieves the next state and is capable of receiving further events.

Claims

1. A process for operating autonomous, collaborative service-oriented automating devices (AG) of a production system at a manufacturing plant level as well as part of an enterprise IT system with service-oriented architecture, whereby the automating devices (AG) are coupled to production devices as well as to each other and offer functionalities of the automating devices and/or functionalities as service or aggregation of services, and/or ask for services or aggregation of services from automating devices (AG) of the manufacturing plant and/or of the enterprise IT system, whereby a setup of the automating devices (AG) is carried out comprising a configuration, definition of service and establishing of connections to other automating devices, whereby the behavior of the production system is based on the asynchronous exchange of service-events and service-calls with the goal of manufacturing a product according to a work plan,

characterized in that the behavior of each automating device (AG) is represented by a part of a middleware envelope that is formally specified by a HLPN (High Level Petri Net) model and is controlled by internal and/or external service-events and service calls, that a service-event received by an automating device (AG) is tested, whereby if the service-event corresponds to a description of a current status of the HLPN model, the production system is transferred into a new status by updating the HLPN model as well as by synchronization of service activities, whereby if the service-event is an exception, an undocumented service-event, or an internal conflict, a decision is made in such a manner that a service-event is generated if necessary information for the solution of the decision is present, and/or that services of external components (DMS) and/or of automating devices (AG) are queried in order to make information for a concrete decision available, and that after execution of the service-event and/or service-calls as well as development of the HLPN model, the production system reaches a next status and is ready for receiving further events.

2. The process according to claim 1, characterized in that status change of the system is carried out by updating the HLPN control model and synchronizing of service activities.

3. The process according to claim 1, characterized in that in order to handle exceptions, undocumented service-events or conflicts, services of a decision-making system (DMS) are queried in order to make suitable information available for a correct decision.

4. The process according to claim 1, characterized in that a service orientation as well as the event-based status change of the HLPN model of the service-oriented automating device (AG) follow rules of a “

token game”

of a high level Petri net.

5. The process according to claim 1, characterized in that an autonomous service-oriented control behavior is implemented in each of the automating devices (AG) which is connected to other automating devices (AG) based on the layout configuration of the manufacturing plant.

6. The process according to claim 1, characterized in that the middleware envelope makes possible behavior connections available based on the making available and/or service calls.

7. The process according to claim 1, characterized in that decision mechanisms associated with a behavior of aggregated services are influenced by information connected to the production system, including a manufacturing plant and higher-level components of the service-oriented enterprise IT system.

8. The process according to claim 1, characterized in that the complete behavior of the manufacturing plant is based on an asynchronous exchange of service-events and service-calls that are carried out by the service-oriented automating devices, and that the behavior formally follows that of the HLPN model.