Patent Grant
7778717
The invention pertains to digital data processing and, more particularly, by way of nonlimiting example, to automated workflow definition and processing. The invention has application, for example, in process control, environmental control, computer aided manufacturing, and other industrial and non-industrial applications.
Automated workflow processing is increasingly common in today's manufacturing plants. Conventional solutions provide general capabilities for interfacing plant equipment to identify events and take specific responsive actions. However, those solutions provide for only rudimentary workflow definition and require special-purpose programs to model plant operations of complexity. The conventional solutions, moreover, provide only limited interfaces, accepting data from and outputting data to only specific hardware devices and software applications.
This runs counter to modern trends, wherein plant owners—and, more generally, all those who own or run process control, environmental control, computer aided manufacturing, and other industrial and non-industrial applications—may wish to “mix and match” hardware devices and software solutions. Thus, for example, different areas of the plant floor and, certainly, of an enterprise as a whole may use different process control, environmental control, computer aided manufacturing, and other industrial and non-industrial equipment. The same is true of software (whether it be for control, “back office” reporting and analysis, and/or other applications) used on the plant floor and/or by the enterprise.
Significantly, this also runs counter to a trend for increased data distribution and visibility. Continuing the above example, those who own or run process control, environmental control, computer aided manufacturing, and other industrial and non-industrial applications, may wish to distribute data among different areas of the plant floor and/or within the enterprise as a whole, regardless of any existing diversity of hardware and software used. They may wish to do this to improve control, as well as reporting and analysis, on the plant floor and/or by the enterprise.
An object of this invention is to provide improved digital data processing systems and methods.
Another object is to provide such systems and methods as are suited to workflow definition and/or processing.
A further object is to provide such systems and methods as provide increased flexibility and workflow modelling processing over conventional systems.
A still further object is to provide such systems and methods as facilitate the mixing and integration of hardware devices and/or software solutions, e.g., whether for improved control, reporting, analysis, or otherwise, on a plant floor, in an enterprise, or otherwise.
Yet still another object of the invention is to provide such systems and methods as facilitate data distribution and visibility, e.g., among hardware devices and/or software solutions, whether of diverse varieties or otherwise.
These are among the objects attained by the invention which provides, in one aspect, improved methods and apparatus for workflow editing. Such methods and apparatus permit, for example, user-defined and/or other tasks to be combined in any combination to specify a workflow. The tasks can be linked for direct, serial processing and/or for conditional processing that includes branching and/or looping.
Related aspects of the invention provide such methods and apparatus as permit third-party (or unrelated) software applications to be invoked as tasks, with their respective contexts defined by environmental variables, e.g., which are interfaced through an applications program interface (API).
Further aspects of the invention provide such methods and apparatus which accept and process factory-floor or other process control, environmental control, computer aided manufacturing, and other industrial and non-industrial application data, regardless of its source. Related aspects of the invention provide for enhanced definition of data sources, data sinks and other tags.
Still further related aspects of the invention provide such methods and apparatus wherein workflow editing is preformed graphically, e.g., using panes that are organized hierarchically or otherwise. Yet still further aspects of the invention provide for definition of the workflow utilizing a graphical programming metaphor. Related aspects of the invention provide for graphical definition of information-flow among tasks and to/from other applications or devices.
Other aspects of the invention provide improved methods and apparatus of workflow definition and processing with extensible actions. Such methods and apparatus permit user definition of workflow tasks, e.g., using the graphical programming metaphor or otherwise. This includes, by way of non-limiting example, interfacing legacy software systems and databases.
Related aspects of the invention provide such methods and apparatus in which the actions conform to a component object model (COM) application program interface (API). That interface can define portions of a third-party application context required for task implementation and can provide mechanisms for communication of that information.
Extensible actions according to some aspects of the invention permits a workflow to interface with components and subsystems not part of the workflow system. This is done by permitting the workflow to instantiate component object model (COM) components that implement an extended action interface. A component of this type permits a workflow editor and workflow processing engine to interrogate the component for input and output arguments and other properties, as well as to cause the component to execute. The extended action interface provides a portal through which the workflow can give information to, and acquire information from, external systems.
Related aspects of the invention provide methods and apparatus as described above in which the input and output argument sets of such a component comprise a portion of an overall workflow context. An action can be executed with the input argument contexts and, upon return from the extended action component, entries in the output argument context can be written back to corresponding entries in the overall workflow context.
Still further related aspects of the invention provide such methods and apparatus as provide for enhanced communication between a task executing in a workflow processing engine and a third-party application.
Still other aspects of the invention provide improved methods and apparatus for workflow definition and processing which utilize workflow variables for communication of data and control information among tasks within a workflow. Such variables can reflect workflow status, factory-floor or other process control, environmental control, computer aided manufacturing, and other industrial and non-industrial application data and/or other parameters.
Related aspects of the invention such methods and apparatus as provide for persistence of the workflow variables, e.g., using XML or other markup languages.
Still other aspects of the invention provide improved methods and apparatus of workflow definition and processing with enhanced messaging. This facilitates communication with an operator station during workflow execution.
Related aspects of the invention provide such methods and apparatus in which both message content and formatting is transmitted between a workflow processing engine and an operator interface, e.g., via a markup language. Related aspects of the invention provide for use of XML and XSL for these purposes. Still further related aspects provide for customizable display of operator interfaces via controls which execute style sheets. Yet still further related aspects of the invention provide for enhanced transmittal of operator responses to the workflow processing engine.
Still other aspects of the invention provide improved methods and apparatus for workflow definition and processing which permit definition of hierarchically enumerated data types, referred to below as List PDIs. These can be used to capture multiple levels of data, e.g., for analysis or reporting.
Related aspects of the invention provide for definition of “plans” to collect, e.g., for storage, data such as the aforementioned hierarchical data types. These plans can include expressions that are evaluated on collection or storage of the data. Such expressions can include execution of procedures, e.g., for obtaining or evaluating further data.
Still other aspects of the invention provide improved methods and apparatus for workflow definition and processing which provide for registration of third-party and other software applications, e.g., used by an enterprise, and that facilitate communication with such applications. Related aspects of the invention facilitate information visibility, e.g., communication of information to/from portals and other data display/collection applications, networked or otherwise.
Still other aspects of the invention provide improved methods and apparatus for workflow definition and processing that utilize a common event-driven or other messaging structures, e.g., for transferring data to/from applications and/or operator interfaces.
Still other aspects of the invention provide improved methods and apparatus for workflow definition and processing that facilitate real-time gathering, processing, communication and/or reporting of data.
Advantages of methods and apparatus according to the foregoing and other aspects of the invention are that they facilitate distribution of data upon event occurrence. This can include, by way of non-limiting example, distribution of distributed control system (DCS) data in real-time to transactional software, e.g., executing within or between enterprises. It can also include, by way of further non-limiting example, communication of information necessary for supply chain automation between a plan and its customers.
Other aspects of the invention are evident in the claims, as well as in the text and drawings that follow.
A more complete understanding of the invention may be attained by reference to the drawings, in which
FIGS. 4 and 4-1 through 4-30 depicts an object oriented class structure used in implementing a system according to one practice of the invention;
FIGS. 9 and 9-1 through 9-21 depict an object oriented class structure supporting inter alia PD1s and collection plans in a system according one practice of the invention;
Engine 18 and applications 12-16 may execute on a single digital data processing device or multiple digital data processing devices, which may be disposed locally or remotely with respect to one another and which may communicate via network or otherwise in the conventional manner known in the art. Each digital data processing device may constitute a conventional workstation, personal computer, mainframe computer, controller, microprocessor, embedded processor, “smart” field device or any other hardware/software platform suitable for module and/or application execution in accord with the teachings hereof. On any given such digital data processing device, the respective engine 18 and/or applications 12-16 may execute within a single process though, more typically, they execute in different respective processes.
Illustrated applications 12-14, referred to as “Appln 0” and “Appln 1,” respectively, have runtime components 12a,14a that operate in accord with information contained in respective databases 12b, 14b, proprietary or otherwise, that may be independent or shared between those and other applications in the conventional manner known in the art (as further adapted in accord with the teachings below). Each application 12, 14 also includes an editor (or configurator) that is used in the conventional manner, e.g., to set up and modify the respective database for such functions as are desired by the plant operator or other personnel. Each additional application 16 can similarly include a runtime component, database and editor.
Those skilled in the art will, of course, appreciate that, per convention in the art, application 12-16 may include fewer components or more components than those shown in the drawing and described herein. Thus, for example, some application used in systems according to the invention may include only a runtime component and others may include multiple runtime components, databases and/or editors, as well as other components.
Illustrated production engine 18 includes a runtime component 18a—referred to below both as the “event manager” or “production engine”—that coordinates operation of, data collection for, and/or reporting for applications 12-16. This is governed by workflow(s) and parameters defined in a configuration database 18b—though, in alternate embodiments these may be hardcoded, e.g., in the runtime component (18a) and/or defined elsewhere. An editor (or configurator) 18c, which includes the Workflow Editor described below, provides a user interface and/or otherwise facilitates set up and modification the database 18b and, more generally, the production engine 18.
The aforementioned operational coordination, data collection and/or reporting may be effected via coupling between the component 18a (the event manager) and the applications' respective runtime components 12a-14a, e.g., utilizing application program interfaces (APIs) or other interprocess communications techniques, as discussed below. Though all of these coupling mechanisms are indicated in the drawing by lines connecting component 18a with the runtime modules 12a-14a and databases 12b-14b, those skilled in the art will appreciate that fewer or additional mechanisms may be employed as well consistent with the teachings below.
In the illustrated embodiment, further coupling between the production engine 18 and the applications 12-16 is provided via their respective database components 12b, 14b and 18b. To this end, system 18 includes a interpreter 18d that transfers data between the configuration database 18b and the application's respective databases 12b-14b. Such transfers may be effected at configuration time, at runtime, periodically, continuously, or otherwise, e.g., in accord with the teachings below.
Communications coupling, formatting and/or translation required for each respective database 12b-14b is effected by respective interface adapters shown, here, “hanging off” the interpreter 18d and labeled A0, A1. In practice, the adapters may be part of (e.g., “hang off”) the interpreter 18d and/or the databases 12b-14b themselves (and, more properly, respective database managements systems—which may, for example, form part of the respective runtime or editor components 12a, 12c-14a, 14c).
To facilitate coordinated setup and/or modification of the system 10, databases 12b, 14b, 18b, configuration editor 18c may include adapters that facilitate direct setup or modification of the application databases 12b-14b, or portions thereof, e.g., via an interface consistent with that provided by editor 18c vis-a-vis database 18b, via interfaces consistent with those provided by editors 12c-14c vis-a-vis databases 12b-14b, or otherwise. As above, the adapters are shown here hanging off the editor 18c and labeled A0, A1. In practice, the adapters may be part of the editor 18c and/or the databases 12b-14b themselves.
Applications 12-16 are clients of the production engine 18, e.g., insofar as those applications rely on services or data provided by engine 18 for purposes of setup and/or coordinated runtime operation. The illustrated system includes further clients, here, runtime clients 18e, 18f that provide for notifications (e.g., alarms), workflow or other status reporting, and/or data collection, e.g., via user interfaces with plant operator or other personnel. While runtime clients 18e, 18f can be adapted to interface process or other control equipment, e.g., in the manner of applications 12-16, in the illustrated embodiment, the runtime clients are more typically adapted to provide alarms, notifications and other information to plant personnel and/or to receive information therefrom, e.g., in addition to or in lieu of such information provided to and/or received from such personnel by the applications 12-16. More particularly, in one embodiment, the runtime client provides for security (e.g., password entry and access restriction); data trending; alarm notification; task list entry, editing, history reporting and querying; graphical or other workflow status visualization; and workflow state setting (e.g., offline versus active).
Overview of Operation and Terminology
The production engine 18 provides a framework to configure, capture and manage process and production data based on inputs from (and outputs to) applications 12-16, plant or personnel, and/or process or other control equipment. It also provides for correlating process and production data, e.g., to facilitate analysis of the effectiveness of a facility or process. To this end, the engine 18 comprises, inter alia, an event manager 18a that monitors the equipment or processes, for example, via communications with applications 12-16 and via interfaces (e.g., through runtime clients 18e, 18f) with the plant personnel and/or control equipment directly); executes workflows and evaluates any expressions defined therein; triggers actions; prompts plant personnel with or for information; collects data from the applications, personnel and/or control equipment.
As noted above, operation of the event manager 18a is based on workflows, e.g., represented in database 18b. Workflow types include, by way of non-limiting example material workflows (e.g., manipulating raw materials to produce finished goods), equipment workflows (e.g., based on a manufacturing resource, e.g., machine, line, cell, exceptions, faults and regular maintenance activities, cleaning, calibration, failures) and supply chain and/or information workflows (e.g., moving information between applications or areas in an enterprise). Workflows can be triggered by multiple machines, with parameters captured automatically from that equipment or manually from its operators.
As discussed further below, workflow definitions can include event triggers, e.g., process value changes, device inputs, production status changes, resource status changes, messages from other application, or UI messaging. Workflow definitions in the illustrated embodiment also typically include event actions. These can include transactions (such as start, complete, etc.) in applications 12-16, stored procedures/database actions; set-point downloading; user tasks, such as data collection, downtime reporting, sample registration, production reporting, consumption reporting, maintenance task; operator messaging (referred to below as User Interface or UI messages); and SCADA alarm actions, such as e-mail, pager, or telephone messages; to name a few.
In addition to events and actions, a workflow of the illustrated embodiment can include activities, which are defined by one or more related actions; transitions, which inhibit the execution of a workflow until a condition is met; conditional branches, which allow one branch of activities to executed based on evaluation of an expression; decision branches, result in execution of one branch of activities if the evaluation of an expression is true and another branch if false; loops, which execute a executes a series of activities until a condition is met. Of course, it will be appreciated that workflows may have other components, instead or in addition, consistent with the teachings hereof.
Workflow definitions in the illustrated embodiment utilize process data items or PDIs. These capture, track and move information about the controlled process. PDIs represent an aggregation of functionality, such as a transaction input, I/O point (or “tag”), process historization, alarming and analysis. Types of PDI in the illustrated embodiment include memory variables/local workflow variables, I/O and device input, user input, and database I/O. At runtime, sources of PDI values include tags (or I/O points), information manually entered (e.g., via a runtime client), values derived from other data, information retrieved from application databases 12b-14b, arithmetic and/or logical expressions.
By way of example, plant equipment such as a packer unit signals the production engine indicating that its status has changed to a non-running state. A scheduler operating within the event manager 18a reschedules work otherwise assigned to that unit to other plant equipment, updating a work-in-process module with the new equipment information. Based on the downtime cause reported by the equipment and its' expected duration, the scheduler also reschedules the shop floor to account for the lost resource and releases a new schedule to the floor, e.g., via operator messing in a runtime client 18e, 18f, concurrently updating application databases 12b-14b (and other tables, databases, etc.) that govern operation of the floor equipment. The scheduler also signals the runtime components of necessary applications, e.g., 12a, to reflect transfer of the job and operators to the new equipment.
Concurrently, the scheduler treats the underlying cause of the non-running state as an indicator of a maintenance task, to which it assigns a resource—here, a mechanic. It notifies both the mechanic and the information technology department (and/or other enterprise personnel) of the assignment, e.g., via a runtime client 18f. The scheduler also messages personnel to have the parts prepared and delivered to the downed equipment.
Referring to
The runtime component of the InTrack™ application is depicted in
Of course, those skilled in the art will appreciate that other applications, regardless of whether available from the assignee hereof, can be utilized in addition to or instead of inTrack™, InSQL™, and/or InTouch™. Those applications may be competitive, functional or other equivalents of the type known in the art amenable or adaptable for use in systems operating according to the teachings hereof. By way of example, in place of (or in addition to) the inSQL™ server, another SQL server may by utilized, as may be a database management system, query system or other system capable of querying or otherwise identifying items of interest in a database, table or other data collection.
Also shown in
The runtime components 18b′ and 18b′″ of the configuration database 18b are generated by the interpreter 18d and/or by an compilation/upload component (not shown). This can include compiling into a suitable runtime representation for component 18b″ the graphical (or other) representation of the workflow maintained in configuration database 18b′. It can also include resolving references to tags and other parameters in the configuration representation so that they can be properly accessed at runtime by the production engine.
According to one practice of the invention, workflows in the configuration database 18b′ are maintained in “disabled” or “enabled” states, as determined by the operator, e.g., using a menu or other option in editor 18c. In a preferred practice, the interpreter 18d and/or compilation/upload element upload to the runtime databases 18b′ and 18b′″ only configuration database 19b′ workflows that are in the “enabled” state.
Likewise, according to one practice of the invention, workflows represented in the runtime databases 18b″ and 18b′″ are maintained in “offline”, “active” and “running” states. Workflows in the offline state are not executed or “evaluated” by the event manager 18a, while those in the active state are amenable to such execution. Workflows currently being executed by the event manager are referred to as running.
Generation of the tag database 18b′″ can be accomplished, for example, by creating a indexed, trees or other accessible compilation of tags suitable for access by the production engine 18 during execution of the workflow represented in database 18b″.
Although the illustrated embodiment utilizes separate databases 18b′-18b′″ to maintain the configuration versus runtime representations of workflows, alternate embodiments utilize a single database (or set of databases) for both configuration and runtime.
In some embodiments, the production engine accesses the tag database 18b″ directly. In other embodiments, a tag database server (not shown) serves as an interface between the production engine 18 and the database 18b″. One such server is commercially available from the assignee hereof as part of its inTouch™ software package.
With further reference to
Communications between the elements and components of
In the illustrated embodiment, further communications mechanisms are used as well. Thus, a communications protocol and, more particularly, and applications program interface (API) defined under the inTouch External Database Access (IDEA) software package commercially available from the assignee, is used to support communications with the inTouch application (which as noted above serves, e.g., as the tag database 18b″ server). Any other mechanism, commercially available, proprietary or otherwise, supporting such access and, more generally, providing communications coupling among and between the elements may be used in addition or instead.
Likewise, the protocol (and API) known as SuiteLink™ available in input/output servers commercially available from the assignee is used to support communications between applications available from the assignee (e.g., inTouch, inSQL, and inTrack) and the devices of the control system. Those servers are identified collectively in the drawing as an “IO Server.” Again, any other mechanism, commercially available, proprietary or otherwise, server-based or otherwise, supporting such access and, more generally, providing communications coupling with the control system may be used in addition or instead. These same or other communications mechanisms can also be used to provide communications coupling between the control system and the real time clients 18e, 18f.
Production Engine
Overview
The production engine 18 includes two components, a configuration client and an interpreter, to enable the user to enter data into a single point. The configuration client, which comprises the configuration database 18b and editor 18c, allows the user to configure a process data item (PDI). Each such data item represents a tag and particularly, in the illustrated embodiment, a tag from the InTouch application, e.g., 12. The data item may also represent a tag from the InSQL application if any of the historization attributes are selected. Of course, those skilled in the art will appreciate that the data items may represent tags from other application instead or in addition. Once the tag is configured and saved, the aforementioned interpreter is executed which transfers the appropriate attributes to the InTouch tag database 12b and InSQL database 14b.
The configuration client permits security groups, users and associated passwords to be created. Once the user information is saved, execution of the interpreter transfers the security information to the InTrack application 12.
The configuration client provides a mechanism for defining an object called a collection plan. The basis of the collection plan is a data collection from one of the applications 12 -16, here, the InTrack application 12. When the user saves the collection plan and runs the interpreter, an automation server is used to create the data collection. Machine and location attributes are available on a collection plan and other objects within production engine. If these attributes are specified they are created within the underlying application, here, InTrack, after running the interpreter. The following default items are created in that application from the interpreter: Default machine types PE Machine and PE Line.
In a typical implementation of one of the applications 12-16 (and particularly, for example, the InTrack application 12), a client application is developed for a shop floor operator. The client application varies but characteristically takes input from the user or gathers information from a control system. These values are used in calls to the automation server or any automation server of another application. The production engine utilizes a set of predetermined actions that encapsulate some of the common transactions. The user operates the configuration client (e.g., database 18b and editor 18c) to create instances of these actions to map control system values via PDIs to the action's parameters. Execution of the actions as part of a workflow replaces the capability provided by the custom scripting or custom applications.
A client of the production engine provides on-demand graphical reports and basic input mechanisms. The client can contain a screen to allow user input into collection plans. Collection plans can be executed on demand or appear to the user by request of engine. A series of reports are also available via buttons on the screen.
Extended Actions
To understand how automation of manufacturing processes involving the interaction of people, equipment, applications, time and external hardware events is facilitated by the production engine 18, it will be appreciated that actions used in the production engine can literally be calls to a limitless range of software. Tasks required of the applications 12-16 are wrapped in COM wrappers, which conforms to a defined interface. The simple COM wrapper conforming to a pre-defined interface enables the configuration client to detect the wrapper's presence on the machine. Once detected the user can create instances of that action for execution in a workflow. The fact that the user can map the new action's parameters to workflow context variables or control system I/O points (PDIs) facilitates interaction of production engine actions and applications 12-16.
For example, to execute actions of a new application, the programmer can wrap that application's APIs in a component with the extended action interface. Once selected from the configuration client and configured, interpreted, and also installed on the application server, it is available for execution by the engine and thus can utilize information from previous actions via parameters the same way internal production engine actions use the variables.
This ability to add programmatic interaction between any application 12-16 (or external software or hardware) relies on use of one of two interface methods:
The workflow editor 18c′ allows greater control of task definition and interaction. If operator input is required for an action, a prompt message can be added into the workflow and automatically sent to the designated operator to retrieve the input. Once the operator enters the input it is returned to the engine. That information is available for use in subsequent actions of the same workflow via workflow context variables.
Instances of actions created in the production engine's configuration client, which use PDIs as parameters, implement the interaction with the control system. Through the use of workflow variables described previously, it allows the activities of the equipment to be intertwined with the activities of the user.
The production engine 18 provides a user interface that allows the operator to select a particular instance of a workflow and visually see the action currently being performed. It also gives information about the status of the workflow. The operator has the option to do such things as:
A further understanding of the relationship between control applications 12-16 and workflow extended actions may be attained by reference to the following discussion of the automated generation of an extended action for e-mailing. Sample code is provided within comments in each of the methods shown.
In the discussion that follows, “activity” refers to an atomic unit of work. An activity is the smallest unit of work in a workflow that can exist either alone or in combination. For our purposes the combination of activities creates a workflow. This single unit of work is referred to elsewhere herein as an “action”. “Extended Action” refers to a component, conforming to an aforementioned COM interface containing one or more activities. These activities are displayed in the Workflow Editor for use in a workflow.
After an interface is named and specific actions associated with it are identified, a class is created. The newly created class can be opened in an applications development tool (here, Visual Studio C++) and the interface (here, IExtendedAction) expanded, as presented, by way of non-limiting example, in
The sample code shows parameters being created for sending an Email:
Each of the parameters (input and output) can be decoded from the converted XML string:
A new extended action component created in this way can be registered with the digital data processor that executes the production engine 18 and can be used in the workflow editor 18c′ as described above and elsewhere herein.
Production Engine System Structure
The illustrated system 10 and, particularly, for example, the production engine 18, can be implemented in three nodes: database server, application server and client node. The configuration client (e.g., database 18b and editor 18c) may be installed on anyone of these nodes. The database server and application server can physically reside on the same server, though, this may present resource contention issues. In the illustrated embodiment, each node utilizes Microsoft Message Queue (MSMQ) to communicate events and responses.
The following is a list of components used in the illustrated embodiment on each node and a brief description of their function:
Database Server
Configuration database 18b′ for configuration data
Production Support database 18b″ for runtime data
Application Server
Runtime Client Node
The control monitors for a message from event manager 18a indicating that a new message is on a runtime client common queue that it is interested in seeing.
Configuration Client Node
In the illustrated embodiment, messages sent are sent to and from the production engine 18 and, more particularly, the event manager 18a via the Microsoft Message Queue, though other messaging systems may be used in addition or instead. The message fields may change content according to the intended message queue. The current message structure for communication trigger messages is as follows, though other message structures can be used instead or in addition.
Label—Trigger Name
AppSpecific—Message Type as described below:
Body—Workflow Context Variables—These variables are stored as an XML message of name value pairs.
The parts of the message described above (Label, AppSpecific, Body) are the actual names of the parts of Microsoft's Message object.
Message to the runtime clients having the following format:
AppSpecific—Message Type as described below:
Label—A bitwise representation of workstations. Bit position 1 indicates that workstation #1 can receive the queue message, Bit position 2 incidates that #2 can receive the queue message. This mechanism allows a single message to be sent to a workstation group and have only one workstation actually respond to the message.
Body—Workflow Context Variables—These variables are stored as an XML message of name value pairs.
IMS Message Toolkit
The XML messages used in production engine 18 and, more particularly, the event manager 18a of the illustrated embodiment all have a common piece—a name and value. A series of class structures is available for use by other C++ components. This class structure not only exposes the methods required to traverse and extract the pieces of information but also the ability to persist them to a database for backup.
IMS Trigger Toolkit
Applications 12-16 transmit trigger and context information to the production engine and, more particularly, the event manager 18a via a workflow activation message component. In the illustrated embodiment, this activation component has a single method as defined below:
Database Servers
In the illustrated embodiment, the configuration database 18b′0 contains all data required for the workflow editor, interpreter, configuration client, production engine. Likewise, the production support database 18b″ contains all data required for the production engine and runtime clients. Additional tables added to this schema include:
In the illustrated embodiment, this is an extended stored procedure dll containing calls to the Microsoft Message Queue api to place a message onto the private em_schedule_q message queue. The dll accepts a trigger name from a stored procedure. The trigger name is placed in the label of the message.
Interaction with Other Components
Event Manager 18a: The event manager service reads trigger information from the production support database 18b″. Triggers have the option to be scheduled. When a trigger is scheduled for a particular time or time interval, event manager uses the SQL demonstration application to create jobs in SQL Server. Each job is created to call the extended stored procedure with the appropriate trigger name. Event manager uses SQL Server's scheduler event mechanism to fire these trigger events.
An Event manager thread constantly monitors the em_schedule_q for trigger messages from the database server.
Application Server Detail
Security Manager Service
In the illustrated embodiment, the Security Manager is a Windows DCOM server service used for security checks of Production Engine clients. The users and their access rights are defined in the Configuration Client database 18b.
There are two different interfaces for the Security Manager. The ISecurityConfig interface is for accessing configuration data and the ISecurityRuntime interface is for accessing runtime or production data. The Logon method is used to validate and provide access to the user in the respective mode (config or runtime or both). A zero result from the logon method means that there was an error, otherwise a handle is returned that is used to grant/deny access. The RequestAccess method is called with the returned handle and the requested access (ConfigRead=1, ConfigReadWrite=2, ManualDataCollection=4, ManualDataSupercede=8, Production Actions=16). The return value of the RequestAccess function is True for access granted and False for access denied. To log off the user, the Logoff method is called.
The clients of the security manager service are the runtime clients 18e, 18f and configuration client (e.g., database 18b and editor 18c).
Event Manager Structure
In the illustrated embodiment, the event manager 18a functionality is separated into eight different categories: startup, shutdown, abstraction client call-back, scheduled event monitoring, action event monitoring, administration event monitoring, client response monitoring, and expression evaluation monitoring.
Startup
During the startup, event manager performs several operations.
Shutdown
An event object is created to request the four spawned threads to shutdown. Once shutdown is complete all allocated memory is deallocated.
Abstraction Client Callback
A callback method is used to receive data change and alarm events from InTouch. This call back routine first examines additional conditions (possibly expressions) to determine whether the trigger should be inhibited. If there are no additional conditions or the conditions return true then a message is placed on the em_internal_q for detection by the action event monitoring thread.
Schedule Event Monitoring
A thread is spawned in event manager to watch the schedule event queue. When a message comes in it is immediately sent to the em_internal_q (action event monitoring). This thread was created for later expansion to allow conditions to be considered before accepting the timed event.
Action Event Monitoring
A thread is spawned in event manager to respond to incoming triggers. A trigger arrives either by a data change or alarm event from InTouch or from a scheduled event. Once the thread detects a message on the em_internal_q it is examined to determine what workflow should be executed. The workflow execution is completed by calling the execute method on an actionTrigger object. The object resides in a standard template library (STL) name-value pair (name—trigger name, value—action Trigger object). Currently the actionTrigger.Execute method traverses an STL vector, containing action object instances, calling each action's execute method. Each action object is derived from a base action class allowing this traversal to occur seamlessly. The following actions are provided: stored procedures, expressions, production actions and collection plans.
Stored Procedures
Stored Procedure actions use ActiveX data objects (ADO) to pass parameters to a stored procedure for execution. If a stored procedure contains output parameters these parameters are written back out to the PDI values. This in turn writes them back to the I/O source using the abstraction client, if the PDI is not a workflow context variable.
Expressions
Expression actions use purchased source code for evaluating complex expressions. Parameters are passed to the GEO dll for evaluation. The result of the expression is written back to the PDI. Again this is written to the I/O source using the abstraction client if the PDI is not a workflow context variable.
Productions Actions
Production actions are a series of transactions, here, transactions defined in the InTrack application 12a. Each action performs the operations necessary to setup the InTrack objects in order to execute the InTrack transactions of (create, start, consume, complete, close, move, and adjust). Parameters from the I/O source or workflow context variables are used to provide the necessary information to the transaction. In cases where data is returned from the transaction the I/O source or workflow context variable is stored.
Collection Plans
In the illustrated embodiment, Collection Plan actions represent an InTrack data collection action. Additional functionality on top of InTrack resides in the ability to assign an expression to a collection plan item. This is accomplished using the GEO application. The expression is evaluated (including the specified item parameters as input). The result is stored as the collection plan item specifying the expression. Another feature in the collection plans is “stored procedures in collection plans”. This feature allows the user to insert one or more stored procedure calls into the collection plans. These stored procedures are executed using ADO. Each collection plan item, specified for use in the stored procedure, are loaded as parameters into the ADO object and the appropriate stored procedure is executed. All collection plan items are written to InTrack via the automation server once all items are evaluated.
Collection Plans can be automatic, partially automatic, or manual. Fully automatic collection plans are evaluated by the action execution thread and stored to InTrack. Partially automatic or manual collection plans are transmitted to the runtime client for further evaluation. These messages are placed in a message and sent via the common runtime client queue. Collection plan actions
Message Action
In the illustrated embodiment, all UI message actions are transmitted to the runtime client via the common runtime client queue. When a message is sent to the queue, the action thread stalls waiting for the response. Once the client response is received, the parameters of the response are written to the workflow context variables for use by other actions. A pool of threads are created which allow each workflow to execute in it's own thread.
Administration Event Monitoring
Administrative events such as responses from the runtime client are monitored through separate thread. Collection plan messages have time out conditions which require the operator to respond in a given amount of time. The types of responses from the runtime client are indications that a
Client Response Monitoring
Client responses are monitored within the action event monitoring. When a message is sent to the runtime client the thread will stall and wait for a client response on the client response queue.
Configuration Client Node Detail
Workflow Editor
The workflow editor 18c′ displays and builds workflows graphically, thereby permitting user-defined workflows. An exemplary editor display, including a sample workflow graphic, is presented in
Workflow Components Pane 2110 presents a tree view of the various component categories that are used to build a workflow document. The category “Workflow Instances” contains the item New Workflow, as well as any other previously saved workflow instances. The New Workflow item can be dragged and dropped onto the editor pane 2100 to create the Start and Stop nodes for each workflow document. The category “Triggers” lists all available Triggers that have been configured for use in a workflow. The category “Actions” lists available Actions that have been configured for use in a workflow. In the illustration, The Actions category includes the following sub-categories: Collection Plans, Expressions, Production Events, and Stored Procedures.
The Graphical Editor Pane 2100 displays a current workflow document that is being edited or blank if it is a new document. In the illustrated embodiment, this can contain any of the following workflow nodes: Start node, which is created when a New Workflow is dragged and dropped onto the editor pane. In the illustrated embodiment, only Trigger nodes can be dropped on the Start node, though other embodiments may vary.
As evident, then, the workflow can further include a Trigger node, which is created when a Trigger node is dragged and dropped on the Start node. In the illustrated embodiment, only the one Trigger node can be added to a workflow, though other embodiments may vary. In the illustrated embodiment, if a workflow contains a Trigger node and another is dropped onto the Start node, the editor prompts the user if it should replace the existing Trigger node.
A workflow in the illustrated embodiment can further include an Action node, which is created when an Action node is dragged and dropped on the Trigger or any other Action node.
Finally, in the illustrated embodiment, a workflow can include a Stop node, which is also created when a New Workflow is dragged and dropped onto the editor pane. Like the Start node, in the illustrated embodiment, the Stop node cannot be deleted and, like the Start node, only Trigger nodes can be dropped on this node.
In order to create (or editor) a workflow, the user drags triggers onto an empty workflow which, in the first instance, is denoted by “start” and “end” graphics, 2112, 2114, respectively. In the illustrated embodiment, once that trigger is associated to a workflow it cannot be used in another workflow; other embodiments may vary in this regard. Actions, too, are dragged onto the workflow and appended into the workflow 2102 graphic. Action ordering is decided by the order in which these graphics they follow the start node. This ordering is written to the configuration database tables. After interpretation, Event Manager 18a uses the production support database 18b″ to determine actual execution order of the workflow.
Though a linear workflow is shown in the drawing, as indicated by the linear arrangement of nodes and the line segments connecting them, the illustrated workflow editor allows for creation and display of decisions, transitions, conditional branches (multi-branch—3 or more choices), parallel workflows and subworkflows. Such workflows is can be represented in flowchart-like or graphical programming-like iconography. Thus, for example, decisions can be represented diamond- (or other-) shaped nodes that connect to different respective action nodes. Conditional branches can be likewise represented. Parallel workflows can be represented, for example, by two or more linear segments (each, for example, including a respective set of one or more action nodes) disposed side-by-side or otherwise. Preferably, modeling of decisions is limited to a controlled mechanism to form workflows. The editor also supports conditional branches, where the expressions are more complex and result in multiple results such as you would see in a programming case statement.
In the illustrated embodiment, underlying the workflow workspace is a hidden grid. This forces alignment of actions into grid locations to allow for a uniformed look to the workflow. The user is allowed to drop an action next to a decision to allow for connection from the main branch of the workflow. The user can connect decision actions to other actions and can supply the expected results of the decision action. The results for each branch of the decision determine the direction of the flow. The workflow editor stores the ordering of the action information along with a series of choices of next actions. In the case of actions, which are not decisions, there is only one possible next action. In the case of decision actions, there are two choices based on a result. Expression functionality executes these decisions.
Drawing and manipulation of graphical objects in the illustrated embodiment is implemented using the commercially available GO++ add-on to the Microsoft Foundation Classes (MFC), though other graphical object manipulation tools, whether or not based on MFC, may be used in addition or instead. The editor of the illustrated embodiment also uses a COM-based data access object mechanism referred to as OLEDB calls to read configuration data from the configuration database 18b′, though other methods of database connectivity or access can be used. Following completion of a graphical model, the user can save that information back to the configuration database. Once the interpreter 18d is run the data is transferred to the production support database 18b′, where it is read at event manager restart to recognize the new workflows.
With further attention to details of implementation of the illustrated embodiment, the MFC Document/View Architecture is used for both the workflow components pane and the graphical editor views, as discussed below.
Workflow Components Pane
CTreeView that is used to hold information about each node the Workflow Editor supports. Each tree item has a class associated with it (Workflow, Trigger, and Action). For each of these classes a collection (C++ vector) has been defined to contain them. A WFComponents class is been defined that includes each one of these collections (Workflow, Trigger, and Action) as member variables.
Referring to
The WFComponents data members include: Workflow, which uses a combination of tables (Workflow, WorkflowActivity, Activity, ActivityAction, Actions, TriggerActions, and TriggerObject); Trigger, which uses the TriggerObject table; and Action, which uses the Action table. The WFComponents class also includes methods that support the following (vectors refer to Workflow, Trigger, and Action collections):
Clear( )—clears all vectors
Load( )—loads all vectors with the appropriate data from the MS SQL Server database.
Reload( )—issues a Clear( ) and Load( ), described above.
SaveWorkflows( )—support for saving vector data to the MS SQL Server database.
Graphical Editor Pane
CWFEditorView derived from CGoGridView is used to support all of the graphical operations the Workflow Editor uses. The nodes that are currently supported are: WFNode, which is derived from CGoArea (GO++). Used as the base class for all Workflow Editor nodes; WFStartNode which is derived from WFNode; WFTriggerNode which is derived from WFNode; WFActionnode which is derived from WFNode; and WFStopNode which is derived from WFNode
CWFEditorDoc is derived from CGoDocument and is used to support all necessary document functionality that is used for the Workflow Editor. Workflows are stored in a MS SQL Server v7.0 database.
Workflow Context
Workflow Context permits a set of associated events to work on a set of data that is particular to them, much like a program uses a local variable set inside a function. Using this metaphor, a workflow is like a function and the set of actions within that workflow is like the instructions within the function. Actions are permitted to operate upon the Workflow Context much like the instructions of the function operate upon the function's local variable set.
In the illustrated embodiment, every workflow maintains a Workflow Context. This context is an association of variable name with variable type/value. The Workflow Context can be initialized upon instantiation of the workflow through a Workflow Activation Message. The Workflow Activation Message contains a Workflow Context which is a proper subset of the instance of the workflow. Upon instantiation of the workflow, the Workflow Context from the Workflow Activation Message is assumed by the workflow's Workflow Context. As the workflow executes, actions within the workflow operate upon the Workflow Context by getting and/or setting the values associated with the name of the entry in the Workflow Context with which they are interested. Actions are able to increase the workflow's context by setting values that are not currently part of the Workflow Context. These entries are then available to the action from that point on as well as being accessible to subsequent actions in the workflow.
The entries within a Workflow Context are manipulated, in the illustrated embodiment, by the same subsystem that manipulates tags associated with physical I/O. This subsystem determines the type of item upon which information is requested. If it is a tag, the subsystem interfaces with the I/O subsystem. If it is part of a Workflow Context, the subsystem either gets or sets the value within the Workflow Context, as requested.
WorkFlows Context Variables
In the illustrated embodiment, workflow variables are implemented as parameters to an event-generated trigger. The trigger is signaled via a message (with its label set to the trigger name) on Event Manager's internal queue. See
In response to the message, the Event Manager searches for an action-trigger object (loaded by EM on startup) by the name specified in the message label. See step 2504. Once found, EM calls this action-trigger's execute method. See step 2506. The workflow context XML string is passed to this method. The action-trigger's Execute method creates a C++ standard template library (STL) map filled with the associations from the XML string passed as an argument. See step 2508. This map now has the name/value pairs collection, or workflow context, in the form of a string for the name and a CComVariant as the value for each pair.
The action-trigger, next, loops over all the actions that were bound to it, passing the workflow context map to each one. See step 2510. Each action implements an Execute method which takes a reference to this workflow context map. As described in the section that follow, all workflow variables of the illustrated embodiment are implemented in the configuration system as PDIs. These special PDIs have a prefix of wf_. As the actions execute, the CPDIRead and CPDIWrite objects are called to get or set the values of PDIs. These objects are instantiated within the action they are needed and passed a pointer to the workflow context map, which was also passed into the action. When the CPDIRead or CPDIWrite objects are asked to provide the value of a workflow variable, instead of going to the tag system, the workflow context map is accessed or modified.
As the actions are executed, the workflow context map is accessed and modified. See step 2512. The modifications are carried from action to action. In this way, subsequent actions have access to values in the workflow context map set by some previous action. Actions are configured to access either workflow context variables or PDIs. To the action, there is no difference: the CPDIRead and CPDIWrite objects handle the details. Expression evaluation actions are configured to set the value of a PDI based on the value(s) of workflow context variable(s). These actions may be configured with a mix of workflow variables and non-workflow PDIs, on the right side of the expression and either type on the left.
WorkFlows Variables
In the illustrated embodiment, workflow variables are implemented as parameters of a trigger and can be accessed via the Workflow Variables tab of the corresponding trigger object in the configuration editor 18c; see, for example,
Variables are initially written to the database and stored in a temporary state until either a save is called or they are deleted (or the application is closed). This allows for restoration of a template that was changed but not saved with the trigger. The following flags are used for this function:
In the illustrated embodiment, all workflow variables are created with a prefix of “wf_” and appear in all drop-down PDI selectors upon creation. After a workflow variable is created and associated with a trigger, it can be used by a different trigger but it's data type cannot be changed due to database referential integrity.
Association of WorkFlows and Order/LOT IDs
A work scheduler 2320 associates orders numbers from the external system 2310 with lot IDs maintained by the aforementioned InTrack application. In a particular example shown in the drawing, Order 1239 from the external system 2310 is shown associated with Lot ID “Purple Widget”, Workflow “Widget Workflow”, Machine Group “Group 1”, Quantity “100” and Lines/Train “Line 1”. Further associations, not shown in the illustration, are provided for Orders 1234-1237 and 1240-1242. The work scheduler 2320 can be an editor, e.g., with a graphical interface of the type shown in the drawing, or otherwise. It can also be a batch system, a script, a macro, a program or otherwise that generates the indicated associations.
Regardless, a function is provided for scheduling the indicated order, here, Order 1239, through selection of the illustrated “Schedule this Work” button. Orders can, of course, be scheduled in other ways, depending on the type of work scheduler 2320 and the user interface, if any, provided thereby. When that function is exercised, the specific association is stored in a table (not shown) in the production database 18b″.
Within at least selected real-time clients 18e, 18f, an ActiveX control reads “work” information directly from the aforementioned table for display to the operator via the corresponding workstation. A display of the type generated by that control is indicated by element 2330 in the drawing. Here, that display shows that, as of 10:58 AM, on Mar. 5, 2002, work available for the applicable real-time clients workstation includes “Use Lot 992 to Create 100 Widgets.” Other work available for that workstation includes use of Lot 123 to create 9 red widgets, processing of Bin 5 of blue widgets, and use of Lot 342 to create 25 widgets. In alternate embodiments, interface mechanisms other than (or in addition to) ActiveX controls are used to display information from the aforementioned table to the operator. In yet still other embodiments, ActiveX controls or other interface mechanisms are used to convey information from the aforementioned table directly to control equipment (, e.g., other than operator workstations).
Regardless, a function is provided for generating a trigger, e.g., for indicating the start of the scheduled work. Here, that function is exercised by an “Start this Work” button provided on the ActiveX control. In other embodiments, the function is exercised otherwise by the user or control equipment. When the trigger is generated, the ActiveX control (or other interface) directly inserts a new trigger record into the trigger queue (see “Internal Trigger Q”,
In the illustrated embodiment, the workflow schedule or 2320 is configured on a custom basis per project. The remaining functionality shown in the drawing is, across all projects and workflow implementations.
Runtime Client Node Detail
ActiveX Controls
The runtime client consists of several activeX controls added into application runtimes 12a, 14a, 16. The runtime client 18e, 18f includes activeX controls, as described below, which facilitate support communications coupling with the production engine and, more particularly, for example event manager 18a and other components of the system 10. Here, as elsewhere in the illustrated embodiment, though implemented in activeX, it will be appreciated that other programming constructs, containers and/or components (whether or not based on Microsoft™ COM (component object model) technology or equivalents thereof, such as OLE, COM+, DCOM, JAVA, OpenDOC, Netscape LiveConnect) can be used in addition or instead.
UI Message Control
AlarmClient Control
This control depends on data from the production support database 18b″ (also referred to as the “ProdSupport” database). It receives alarm arrived events from alarm sub-system. An alarm consumer dll interfaces to an Alarm Monitoring DCOM server. The Alarm monitoring DCOM server polls the alarm subsystem of an application 12-16 (e.g., inTouch application 12a) for alarms.
PDISelector Control
This control combines data from production support database 18b″, the application databases (e.g., InSQL database 14b) and a runtime database.
ActiveClient Control
The control combines data from production support database 18b″ and the runtime database. It depends on the production engine for message queue server information and PDI information from production support database 18b″.
QueueArrived Control
This control polls message queue for incoming messages. It uses product support database to determine queue information.
ParetoChart Control
This control combines data from the production support database 18b″, the runtime database and one or more application databases (e.g., InSQL database 14b). The chart is able to provide information based on the following inputs: PDI information, configured collection plan information.
Trend Control
This control combines data from the production support database 18b″, the runtime database and one or more application databases (e.g., InSQL database 14b). The control has the ability to trend on the following: configured PDIs, configured collection plan information.
SecurityDialog Control
This control interfaces to security manager service of application server to validate configured users.
Data Structures
Production engine 18 and, particularly. event manager 18a, are implemented utilizing objects implemented from classes of a structure of the type shown in FIGS. 4 and 4-1 through 4-30. It will be appreciated that other class structures and data types may be used in addition or instead
Populating Data Collection-User Action List
Action Message Life Cycle
Production and Configuration Databases
In the illustrated embodiment, the tables below are common to the configuration and production databases 18b′ and 18b″.
Action
The Action table identifies Actions in the illustrated system. Actions may be one of several types indicated by the Action Type field.
ActionEMail
This table is describes the E-Mail type of Action. Each E-Mail action has a record in this table. In the illustrated embodiment, it is mapped 1:1 with Action Where ActionType=5
ActionExpression
This table is specifically for Expression type Actions.
ActionSQL
This table identifies a SQL expression to be executed for ActionType=6. This differs from the Expression type of Action in that the result of the SQL Statement is not used to populate a PDI value.
AlarmGroup
This table lists all the Alarm Groups for the illustrated system. This is primarily used by the InTouch Tag Server to group alarms into hierarchical sets. These sets can be used by the clients to filter out alarms that are not of concern to the operator.
AlarmItem
This table identifies single alarms in an AlarmSet. Each record in this table represents a different type of alarm for the alarm set.
ATEvent
In the illustrated embodiment, this table is 1:1 with the TriggerObject table for ATEvent type triggers
ATSchedule
In the illustrated embodiment, this table is 1:1 with TriggerObject for Schedule type Triggers.
ATSecConstraint
This table identifies secondary constraints on triggers using a PDI expression.
ATSecConstraintSQL
This table identifies secondary constraints on triggers that are made with a SQL statement.
CollectionItem
This table identifies individual items to be collected as part of a Collection Template. Each item identifies a “slot” in the collection plan. Multiple collection plans may share the same Collection Template and therefore the same set of Collectionitems.
CollectionPDI
This table lists the specific PDIs that are mapped to Collectionitems for each Collection Plan.
CollectionPlan
In the illustrated embodiment, this table is 1:1 with Action where ActionType=1
ControlItem
This table identifies target and limit sets by PDI, Product Group, and Effective date.
ControlSet
This table groups the target and limit sets given by the Controlltem table into sets for standardization. Every PDI for SPC analysis has a ControlSet. This can be standardized so that several PDI may share the same control set.
DataRetention
This table defines the global data retention parameters for the illustrated system.
EventType
This table enumerates the event types possible with Production Events. The table is pre-populated with the types supported by the illustrated system. In the illustrated embodiment, the supported Event Types are:
PDIGroup
This table defines groups of PDIs. PDIs can be grouped for reports, displays, etc. Groups can be public or private.
PDIObject
This table identifies PDIs of all types. It contains information common to all PDI types.
ProductionItem
This table enumerates the parameters for each Production EventType. This table is pre-populated with the set of parameters for each EventType in the EventType table (see EventType).
ProductionPDI
This table lists the parameters for each real ProductionEvent and the PDI or Expression assignement. In the illustrated embodiment, expressions are a constant value. In alternate embodiments, arithmetic and string expressions are supported. The Expression and PDIObject fields are mutually exclusive. One and only one of these two fields must be NULL.
SPCAlarm
This table identifies the SPC Alarms which have been configured for each PDI (DataSet)
Event Manager
In the illustrated embodiment, a scheduled event message, notification or other indicator (collectively, “scheduled event”) S1 is generated by the SQL server based on a search of the production database 18b″ for scheduled events or other triggering conditions. Other mechanisms may be used to identify schedule events, e.g., non-SQL database searches, timers, scheduled events lists, and so forth. Regardless, the event S1 is queued or otherwise stored for processing on a FIFO or other basis. And, indeed, in some embodiments, selected (or all) events made available for immediate communication to the event manager 18a.
Like the scheduled event S1, a device input i1—that is, inputs from process or other control equipment to which the applications 12-16 are coupled—are generated by the respective applications, here, tag server associated with the inTouch™ application 12a. The device input i1 may be made available for immediate communication to the event manager 18a or, for example, as here, transmitted from the tag server (or other server, database management system or other store, manager and/or monitor of tags or other device input/output events) via illustrated abstraction client that reformats, maps and/or otherwise insures proper formatting, consistency and/or uniqueness among device inputs i1 received, potentially, from a variety of applications 12-16.
Following queuing, if any, event monitoring functionality in the event manager polls, receives or otherwise identifies scheduled event and device inputs. These are designated in the drawing as S2 and i2, respectively. Specifically, a scheduled event thread identifies and obtains generated/queued event S2 and checks them against event constraints, e.g., stored in the production support database 18b″. An I/O event thread likewise identifies and obtains generated/queued device inputs i2 and checks them against constraints in the production support database 18b″. If the events S2 or inputs i2 match the constraints, they are queued in an internal trigger queue for processing. These are designated in the drawing T1, the letter “T” indicating that they are triggers.
The triggers are, in turn, queued in an internal trigger queue for processing. These are taken up on a FIFO or other basis by an action execution thread (“AET”) also executing in the event manager 18a. One such trigger is designated T2 in the drawing. The action execution thread processes the trigger in accord with the workflow, particularly, for example, executing the event action(s) associated with the particular current trigger (here, trigger T2). As noted previously, those actions can include transactions (such as start, complete, etc.) to be executed by the client applications 12-16, stored procedures/database actions, and so forth.
As discussed above in connection with
With continued reference to
The event manager 18a also includes an administrative command evaluation thread that processes commands received, for example, from the operator console. As above, one such command, here, designated A1, generated by the console is queued or otherwise transmitted for processing by the event manager 18a. That request is dequeued or otherwise received by the command evaluation thread, which parses or otherwise interprets it, altering internal system states, generating output, or performing such processing as is desirable or necessasry in view of the command. It will be appreciated that, though not illustrated here, such processing may include generation of messages to the client applications 12-16, e.g., as discussed above in connection with the expression evaluation and action execution threads.
Process Data Items
The configuration manager integrates information generated by operation of system 10 and its constituent components using Process Data Items (PDIs). These can be established to collect information, trigger actions, and activate messages. These are also used to process values that are maintained or managed by the system.
PDIs can be associated with equipment or locations, and also can depend, for example, on materials to determine appropriate SPC targets and limits. The source of PDI values can be an I/O source. For example, basic information coming from the PLC or other I/O source, such as roll count, is used to trigger tags (PDIs). For example, a roll is completed every time 500 units are processed and a test is required after every five rolls. The following tags would be established:
PDI values can also be derived from an expression calculated from other PDIs. In either event, limits and scaling are similar to those for process control tags. Extensions to process data items include collection plans, events and messages. These enable the grouping of process data items so they can be captured as a single event, either automatically, manually, or in combination. FIGS. 9 and 9-1 through 9-21 depict an object-oriented class structure supporting, among other things, PD1s and collection plans in a system according one practice of the invention.
Types of PDIs supported by the illustratred embodiment include date/time, discrete, list, numerical and text, as described above.
List PDIs.
A list PDI is a process data item or tag that stores a position in a hierarchical tree. The tree in the database schema is a circular reference (references itself) so that it can be easier to store in the database. The database structure can be seen in
Jump points, elements 1308 and 1310 of
Note from
The anatomy of a list PDI is illustrated by
The illustrated PDI defines a hierarchical relationship between the term “electrical” and the terms “light,” “motor,” and “switch,” as illustrated. It further defines a hierarchical relationship between the term “motor” and the terms “rotor failure,” “bushing burnout” and “fuse failure.” Such a PDI can be used to reflect a real-world (or other) relationship, for example, between the electrical system of a hypothetical plant or control system and its major consti-tutents, to wit, the light, motor and switch. It can likewise reflect, to continue the example, modes of failure of those constituents—here, rotor failure or bushing burnout of the motor. In practice, a standard PDI may include more nodes than illustrated PDI 1302.
PDI instances can be created ad hoc as illustrated by element 1304. This PDI defines a hierarchical relationship between the term “plant 1” and the terms “catastrophic failure” and “mechanical.” It further defines a hierarchical relationship between the term “mechanical” and terms “belt broke” and “rivet failed.” Such a PDI can be used to reflect a real-world (or other) relationship, for example, between a plant (here, “plant 1”) or control system and its the failure modes (here, “mechanical” and “catastrophic failure”). It can further reflect, to continue the example, the causes of those failures (here, “belt broke” or “rivet failed” as types of mechanical failure). Again, in practice, a standard PDI may include more nodes than illustrated PDI 1302.
PDI instances can also contain or be created (solely or otherwise) from standard PDIs, as illustrated by element 1306. This PDI 1306 combines the hierarchical relationship defined in 1302 and 1304 as indicated in the drawing. For convenient viewing, the relationships taken from standard PDI 1302 are indicated by dashed lines.
The illustrated PDIs 1304, 1306 further include jump points, designated 1308 (with a value “112”) and 1810 (with a value “4938”). These are effectively short-cuts that permit the user to quickly identify an element in a potentially large or complex hierarchical list. For example, the value “112” can be used, e.g., when defining displays based on the list PDI 1304, as a reference (e.g., which can be quickly input by the user or system engineer) to plant 1/mechanical/belt broke node of list PDI 1304. Likewise, the value 4938 can be used as a reference to the plant 1/electrical/motor/rotor failure node of list PDI 1306.
The components and uses of list PDIs may be better understood by reference to the graphical user interface (GUI) screens/panels through which they are maintained in the illustrated embodiment. It will be appreciated that list PDIs in other embodiments may have components other than those shown here, and they may be maintained other than via the illustrated GUI screens. In the illustrated embodiment, three maintenance panels are provided. General (see
Referring to
The General panel includes the following fields:
Referring to
A right-click menu is available on the List Members table. After selecting an element, click the right mouse button to display a list of edit options: Add Element—to add a new element on the next sublevel below the selected element. Edit Element—to edit the details for the selected element. Remove Element—to remove the selected element. Move Up—to move the selected element above the previous element at the same level. Move Down—to move the selected element below the next element at the same level.
The List Definition panel includes the following fields:
Referring to
In the illustrated embodiment, the configuration manager 18g manages process data items (PDIs). The configuration client allows the user to configure them. PDIs are supported through data maintained in the InTrack database 12b, including work-in-progress tracking and resource tracking, and represent tag in the aforementioned InTouch application. If any of the historization attributes are selected, the PDI also represents a tag in the aforementioned InSQL application. Once a tag is configured and saved, the interpreter 18d is executed which transfers the appropriate attributes to the InTouch tag database and InSQL database. The configuration client permits security groups, users and associated passwords to be created. Once the user information is saved, execution of the interpreter will transfer the security information to the aforementioned InTrack application.
Collection Plans
Collection plans are used to collect run-time data. They can be automatic, partially automatic, or manual. In the illustrated embodiment, automatic collection plans are evaluated by the action execution thread (see
To that end, messsages for those plans are sent via the common run-time client queue (see
The runtime clients 18e, 18f allows operators to enter data responsive to those messages for entry into the respective plans. Manual collection plans appear on task lists for assigned workstations associated with the run-time clients 18e, 18f. When opened, entry grids enable operators to enter information for each PDI in the collection plan. This data is stored in the databases. The illustrated embodiment also permits stored procedures to be included in collection plans: as the collection plans are opened and saved, additional activities such as calculations or communication with other resources can be executed.
Collection plans can be based on templates that serve as outlines or basic patterns. For example, if a user wishes to establish six different product quality tests with the same types of measurements, he or she can enter the basic collection items in a template. When individual collection plans are created from the template, the user assigns individual parameters to the measurements as needed. In the illustrated embodiment, collection plan templates are optional: the user can create individual collection plans without them.
In the illustrated embodiment, collection plans are a superset of InTrack data collection, that is, of the data collection maintained by the inTrack application 12a and stored in the associated database 12b. In this regard, the InTrack application 12a provides the mechanism to store and retrieve a time stamped series of user definable records and columns. (Of course, it will be appreciated that other functionality, standard in the art, proprietary, or otherwise, could be used for this purpose in place of the InTrack application). The configuration manager and client permits the user to specify collection plan objects linking InTrack data collection items to PDIs (external data points) and expressions. They also allow the user to define specific items of information to be collected per location or machine. Collection plan actions can also be dropped into workflows.
When the user saves a collection plan and runs the interpreter 18d, the aforementioned automation server creates the data collection, using machine and location attributes available on the collection plan and other objects available within production engine. Specified attributes are created within the InTrack application 12a after running the interpreter 18d.
Once saved and interpreted, the engine executes workflows as they are triggered. When the collection plan action is executed the engine gathers the appropriate external data storing them to collection items, performs the configured calculations using other collection items and stores the values using calls to the data set object of the InTrack automation server.
The expression assignment capability is provided, in the illustrated embodiment, via the GEO application, though, other mechanisms standard in the art, proprietary or otherwise can be used instead or in addition. At runtime, each expression is evaluated, including the specified item parameters as input. The result is stored as the collection plan item specifying the expression.
The illustrated system also provides for “stored procedures in collection plans”. These allows the user to insert one or more stored procedure calls into the collection plans. These stored procedures are executed using ADO. Each collection plan item, specified for use in the stored procedure, are loaded as parameters into the ADO object and the appropriate stored procedure is executed. All collection plan items are written to InTrack via the automation server once all items are evaluated.
Active Client Control
Described below is the ActiveClient control used by runtime clients 18e, 18f according to one practice of the invention to create and edit collection plan records. The control is implemented into the runtime clients to allow users the ability to view queued items, as well as templates for creating new records. The control is also be defined to display archived collection plan records according to a user define query filter.
In the illustrated embodiment, two modes are defined for the user to view and edit collection plan records; “View” and “Edit”. Three panels are defined to display to the user; the tasks available, the records associated to the selected task, and the selected task items for editing. A separate panel is defined to allow the user the ability to filter the returned collection plan records.
View Mode
Referring to
New Collection Plan from a Template
In the illustrated embodiment, entering edit mode through a template item creates a new collection plan record. This template supports automatic and manual items. Manual items require user input. A generic default value is stored initially into the field upon entering edit mode, unless a specific default value had been configured. Automatic items are populated by retrieving values from a tag server. If the tag server is not available, default values are used as with manual items. Automatic items are not editable by the user, unless they were defined as a datetime with the name of “SampleTime”, or as a list item.
Edit Collection Plan Record from a Queue Item
Entering edit mode through a queued task item removes the item from the common message queue folder. This prevents all other configured users from accessing this item. This record is stored in a separate database table until all required items have been supplied by the user, and the task list displays this item as “InWork” with the use of a distinct icon. Upon completion of all required items, the task is removed from the task list, the stored record is removed, and the collection plan record status is updated to the appropriate status indicator.
Edit Collection Plan Record from an Archived Item
After a queued task has been completed, and the item has been removed from the task list, the user can still edit the record by way of the Collection Plan Samples grid (defined below).
Collection Plan Samples
A grid is defined to display all collection plan records according to the user defined query criteria. This is performed when the user configures the QBE, and by selecting a task in the task list. All configured data items within the collection plan record are supplied in the grid, as well as all relevant base InTrack table items: such as Status, SampleTime, SampleID, etc. During edit mode, manual and automatic items have specific characteristics. The following section describes the characteristics.
Automatic Items
Upon entering edit mode, automatic items are populated with the values from the tag server only when the user has selected a collection plan template for creating a new record. Otherwise, the Event Manager supplies the automatic items through a queued collection plan record to the client, or previously by a client creating a new sample through a template. In the illustrated embodiment, after the record has been created and saved, no automatic items are editable, except for the following: collection plan items configured as a Datetime item, and configured with the item name “SampleTime” and any list item.
Manual Items
Upon entering edit mode, any manual item is made available for editing. This is true for new records, queued records, or archive records.
Data Types
In the illustrated embodiment, a collection plan can include the following data types:
Data/Time
In the illustrated embodiment, a datetime PDI (or tag) is defined as an item to represent a date and time value. Datetime items can be configured with a default value representing any valid date and time.
Discrete
In the illustrated embodiment, a discrete PDI (or tag) is defined as an item to represent a “True” or “False” condition. This value can be displayed with a textual value such as “On” or “Off”, as well as any other desired combination. Discrete items can be configured with a default value representing either a “True” of “False” value.
List Items
As evident in the discussion above, a list PDI (or tag) is an item that stores a position in a hierarchical tree. In the illustrated embodiment, the tree in the database schema is a circular reference (references itself) so that it can be easier to store in the database.
Numeric
In the illustrated embodiment, a numeric PDI (or tag) is defined as an item to represent any valid numeric value. Numeric items can be configured with a default value representing any valid numeric value.
Stored Procedure
In the illustrated embodiment, a stored procedure PDI (or tag) is defined as an item to represent any valid stored procedure interface. This item allows the user to supply information to return further information through a stored procedure.
Text
In the illustrated embodiment, a text PDI (or tag) is defined as an item to represent a textual value. Text items can be configured with a default value representing any value.
Collection Plan Execution Implementation
Event Manager
In the illustrated embodiment, the event manager and runtime client (RTC) nodes work together to create collection plan data. Initially, the collection plan initiated. If it is an automatic collection plan then the RTC has no interaction. If it is a manual collection plan then the RTC supplies Event Manager with some or all of the collection plan data. To initiate the collection plan, a trigger is required. The collection plan is either a manual or automatic collection plan as described below.
Automatic Collection Plan
When the trigger is fired, the event manager fills in the data for the collection plan. This is saved using one of the control applications 12-16 and, specifically, in the illustrated embodiment, the data collection method of the aforementioned InTrack application (though, it will be appreciated, that data collection methods of other control applications, industry standard, proprietary or otherwise, may be used in addition or instead).
Manual Collection Plan
First, the event manager fills what data it can in the collection plan with the automatically collected items and then calls the InTrack (or, as indicated in the prior paragraph, other application) data collect method. In the illustrated embodiment, a message is sent to the Microsoft Message Queue server with the data in a ADO recordset. This message is directed to one or more real time clients (RTC). The RTC(s) read(s) this message and the user fills in some or all of the data for the collection plan. This data is then sent back to Event Manager via another message. Event Manager calls as method from the DSSManager which updates the previous InTrack data collection data using InTrack's data collection supercede.
Collection Plan Stored Procedures
Stored procedures are fully operable for both collection plans and actions in the illustrated system. Entry options in the configuration client to enable fast entry of connection information and stored procedure parameters and commands.
Stored procedures are activated series of commands that are triggered when a collection plan or action is conducted in Runtime. Trigger conditions determine if and when the stored procedure is activated. Stored procedures can be used to:
Configuration Entry Screens
Entry screens and display windows accommodate entry of stored procedure connection and command information. List windows enable selection and display of existing stored procedures. As stored procedure information is entered, default input and output item names are assigned automatically, selection options enable the configuration of items, and SQL script validation is performed. Entry screens have been standardized, enabling fast reference and selection of stored procedures activated by any combination of multiple collection plans and actions.
Collection Plan Template Maintenance Screen
In the illustrated embodiment, after a new collection plan template is selected for editing, a collection plan template maintenance screen appears. See,
Config & Prodsupport Common Tables
The following tables are common to both the Configuration and Production Support databases in support of Collection Plans in the illustrated embodiment.
Action
In the illustrated embodiment, the Action table identifies Actions in the illustrated system. Actions may be one of several types indicated by the ActionType field.
CollectionItem
In the illustrated embodiment, this table identifies individual items to be collected as part of a Collection Template. Each item identifies a “slot” in the collection plan. Multiple collection plans may share the same Collection Template and therefore the same set of CollectionItems.
CollectionPDI
In the illustrated embodiment, this table lists the specific PDIs that are mapped to Collectionitems for each Collection Plan.
CollectionPlan
In the illustrated embodiment, this table is 1:1 with Action where ActionType=1
ControlItem
This table identifies target and limit sets by PDI, Product Group, and Effective date.
ControlSet
In the illustrated embodiment, the table groups the target and limit sets given by the Controlltem table into sets for standardization. Every PDI for SPC analysis has a ControlSet. This can be standardized so that several PDI may share the same control set.
UI Messaging
The UI Messaging mechanism of the illustrated embodiment provides for definition of a user interface—i.e., prompts, questions, text/list/combo boxes, and so forth—through which information is presented to, and accepted from, the operator, e.g., via real-time clients 18e, 18f and via applications 12-16 which understand the UI message format. The UI mechanism also provides the ability to associate elements of the presented user interface with variables (e.g., PDIs) in the system 18, as well as the ability to programmatically extract user-entered results from the UI Message for use in other parts of the execution context, e.g., as workflow variables.
Configuration of UI Messages is accomplished using the configuration client, e.g., database 18b and editor 18c. The configuration client of the illustrated embodiment utilizes displays as shown in
Referring to
The configuration client stores data that makes up a UI Message in three tables in the configuration database 18b:
UIMessage
UIMessageTransforms
UIMessageItems
These tables are created via an SQL commands as follows, though it will be appreciated that such tables may be created elsewise and that they may be represented, instead or in addition, by structures other than tables (e.g., hierarchical databases, linked lists, objects or object databases, and so forth). It will also be appreciated that the fields other than those shown in the following SQL commands may be used in the tables instead or in addition.
The data in the respective UIMessage tables is moved into the runtime execution environment when the interpreter 18d is executed. At that point, all UI Message data available in the production support database 18b″, using an identical schema to that shown above.
In the illustrated embodiment, UI Messages are implemented as actions; hence, all activity on them is initiated by the Event Manager. A UI Message “action” may be part of a workflow and/or otherwise associated with a data change event, an alarm event, a scheduled event, or otherwise.
A IUIMessage component is provided by the system to facilitate processing of UI Messages by the AET and by the runtime clients. The IUIMessage component is a DLL which provides the following interface and which has the following functionality.
A corresponding IUIMessageDisplay component is an active template library (ATL) HTML-based control. The UIMessageDisplay is an ActiveX control that leverages the Microsoft WebBrowser control for rendering a UIMessage. UIMessageDisplay applies an XSLT to transform the UIMessage document into an HTML-based visualization. The UIMessageDisplay also handles user input [which includes various forms of data validation] as well as submission of the UIMessage back to the engine. The control supports the following interface:
As evident in the discussion that follows, in the illustrated embodiment, UI messages are converted to/from XML markup language by the IUI Message component for use (e.g., information display and/or retrieval) by the IUIMessageDisplay component. To facilitate dynamic display of the UI messages, the latter specifies their output to the webbrowser component active within the runtime client application in XHTML, though it will be appreciated that HTML or other protocols, proprietary or otherwise, markup language-based or otherwise, may be used as well or in addition. Moreover, IUIMessageDisplay utilizes XSL to govern formatting of those displayed message by the webbrowser component, though, again, it will be appreciated that other format specification techniques, proprietary or otherwise, may be used to specify the formatting of UI messages or the elements thereof. Shown in
Turning back to
In step 3020, the AET sets the routing information for the UIMessage. The illustrated embodiment utilizes MSMQ to route messages to runtime clients, though other embodiments may use other protocols instead or in addition.
In step 3030, the AET routes the UIMessage command message—now, in XML format—to the designated runtime client applications. In the illustrated embodiment, which uses MSMQ, this means creating an MSMQ message of the requisite type and notifying the client application(s) that it is available. In step 3040, waits on the asynchronous response from the runtime client(s).
To receive a UI Message from the MSMQ queue, the runtime client:
UI Message visualization is generated dynamically by using an XSL Stylesheet associated with the UI Message XML document. A default standard XSL stylesheet, depicted in
To use default (or standard) UI Message visualization in edit mode, the runtime client:
Overriding the standard UIMessage Visualization is accomplished on a per-UIMessage basis. The IUIMessage component has a Name property. If the client application has provided a custom visualization for UIMessages that have a specific name, then the client may choose not to use the IUIMessageDisplay control.
Referring back go
A further understanding of the interaction between the UIMessage component, the UIMessage display component and the operator is depicted in
Thin Client UI Messaging
UI Messaging for a “thin” runtime client is accomplished as discussed above, taking into account the modifications below.
At the outset, the runtime client of a “thin” client is an Microsoft ASP.NET application that provides web-based access to UI Messages for web browsers and mobile devices. As above, that application provides a view of the available UI messages for a client, and enables the client to enter values for the message items and submit the results.
Referring to
Startup
Both applications query the production support database 18b″ at startup to determine the common and response queues to use for getting and returning messages. In order for this to work, the IIS machine must be entered as a workstation in the ConfigClient. The WorkstationID for the IIS machine is also retrieved at this time. This data is stored in the Application object.
When a client makes a request for the first time, its WorkstationID is retrieved from the production support database 18b″ as well. If it does not exist in the product support database 18b″, a-1 is stored. This information is stored in the Session object.
UI Message List
When the user requests a list of the available UI Messages (UIMessageList.aspx), the application iterates through the common queue, looking for messages that match the IIS WorkstationID or the client's WorkstationID. If a message matches, it is added to a table. The name of the UI Message is stored as a link to the UI Message editing page (UIMessage.aspx). This link also contains a parameter named ID that identifies the message.
UI Message
When the user selects a message in the list by clicking on its name, the application receives the message from the common queue. This removes the message from the queue, making it unavailable to others. This is done using a transaction. The reason for this is that if the user later cancels the message or never submits it, the transaction can be aborted and the message will be returned to the common queue were another client can pick it up.
Once the message has be received, it's name is used to check for the existence of a custom page. If a custom page is found, control is transferred to that page.
The body of the message is loaded into an XML DOM and then parsed to find the labels, questions, and list PDIs. Appropriate controls are added to the page to allow the user to enter values for these items. If the item is required and/or a numeric field, a validator control is added as well to insure the submitted results are valid. The control IDs are set to match the names of the workflow variables corresponding to each of the message items. This aids in returning the results later.
The XML DOM, message ID, and message transaction are all stored in the session object for later use.
If the user clicks the cancel button, the message transaction is aborted, and the message returns to the common queue.
If the user clicks the submit button, the application parses through the XML DOM finding message items. It uses the workflow variable name assigned to the item to retrieve the value submitted from the form. These values are then set in the XML DOM. Once all of the values have been retrieved and stored in the XML DOM, the message is sent to the response queue and the transaction is committed.
UI Message Notification
A UI Message Notification control was created to provide a way to add an indicator to a web page that informs the user when a message is available. The indicator is a red image when no messages are available for the client, and turns green when a message is available. When the indicator is green, clicking on it will popup a new page that contains the UI Message List.
Disclosed above are methods and apparatus meeting the objectives set forth above, among others. It will, of course, be appreciated that the embodiments disclosed herein are merely examples of the invention and that other embodiments incorporating changes therein fall within the scope of the invention. In view thereof, what we claim is:
This application claims the benefit of filing of U.S. Provisional Patent Application No. 60/372,770, filed Apr. 15, 2002, and entitled METHODS AND APPARATUS FOR WORKFLOW DEFINITION AND PROCESSING, the teachings of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3665172 | Spaargaren et al. | May 1972 | A |
| 3810119 | Zieve et al. | May 1974 | A |
| 3825905 | Allen et al. | Jul 1974 | A |
| 4006464 | Landell | Feb 1977 | A |
| 4096566 | Borie et al. | Jun 1978 | A |
| 4276593 | Hansen | Jun 1981 | A |
| 4302820 | Struger et al. | Nov 1981 | A |
| 4312068 | Goss et al. | Jan 1982 | A |
| 4323966 | Whiteside et al. | Apr 1982 | A |
| 4347563 | Paredes et al. | Aug 1982 | A |
| 4410942 | Milligan et al. | Oct 1983 | A |
| 4413314 | Slater et al. | Nov 1983 | A |
| 4423486 | Berner | Dec 1983 | A |
| 4428044 | Liron | Jan 1984 | A |
| 4435762 | Milligan et al. | Mar 1984 | A |
| 4443861 | Slater | Apr 1984 | A |
| 4456997 | Spitza | Jun 1984 | A |
| 4466098 | Southard | Aug 1984 | A |
| 4471457 | Videki | Sep 1984 | A |
| 4488226 | Wagner, Jr. | Dec 1984 | A |
| 4493027 | Katz et al. | Jan 1985 | A |
| 4570217 | Allen et al. | Feb 1986 | A |
| 4609995 | Haebe | Sep 1986 | A |
| 4615001 | Hudgins, Jr. | Sep 1986 | A |
| 4628437 | Poschmann et al. | Dec 1986 | A |
| 4639852 | Motomiya | Jan 1987 | A |
| 4641269 | Japenga et al. | Feb 1987 | A |
| 4641276 | Dunki-Jacobs | Feb 1987 | A |
| 4648064 | Morley | Mar 1987 | A |
| 4649479 | Advani et al. | Mar 1987 | A |
| 4663704 | Jones et al. | May 1987 | A |
| 4672530 | Schuss | Jun 1987 | A |
| 4675812 | Capowski et al. | Jun 1987 | A |
| 4682158 | Ito et al. | Jul 1987 | A |
| 4682304 | Tierney | Jul 1987 | A |
| 4683530 | Quatse | Jul 1987 | A |
| 4692859 | Ott | Sep 1987 | A |
| 4692918 | Elliott et al. | Sep 1987 | A |
| 4703421 | Abrant et al. | Oct 1987 | A |
| 4704676 | Flanagan et al. | Nov 1987 | A |
| 4709325 | Yajima | Nov 1987 | A |
| 4719593 | Threewitt et al. | Jan 1988 | A |
| 4727477 | Gavril | Feb 1988 | A |
| 4733366 | Deyesso et al. | Mar 1988 | A |
| 4742349 | Miesterfeld et al. | May 1988 | A |
| 4750109 | Kita | Jun 1988 | A |
| 4790762 | Harms et al. | Dec 1988 | A |
| 4805107 | Kieckhafer et al. | Feb 1989 | A |
| 4816996 | Hill et al. | Mar 1989 | A |
| 4817094 | Lebizay et al. | Mar 1989 | A |
| 4872106 | Slater | Oct 1989 | A |
| 4897777 | Janke et al. | Jan 1990 | A |
| RE33162 | Yoshida et al. | Feb 1990 | E |
| 4910658 | Dudash et al. | Mar 1990 | A |
| 4910691 | Skeirik | Mar 1990 | A |
| 4918690 | Markkula, Jr. et al. | Apr 1990 | A |
| 4958277 | Hill et al. | Sep 1990 | A |
| 4959774 | Davis | Sep 1990 | A |
| 4965717 | Cutts, Jr. et al. | Oct 1990 | A |
| 4965742 | Skeirik | Oct 1990 | A |
| 4965880 | Petijean | Oct 1990 | A |
| 4991170 | Kem | Feb 1991 | A |
| 5008805 | Fiebig et al. | Apr 1991 | A |
| 5050165 | Yoshioka et al. | Sep 1991 | A |
| 5068778 | Kosem et al. | Nov 1991 | A |
| 5121318 | Lipner et al. | Jun 1992 | A |
| 5122948 | Zapolin | Jun 1992 | A |
| 5124908 | Broadbent | Jun 1992 | A |
| 5129087 | Will | Jul 1992 | A |
| 5131092 | Sackmann et al. | Jul 1992 | A |
| 5134574 | Beaverstock et al. | Jul 1992 | A |
| 5136704 | Danielsen et al. | Aug 1992 | A |
| 5138708 | Vosbury | Aug 1992 | A |
| 5140677 | Fleming et al. | Aug 1992 | A |
| 5146589 | Peet, Jr. et al. | Sep 1992 | A |
| 5151978 | Bronikowski et al. | Sep 1992 | A |
| 5151981 | Westcott et al. | Sep 1992 | A |
| 5159673 | Sackmann et al. | Oct 1992 | A |
| 5162986 | Graber et al. | Nov 1992 | A |
| 5163055 | Lee et al. | Nov 1992 | A |
| 5164894 | Cunningham-Reid et al. | Nov 1992 | A |
| 5166685 | Campbell, Jr. et al. | Nov 1992 | A |
| 5168276 | Huston et al. | Dec 1992 | A |
| 5168441 | Onarheim et al. | Dec 1992 | A |
| 5175829 | Stumpf et al. | Dec 1992 | A |
| 5193175 | Cutts, Jr. et al. | Mar 1993 | A |
| 5202961 | Mills et al. | Apr 1993 | A |
| 5212784 | Sparks | May 1993 | A |
| 5233615 | Goetz | Aug 1993 | A |
| 5245704 | Weber et al. | Sep 1993 | A |
| 5251125 | Karnowski et al. | Oct 1993 | A |
| 5255367 | Bruckert et al. | Oct 1993 | A |
| 5258999 | Wernimont et al. | Nov 1993 | A |
| 5271013 | Gleeson | Dec 1993 | A |
| 5276901 | Howell | Jan 1994 | A |
| 5283729 | Lloyd | Feb 1994 | A |
| 5289365 | Caldwell et al. | Feb 1994 | A |
| 5295258 | Jewett et al. | Mar 1994 | A |
| 5297143 | Fridrich et al. | Mar 1994 | A |
| 5301320 | McAtee et al. | Apr 1994 | A |
| 5302952 | Campbell, Jr. et al. | Apr 1994 | A |
| 5303227 | Herold et al. | Apr 1994 | A |
| 5303375 | Collins et al. | Apr 1994 | A |
| 5303392 | Carney et al. | Apr 1994 | A |
| 5307346 | Fieldhouse | Apr 1994 | A |
| 5307372 | Sawyer et al. | Apr 1994 | A |
| 5307463 | Hyatt et al. | Apr 1994 | A |
| 5309556 | Sismilich | May 1994 | A |
| 5317726 | Horst | May 1994 | A |
| 5335221 | Snowbarger et al. | Aug 1994 | A |
| 5347181 | Ashby et al. | Sep 1994 | A |
| 5349343 | Oliver | Sep 1994 | A |
| 5352033 | Gresham et al. | Oct 1994 | A |
| 5359721 | Kempf et al. | Oct 1994 | A |
| 5367640 | Hamilton et al. | Nov 1994 | A |
| 5371895 | Bristol | Dec 1994 | A |
| 5377315 | Leggett | Dec 1994 | A |
| 5381529 | Matsushima | Jan 1995 | A |
| 5384910 | Torres | Jan 1995 | A |
| 5390321 | Proesel | Feb 1995 | A |
| 5392389 | Fleming | Feb 1995 | A |
| 5394522 | Sanchez-Frank et al. | Feb 1995 | A |
| 5398331 | Huang et al. | Mar 1995 | A |
| 5398336 | Tantry et al. | Mar 1995 | A |
| 5400140 | Johnston | Mar 1995 | A |
| 5408603 | Van de Lavoir et al. | Apr 1995 | A |
| 5410717 | Floro | Apr 1995 | A |
| 5420977 | Sztipanovits et al. | May 1995 | A |
| 5426732 | Boies et al. | Jun 1995 | A |
| 5428734 | Haynes et al. | Jun 1995 | A |
| 5428781 | Duault et al. | Jun 1995 | A |
| 5432711 | Jackson et al. | Jul 1995 | A |
| 5434997 | Laundry et al. | Jul 1995 | A |
| 5437007 | Bailey et al. | Jul 1995 | A |
| 5442639 | Crowder et al. | Aug 1995 | A |
| 5444851 | Woest | Aug 1995 | A |
| 5450403 | Ichii et al. | Sep 1995 | A |
| 5450425 | Gunn et al. | Sep 1995 | A |
| 5450764 | Johnston | Sep 1995 | A |
| 5451939 | Price | Sep 1995 | A |
| 5452201 | Pieronek et al. | Sep 1995 | A |
| 5457797 | Butterworth et al. | Oct 1995 | A |
| 5459825 | Anderson et al. | Oct 1995 | A |
| 5459839 | Swarts et al. | Oct 1995 | A |
| 5461710 | Bloomfield et al. | Oct 1995 | A |
| 5463735 | Pascucci et al. | Oct 1995 | A |
| 5467264 | Rauch et al. | Nov 1995 | A |
| 5475856 | Kogge | Dec 1995 | A |
| 5481741 | McKaskle et al. | Jan 1996 | A |
| 5483660 | Yishay et al. | Jan 1996 | A |
| 5485620 | Sadre et al. | Jan 1996 | A |
| 5490276 | Doli, Jr. et al. | Feb 1996 | A |
| 5491791 | Glowny et al. | Feb 1996 | A |
| 5493534 | Mok | Feb 1996 | A |
| 5500934 | Austin et al. | Mar 1996 | A |
| 5504672 | Hardiman et al. | Apr 1996 | A |
| 5504902 | McGrath et al. | Apr 1996 | A |
| 5509811 | Homic | Apr 1996 | A |
| 5513095 | Pajonk | Apr 1996 | A |
| 5513192 | Janku et al. | Apr 1996 | A |
| 5513354 | Dwork et al. | Apr 1996 | A |
| 5517655 | Collins et al. | May 1996 | A |
| 5519605 | Cawlfield | May 1996 | A |
| 5519701 | Colmant et al. | May 1996 | A |
| 5522044 | Pascucci et al. | May 1996 | A |
| 5530643 | Hodorowski | Jun 1996 | A |
| 5537548 | Fin et al. | Jul 1996 | A |
| 5539909 | Tanaka et al. | Jul 1996 | A |
| 5544008 | Dimmick et al. | Aug 1996 | A |
| 5549137 | Lenz et al. | Aug 1996 | A |
| 5550980 | Pascucci et al. | Aug 1996 | A |
| 5551047 | Mori et al. | Aug 1996 | A |
| 5555213 | DeLong | Sep 1996 | A |
| 5555437 | Packer | Sep 1996 | A |
| 5555510 | Verseput et al. | Sep 1996 | A |
| 5559691 | Monta et al. | Sep 1996 | A |
| 5559963 | Gregg et al. | Sep 1996 | A |
| 5566320 | Hubert | Oct 1996 | A |
| 5568378 | Wojsznis | Oct 1996 | A |
| 5572673 | Shurts | Nov 1996 | A |
| 5576946 | Bender et al. | Nov 1996 | A |
| 5579220 | Barthel et al. | Nov 1996 | A |
| 5579487 | Meyerson et al. | Nov 1996 | A |
| 5581760 | Atkinson et al. | Dec 1996 | A |
| 5586112 | Tabata | Dec 1996 | A |
| 5586329 | Knudsen et al. | Dec 1996 | A |
| 5586330 | Knudsen et al. | Dec 1996 | A |
| 5587899 | Ho et al. | Dec 1996 | A |
| 5594858 | Blevins | Jan 1997 | A |
| 5594899 | Knudsen et al. | Jan 1997 | A |
| 5596331 | Bonaffini et al. | Jan 1997 | A |
| 5596752 | Knudsen et al. | Jan 1997 | A |
| 5598536 | Slaughter, III et al. | Jan 1997 | A |
| 5598566 | Pascucci et al. | Jan 1997 | A |
| 5600845 | Gilson | Feb 1997 | A |
| 5604871 | Pecone | Feb 1997 | A |
| 5611057 | Pecone et al. | Mar 1997 | A |
| 5613148 | Bezviner et al. | Mar 1997 | A |
| 5617540 | Civanlar et al. | Apr 1997 | A |
| 5621871 | Jaremko et al. | Apr 1997 | A |
| 5623592 | Carlson et al. | Apr 1997 | A |
| 5627979 | Chang et al. | May 1997 | A |
| 5629949 | Zook | May 1997 | A |
| 5630056 | Horvath et al. | May 1997 | A |
| 5630152 | DeLuca et al. | May 1997 | A |
| 5642511 | Chow et al. | Jun 1997 | A |
| 5649121 | Budman et al. | Jul 1997 | A |
| 5655092 | Ojala | Aug 1997 | A |
| 5659680 | Cunningham et al. | Aug 1997 | A |
| 5664101 | Picache | Sep 1997 | A |
| 5664168 | Yishay et al. | Sep 1997 | A |
| 5671374 | Postman et al. | Sep 1997 | A |
| 5676141 | Hollub | Oct 1997 | A |
| 5680404 | Gray | Oct 1997 | A |
| 5680409 | Qin et al. | Oct 1997 | A |
| 5682476 | Tapperson et al. | Oct 1997 | A |
| 5687316 | Graziano et al. | Nov 1997 | A |
| 5701414 | Cheng et al. | Dec 1997 | A |
| 5708779 | Graziano et al. | Jan 1998 | A |
| 5719761 | Gatti et al. | Feb 1998 | A |
| 5726912 | Krall, Jr. et al. | Mar 1998 | A |
| 5727128 | Morrison | Mar 1998 | A |
| 5732218 | Bland et al. | Mar 1998 | A |
| 5734837 | Flores et al. | Mar 1998 | A |
| 5737529 | Dolin, Jr. et al. | Apr 1998 | A |
| 5742762 | Scholl et al. | Apr 1998 | A |
| 5748467 | Qin et al. | May 1998 | A |
| 5751574 | Loebig | May 1998 | A |
| 5752007 | Morrison | May 1998 | A |
| 5752008 | Bowling | May 1998 | A |
| 5752246 | Rogers et al. | May 1998 | A |
| 5754772 | Leaf | May 1998 | A |
| 5758073 | Liang et al. | May 1998 | A |
| 5758075 | Graziano et al. | May 1998 | A |
| 5761518 | Boehling et al. | Jun 1998 | A |
| 5764906 | Edelstein et al. | Jun 1998 | A |
| 5768119 | Havekost et al. | Jun 1998 | A |
| 5768510 | Gish | Jun 1998 | A |
| 5774670 | Montulli | Jun 1998 | A |
| 5777874 | Flood et al. | Jul 1998 | A |
| 5790791 | Chong et al. | Aug 1998 | A |
| 5793963 | Tapperson et al. | Aug 1998 | A |
| 5796602 | Wellan et al. | Aug 1998 | A |
| 5797038 | Crawford et al. | Aug 1998 | A |
| 5801770 | Paff et al. | Sep 1998 | A |
| 5801942 | Nixon et al. | Sep 1998 | A |
| 5805442 | Crater et al. | Sep 1998 | A |
| 5805922 | Sim et al. | Sep 1998 | A |
| 5808907 | Shetty et al. | Sep 1998 | A |
| 5812394 | Lewis et al. | Sep 1998 | A |
| 5815152 | Collier et al. | Sep 1998 | A |
| 5822220 | Baines | Oct 1998 | A |
| 5828851 | Nixon et al. | Oct 1998 | A |
| 5828882 | Hinckley | Oct 1998 | A |
| 5831669 | Adrain | Nov 1998 | A |
| 5832418 | Meyer | Nov 1998 | A |
| 5838563 | Dove et al. | Nov 1998 | A |
| 5838920 | Rosborough | Nov 1998 | A |
| 5838969 | Jacklin et al. | Nov 1998 | A |
| 5841360 | Binder | Nov 1998 | A |
| 5841654 | Verissimo | Nov 1998 | A |
| 5841963 | Nakamikawa et al. | Nov 1998 | A |
| 5844601 | McPheely et al. | Dec 1998 | A |
| 5847957 | Cohen et al. | Dec 1998 | A |
| 5848393 | Goodridge et al. | Dec 1998 | A |
| 5854944 | Catherwood et al. | Dec 1998 | A |
| 5859966 | Hayman et al. | Jan 1999 | A |
| 5862052 | Nixon et al. | Jan 1999 | A |
| 5872992 | Tietjen et al. | Feb 1999 | A |
| 5873089 | Regache | Feb 1999 | A |
| 5874990 | Kato | Feb 1999 | A |
| 5878415 | Olds | Mar 1999 | A |
| 5880775 | Ross | Mar 1999 | A |
| 5903455 | Sharpe, Jr. et al. | May 1999 | A |
| 5909368 | Nixon et al. | Jun 1999 | A |
| 5909586 | Anderson | Jun 1999 | A |
| 5920479 | Sojoodi et al. | Jul 1999 | A |
| 5930768 | Hooban | Jul 1999 | A |
| 5940294 | Dove | Aug 1999 | A |
| 5956487 | Venkatraman et al. | Sep 1999 | A |
| 5960214 | Sharpe, Jr. et al. | Sep 1999 | A |
| 5975737 | Crater et al. | Nov 1999 | A |
| 5980078 | Krivoshein et al. | Nov 1999 | A |
| 5980090 | Royal, Jr. et al. | Nov 1999 | A |
| 5982362 | Crater et al. | Nov 1999 | A |
| 5994998 | Fisher et al. | Nov 1999 | A |
| 5995916 | Nixon et al. | Nov 1999 | A |
| 6014591 | Ikeda | Jan 2000 | A |
| 6014612 | Larson et al. | Jan 2000 | A |
| 6018627 | Iyengar et al. | Jan 2000 | A |
| 6026336 | Sakurai et al. | Feb 2000 | A |
| 6026352 | Burns et al. | Feb 2000 | A |
| 6032208 | Nixon et al. | Feb 2000 | A |
| 6035264 | Donaldson et al. | Mar 2000 | A |
| 6041306 | Du et al. | Mar 2000 | A |
| 6049775 | Gertner et al. | Apr 2000 | A |
| 6055633 | Schrier et al. | Apr 2000 | A |
| 6061603 | Papadopoulos et al. | May 2000 | A |
| 6073109 | Flores et al. | Jun 2000 | A |
| 6078320 | Dove et al. | Jun 2000 | A |
| 6094600 | Sharpe, Jr. et al. | Jul 2000 | A |
| 6095674 | Verissimo et al. | Aug 2000 | A |
| 6098116 | Nixon et al. | Aug 2000 | A |
| 6105132 | Fritch et al. | Aug 2000 | A |
| 6115468 | De Nicolo | Sep 2000 | A |
| 6129449 | McCain et al. | Oct 2000 | A |
| 6139177 | Venkatraman et al. | Oct 2000 | A |
| 6140911 | Fischer et al. | Oct 2000 | A |
| 6151583 | Ohmura et al. | Nov 2000 | A |
| 6151625 | Swales et al. | Nov 2000 | A |
| 6176421 | Royal, Jr. et al. | Jan 2001 | B1 |
| 6195591 | Nixon et al. | Feb 2001 | B1 |
| 6201996 | Crater et al. | Mar 2001 | B1 |
| 6212559 | Bixler et al. | Apr 2001 | B1 |
| 6218930 | Katzenberg et al. | Apr 2001 | B1 |
| 6268789 | Diamant et al. | Jul 2001 | B1 |
| 6269473 | Freed et al. | Jul 2001 | B1 |
| 6345382 | Hughes | Feb 2002 | B1 |
| 6349287 | Hayashi | Feb 2002 | B1 |
| 6397191 | Notani et al. | May 2002 | B1 |
| 6405099 | Nagai et al. | Jun 2002 | B1 |
| 6405210 | Doyle et al. | Jun 2002 | B1 |
| 6412070 | Van Dyke et al. | Jun 2002 | B1 |
| 6442442 | Weinhofer | Aug 2002 | B1 |
| 6445962 | Blevins et al. | Sep 2002 | B1 |
| 6449715 | Krivoshein | Sep 2002 | B1 |
| 6470227 | Rangachari et al. | Oct 2002 | B1 |
| 6473660 | Thibault | Oct 2002 | B1 |
| 6477434 | Wewalaarachchi et al. | Nov 2002 | B1 |
| 6510351 | Blevins et al. | Jan 2003 | B1 |
| 6510352 | Badavas et al. | Jan 2003 | B1 |
| 6574515 | Kirkpatrick et al. | Jun 2003 | B1 |
| 6594588 | Peden et al. | Jul 2003 | B1 |
| 6606740 | Lynn et al. | Aug 2003 | B1 |
| 6675230 | Lewallen | Jan 2004 | B1 |
| 6718533 | Schneider | Apr 2004 | B1 |
| 6725445 | Leymann et al. | Apr 2004 | B1 |
| 6754885 | Dardinski | Jun 2004 | B1 |
| 6760687 | Apel et al. | Jul 2004 | B2 |
| 6801224 | Lewallen | Oct 2004 | B1 |
| 6801225 | Gould | Oct 2004 | B1 |
| 6806847 | Nixon et al. | Oct 2004 | B2 |
| 6832120 | Frank et al. | Dec 2004 | B1 |
| 6850973 | Larson et al. | Feb 2005 | B1 |
| 6854122 | Sheriff et al. | Feb 2005 | B1 |
| 6854123 | Lewallen | Feb 2005 | B1 |
| 6975914 | DeRemer et al. | Dec 2005 | B2 |
| 7069101 | Arackaparambil et al. | Jun 2006 | B1 |
| 7174230 | Arackaparambil et al. | Feb 2007 | B2 |
| 7242991 | Budinger et al. | Jul 2007 | B2 |
| 7272815 | Eldridge et al. | Sep 2007 | B1 |
| 7363377 | Alban et al. | Apr 2008 | B1 |
| 20010007133 | Moriconi et al. | Jul 2001 | A1 |
| 20010044738 | Elkin et al. | Nov 2001 | A1 |
| 20010056362 | Hanagan et al. | Dec 2001 | A1 |
| 20020016725 | Eichstaedt et al. | Feb 2002 | A1 |
| 20020022900 | Honda | Feb 2002 | A1 |
| 20020026514 | Ellis et al. | Feb 2002 | A1 |
| 20020046072 | Arai et al. | Apr 2002 | A1 |
| 20020065701 | Kim et al. | May 2002 | A1 |
| 20020138316 | Katz et al. | Sep 2002 | A1 |
| 20020178077 | Katz et al. | Nov 2002 | A1 |
| 20030004771 | Yaung | Jan 2003 | A1 |
| 20030004874 | Ludwig et al. | Jan 2003 | A1 |
| 20030033443 | Igotti | Feb 2003 | A1 |
| 20030051068 | Eldridge | Mar 2003 | A1 |
| 20030055668 | Saran et al. | Mar 2003 | A1 |
| 20030106039 | Rosnow et al. | Jun 2003 | A1 |
| 20030167269 | Gupta | Sep 2003 | A1 |
| 20030176940 | Rangachari et al. | Sep 2003 | A1 |
| 20030177046 | Socha-Leialoha | Sep 2003 | A1 |
| 20030181991 | Chau et al. | Sep 2003 | A1 |
| 20030200527 | Lynn et al. | Oct 2003 | A1 |
| 20030217053 | Bachman et al. | Nov 2003 | A1 |
| 20030217054 | Bachman et al. | Nov 2003 | A1 |
| 20030225462 | Bachman et al. | Dec 2003 | A1 |
| 20040015821 | Lu et al. | Jan 2004 | A1 |
| 20041111512 | Barth | Jun 2004 | |
| 20040254465 | Sano et al. | Dec 2004 | A1 |
| 20050074018 | Zintel et al. | Apr 2005 | A1 |
| 20050093881 | Okita et al. | May 2005 | A1 |
| 20050155039 | Miller et al. | Jul 2005 | A1 |
| 20060143437 | Narin | Jun 2006 | A1 |
| 20070150333 | Hurst et al. | Jun 2007 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 411 869 | Jul 1990 | EP |
| 1502218 | Feb 2005 | EP |
| WO 9504314 | Feb 1995 | WO |
| WO 9631047 | Mar 1996 | WO |
| WO 9623377 | Aug 1996 | WO |
| WO 9707486 | Feb 1997 | WO |
| WO 9820649 | May 1998 | WO |
| WO 9836518 | Aug 1998 | WO |
| WO 9854843 | Dec 1998 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20030225462 A1 | Dec 2003 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60372770 | Apr 2002 | US |
