System and method for integrated workflow scaling

• US 9,436,922 B2
• Filed: 04/02/2014
• Issued: 09/06/2016
• Est. Priority Date: 10/15/2010
• Status: Active Grant

• Current Assignee: Schneider Electric Software, LLC (Schneider Electric SE)
• Original Assignee: Invensys Systems Incorporated (Invensys PLC)
• Inventors: Agarwal, Arvind, Shah, Sanjay M., Troy, Thomas A.
• Primary Examiner(s): Truong, Camquy
• Application Number:
  US14/243,101
• Publication Number:
  US 20140214478A1
• Time in Patent Office: 888 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/433 Dependency analysis; Data or control flow analysis
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/0633 Workflow analysis

Abstract

A system is provided. The system comprises a first computer located in a first plant, a first memory, and a first object based process management application stored in the first memory. The system further comprises a second computer located in a location separate from the first plant, a second memory, and a second object based process management application stored in the second memory. When executed on the first computer, the first application invokes scripts in response to events and the scripts launch tasks. When executed on the second computer, the second computer invokes scripts in response to events and the scripts launch tasks, one of the events acted on by the second application is a message received from the first application.

Claims

1. A method of defining a workflow comprised of objects, comprising:

opening an application interface associated with one of a manufacturing execution system (MES) application, a product lifecycle management (PLM) application, an enterprise resource planning (ERP) application, or a human machine interface (HMI);

in the application interface, defining a workflow comprising a plurality of tasks, wherein each task is defined as one or more objects; and

in the application interface, activating a first control to automatically generate an executable script to be attached to one of the objects, wherein when a first event occurs the executable script executes;

wherein the first event is associated with an event definition and/or event design window and/or dialog box that defines a first event trigger;

wherein the first event is linked to other tasks and/or other workflows;

wherein when the first event trigger occurs the linked task and/or the linked other workflow is launched by executing the generated executable script;

wherein the application interface includes a workflow builder interface which invokes one or more application programming interface calls to construct and build the workflow, the tasks, and the scripts; and

wherein the workflow builder interface is implemented in or interfaces with a plant model automation application for defining a workflow as an object oriented plant model wherein different aspects of the plant are modeled as objects, each object having attributes comprising at least one of temperature, state, pressure, and/or other values relating to its object; and

further comprising;

activating a second control to define a context of the first event wherein the second control automatically generates a second executable script to be attached to one of the objects, wherein when the first event occurs the second executable script executes.

2. The method of claim 1, wherein the context comprises information about the first event that is passed on to a task launched by the executable script.

3. The method of claim 1, wherein the executable script defines a first task that is launched when the script executes.

4. The method of claim 3, wherein the executable script is directed to a proxy, wherein the proxy identifies at run time on what computer system the first task is executed.

5. The method of claim 3, wherein the first task is associated with a first task object.

6. The method of claim 1, wherein the workflow is associated with one of a manufacturing process, a food making process, an oil refining process, or a chemical process.

7. The method of claim 1, wherein the workflow executes in part in a plant and in part in a central office.

8. The method of claim 1 wherein selecting an event tab of the application interface displays an event definition window and/or an event design window and/or a dialog box that promotes defining the event trigger.

9. The method of claim 1 wherein the workflow builder interface comprises a builder tab in a graphical user interface of the application interface for selecting a workflow builder window or workflow builder graphical user interface to be displayed.

10. The method of claim 1 wherein when defining and/or building an object using the workflow builder interface a tab on a graphical user interface window is presented by the workflow builder interface for configuring an event on the object that is automatically implemented by the workflow builder as a script.

11. The method of claim 10 wherein workflow builder interface promotes defining one or more events associated with a particular object, including at least one of events that occur at different thresholds of the value of a particular attribute of the particular object or events that occur related to different attributes of the particular object.

12. The method of claim 1 wherein when the user activates the first control to define an event, the application interface maps the event to a script hidden from the user which is associated with an object of the event.

13. A method of defining a workflow comprised of objects, comprising:

opening an application interface associated with one of a manufacturing execution system (MES) application, a product lifecycle management (PLM) application, an enterprise resource planning (ERP) application, or a human machine interface (HMI);

in the application interface, defining a workflow comprising a plurality of tasks, wherein each task is defined as one or more objects; and

in the application interface, activating a first control to automatically generate an executable script to be attached to one of the objects, wherein when a first event occurs the executable script executes;

wherein the first event is associated with an event definition and/or event design window and/or dialog box that defines a first event trigger;

wherein the first event is linked to other tasks and/or other workflows;

wherein when the first event trigger occurs the linked task and/or the linked other workflow is launched by executing the generated executable script;

wherein when an event occurs, an executable script executes causing a new task to launch or causing a workflow to terminate, wherein the script raises an event to a workflow subsystem, and the workflow subsystem channelizes the event to appropriate workflows; and

wherein the executed script causes other functionality to occur including an automated action comprising at least one of logging of process data or storing of process data.

14. A non-transitory computer-readable medium having computer-executable instructions stored thereon that, when executed by a processor, perform a method of defining a workflow comprised of objects, the method comprising:

opening an application interface associated with one of a manufacturing execution system (MES) application, a product lifecycle management (PLM) application, an enterprise resource planning (ERP) application, or a human machine interface (HMI);

in the application interface, defining a workflow comprising a plurality of tasks, wherein each task is defined as one or more objects; and

in the application interface, activating a first control to automatically generate an executable script to be attached to one of the objects, wherein when a first event occurs the executable script executes;

wherein the first event is associated with an event definition and/or event design window and/or dialog box that defines a first event trigger;

wherein the first event is linked to other tasks and/or other workflows;

wherein when the first event trigger occurs the linked task and/or the linked other workflow is launched by executing the generated executable script;

wherein when an event occurs, an executable script executes causing a new task to launch or causing a workflow to terminate, wherein the script raises an event to a workflow subsystem, and the workflow subsystem channelizes the event to appropriate workflows; and

wherein the executed script causes other functionality to occur including an automated action comprising at least one of logging of process data or storing of process data.