Module class subsets for industrial control

CROSS REFERENCE TO RELATED APPLICATION

0001This application claims the benefit of U.S. Provisional Patent Application No. 60/862,403 entitled MODULE CONTROL AND STATE PROPAGATION, and filed on Oct. 20, 2006, the entirety of which is incorporated herein by reference.

TECHNICAL FIELD

0002The claimed subject matter relates generally to industrial control systems and more particularly to module class components that are defined to facilitate software re-use and mitigate manual coding operations.

BACKGROUND

0003One type of industrial control process is referred to as a batch process, which involves subjecting raw materials to processing steps using one or more pieces of equipment to produce a “batch” of product. Efforts to automate batch processing have led to the formation of standards committees by members of industries involved in batch processing and suppliers of batch processing equipment, among others. The general purpose of these standards committees has been to define uniform standards for automated batch processing. One such standard has been promulgated by the International Society for Measurement and Control, an international organization concerned with issues of process control. This standard is entitled Batch Control Part 1: Models and Terminology and is often referred to as the ISA S88.01-1995 standard (or “S88” for purposes of this application).

0004The S88.01 standard defines models of equipment and procedures for use in automated batch processes, as well as terminology for use in referring to those models and their elements. The S88.01 standard defines a “batch process” as a process that leads to the production of finite quantities of material by subjecting quantities of input materials to an ordered set of processing activities over a finite period of time using one or more pieces of equipment. A “batch” is defined as the material that is being produced or has been produced by a single execution of a batch process.

0005Batch-processing equipment (i.e., controllable elements such as valves, heaters, mixers, and so forth) is operated according to procedures to produce a batch. Generally, such equipment is referred to synonymously as equipment, equipment modules, processing equipment, or physical elements. The procedures to operate such physical elements are often referred to by the S88.01 standard as the “procedural model.” According to the S88.01 standard, the procedural model is structured as a hierarchical ranking of procedures, with the highest level encompassing each of the lower levels, the next highest level encompassing each of the levels below it, and so on. Typically, the levels of the S88.01 procedural model of a particular application are, in descending order: the “procedure;” the “unit procedure;” the “operation;” and the “phase.”

0006The term “procedural element” generally refers to components that employ any of the levels of the S88.01 procedural model, not just to those of the “procedure” level or any other single level of the procedural model. The highest-level procedural element of interest is referred to as a procedure, which is made up of one or more unit procedures. Each unit procedure is in turn made up of one or more operations, which are each in turn made up of one or more phases. The S88.01 procedural model does not preclude definition and use of other hierarchical levels, nor does it require that each level be present in particular applications. Rather, the standard is intended to provide a broad, standardized model for describing the procedures followed in automated batch-process control.

0007A problem that has evolved with the adoption of such standards is how to implement desired coordination between individual elements such as modules that are defined within the respective standard. Often, Engineers design custom code for each installation to perform the nuances of module coordination and communication. In prior systems, modules which are part of a uniform processing model such as S88 or S95 are developed where various code portions within the modules are designed or written by hand. This is repeated many times over as most systems implement several modules to produce a given product. As can be appreciated, it can be exceedingly costly to develop and implement code for each installation.

SUMMARY

0008The following presents a simplified summary in order to provide a basic understanding of some aspects described herein. This summary is not an extensive overview nor is intended to identify key/critical elements or to delineate the scope of the various aspects described herein. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

0009Module class subsets are provided where portions of a given module that were previously coded by hand have been identified and generated automatically for the designer in view of an identified class. The identified class represents an analysis of functional elements within the module that can be generically provided before system design/implementation. For example, Equipment or Phase Modules (or other type modules) can be decomposed into sub components and classes, thus allowing commonalty between equipment modules and other points of a module's extension to be identified. This allows building a limited number of equipment modules from the respective classes to address the large (virtually infinite) number of process or discrete applications. Example Equipment Modules provided include Generic, Material Transfer, and Equipment Verification. Respective Equipment Modules can communicate with associated Phase Modules which have also been developed according to a class structure. By identifying common portions of modules and codifying the respective portions in advance, code generation and development for the common portions identified is mitigated which in turn conserves resources for system designers and end users.

0010To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative of various ways which can be practiced, all of which are intended to be covered herein. Other advantages and novel features may become apparent from the following detailed description when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> is a schematic block diagram illustrating industrial control module and phase components for an industrial automation system.

<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of an example equipment module that has been functionally decomposed into class components.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example equipment phase that has been functionally decomposed into respective class components.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates example equipment module and equipment phase interactions.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates state processing aspects between equipment modules and equipment phases.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates example state processing between phase and equipment modules.

<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram illustrating a state processing methodology.

<figref idref="DRAWINGS">FIG. 8</figref> is a diagram illustrating module attributes.

<figref idref="DRAWINGS">FIG. 9</figref> is a diagram illustrating example resource control modules.

<figref idref="DRAWINGS">FIG. 10</figref> is a diagram illustrating a resource module.

<figref idref="DRAWINGS">FIG. 11</figref> is a diagram illustrating example resource modules.

<figref idref="DRAWINGS">FIG. 12</figref> is a diagram illustrating a resource control model.

DETAILED DESCRIPTION

0023A reduced subset of module and phase components is provided to mitigate manual coding requirements of conventional systems that adhere to applicable standards. In one aspect, a system that facilitates module design in an industrial environment is provided. The system includes a module component that defines operations to control an industrial process. At least one class component is defined within the module that identifies a generic operation for the module, where the class component executes one or more of the operations within the industrial control process.

0024It is noted that as used in this application, terms such as “component,” “module,” “model,” and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution as applied to an automation system for industrial control. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program and a computer. By way of illustration, both an application running on a server and the server can be components. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers, industrial controllers, and/or modules communicating therewith.

0025Referring initially to <figref idref="DRAWINGS">FIG. 1</figref>, a system <b>100</b> illustrates module and phase components for controlling an industrial automation environment. One or more module components <b>110</b> include one or more module class components <b>120</b>. The module class components <b>120</b> identify common functional portions of the module components <b>110</b> that can be identified and provided in advance to systems designers in order to mitigate coding or redesign of the module components themselves. As shown at <b>130</b>, a limited subset or class of module components <b>110</b> can be provided to facilitate a substantially large number of control applications. This can include defining the limited subset at <b>130</b> based in part on identified module behavior for example. Similarly, one or more phase components <b>140</b> can also be provided that in turn include one or more phase class components <b>150</b>. As with the module components <b>110</b>, the phase class components <b>150</b> can identify common portions which can be provided in advance and form a limited subset or class of phase modules that can satisfy a large number of control applications. As shown at <b>160</b>, a limited subset of phase modules <b>140</b> can be defined based in part on report or parameter data for example.

0026In general, the phase components <b>140</b> send control commands to the module components <b>110</b> and receive status there from. As will be described in more detail below with respect to <figref idref="DRAWINGS">FIGS. 2 and 3</figref>, the phase components <b>140</b> and the module components <b>110</b> can be broken into various classes such as interfaces, commands, status, parameters, and so forth. From such functional identifications via the classes, common module or phase elements can be defined allowing a limited class or subset of module and phase components to serve a large variety or control applications. In this manner, a large set of modules can be reduced to a limited subset defined by the identified classes.

0027Generally, module class subsets include portions of a given module or phase that were previously coded by hand and have been identified and generated automatically for the designer in view of an identified class. The identified class represents an analysis of functional elements within the module or phase that can be generically provided before system design/implementation. For example, Equipment or Phase Modules (or other type modules) can be decomposed into sub components and classes, thus allowing commonalty between equipment modules and other points of a module's extension to be identified. This allows building a limited number of equipment modules from the respective classes to address the substantially large number of process or discrete actions. Example Equipment Modules provided include Generic, Material Transfer, and Equipment Verification. Respective Equipment Modules can communicate with associated Phase Modules which have also been developed according to a class structure.

0028A limited number of equipment modules and equipment phases may be used with minimal customization to satisfy the majority of process action requirements although it is to be appreciated that other modules can be added to the subset. Behavior can be a determining factor in the classification of Equipment Modules, for example. The following table outlines example behavior for three example classes of Equipment Module.

0000<tables id="TABLE-US-00001" num="00001"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="42pt" align="left" /><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="49pt" align="left" /><colspec colname="3" colwidth="56pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry /><entry>Equipment</entry></row><row><entry /><entry>Material Transfer</entry><entry>Generic</entry><entry>Verification</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="70pt" align="left" /><colspec colname="3" colwidth="49pt" align="left" /><colspec colname="4" colwidth="56pt" align="left" /><tbody valign="top"><row><entry>Behavior</entry><entry>Ability to restart (e.g.,</entry><entry>Momentary</entry><entry>Confirmation of</entry></row><row><entry /><entry>Advance/Correct)</entry><entry /><entry>Unit Status</entry></row><row><entry /><entry /><entry>Latch/Unlatch</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0029Report/Parameter data can be a determining factor in the classification of Equipment Phases. The following table outlines an example data requirement for three classes of Equipment Phases.

0000<tables id="TABLE-US-00002" num="00002"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="offset" colwidth="42pt" align="left" /><colspec colname="1" colwidth="70pt" align="left" /><colspec colname="2" colwidth="42pt" align="left" /><colspec colname="3" colwidth="63pt" align="left" /><thead><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row><row><entry /><entry /><entry /><entry>Equipment</entry></row><row><entry /><entry>Material Transfer</entry><entry>Generic</entry><entry>Verification</entry></row><row><entry /><entry namest="offset" nameend="3" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="4"><colspec colname="1" colwidth="42pt" align="left" /><colspec colname="2" colwidth="70pt" align="left" /><colspec colname="3" colwidth="42pt" align="left" /><colspec colname="4" colwidth="63pt" align="left" /><tbody valign="top"><row><entry>Parameter</entry><entry>Setpoint</entry><entry>Setpoint</entry><entry>Equipment Status</entry></row><row><entry /><entry>Positive Tolerance</entry><entry /><entry>Expected</entry></row><row><entry /><entry>Negative Tolerance</entry></row><row><entry>Report</entry><entry>Exit Status</entry><entry>Exit Status</entry><entry>Exit Status</entry></row><row><entry /><entry /><entry /><entry>Equipment Status</entry></row><row><entry /><entry>Actual Amount</entry><entry>Actual</entry><entry>Actual</entry></row><row><entry /><entry>Error</entry></row><row><entry /><entry>Initial Gross Weight</entry></row><row><entry /><entry>Final Gross Weight</entry></row><row><entry /><entry>Material Transfer</entry></row><row><entry /><entry>Status</entry></row><row><entry namest="1" nameend="4" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

0030As will be described in more detail below, the module components <b>110</b> or phase components <b>140</b> can be an association of logic with one or more resources. The logic includes program code that can alter the state of a resource for example, ladder code, function chart, script, JAVA, C code, and so forth. The resources are those components or elements that perform an activity in a system including equipment and personnel that perform work in a system. Other examples of types of resources include Equipment, Material, Personnel, Segments and Storage. Personnel and equipment (machines) can perform activities in a system. Resources that can perform work can be classified as active resources (e.g., CNC machine, Injection molding machine), whereas other equipment resources can be considered passive resources (e.g., sensor, material). In general, the modules hide the user from internal interfaces, messages, and logic specific to the resources yet provide standard or generic interfaces to external systems or between components.

0031Modules may include other modules including nested modules where standard module behaviors and attribute patterns can be represented using common data model representations for module classes, module templates and module inheritance. Module classes and templates can be maintained in libraries which facilitate access to desired system functionality and further promote system integration. Resources can have various states associated therewith such as common S88 state classifications including idle, hold, abort, run, reset, stop, restart, and so forth where the module can present logic to represent state machines that manage the state of the resource. During application, resource modules (described below) can take on the name of the resource that is the primary focus on the module. For example, an Equipment module is primarily focused on coordination of equipment but may involve personnel in the process. Similarly, a Personnel module is focused on coordination of personnel but may involve other resources in the process. A Control Module that manages a material may be referred to as a Material Control Module and so forth.

0032It is noted that components associated with the system <b>100</b> can include various computer or network components such as servers, clients, programmable logic controllers (PLCs), communications modules, mobile computers, wireless components, control components and so forth which are capable of interacting across a network. Similarly, the term PLC as used herein can include functionality that can be shared across multiple components, systems, and/or networks. For example, one or more PLCs can communicate and cooperate with various network devices across the network. This can include substantially any type of control, communications module, computer, I/O device, sensor, Human Machine Interface (HMI) that communicate via the network which includes control, automation, and/or public networks. The PLC can also communicate to and control various other devices such as Input/Output modules including Analog, Digital, Programmed/Intelligent I/O modules, other programmable controllers, communications modules, sensors, output devices, and the like.

0033The network can include public networks such as the Internet, Intranets, and automation networks such as Control and Information Protocol (CIP) networks including DeviceNet and ControlNet. Other networks include Ethernet, DH/DH+, Remote I/O, Fieldbus, Modbus, Profibus, wireless networks, serial protocols, and so forth. In addition, the network devices can include various possibilities (hardware and/or software components). These include components such as switches with virtual local area network (VLAN) capability, LANs, WANs, proxies, gateways, routers, firewalls, virtual private network (VPN) devices, servers, clients, computers, configuration tools, monitoring tools, and/or other devices.

0034Referring now to <figref idref="DRAWINGS">FIG. 2</figref>, an example equipment module <b>200</b> that has been functionally decomposed into respective class components is illustrated. It is to be appreciated that the equipment module <b>200</b> is exemplary in nature and that other types of modules and/or classes are possible. The equipment module <b>200</b> (EM) can include an equipment phase interface <b>210</b> that provides a linkage to/from an Equipment Phase (EP) which is described in more detail below with respect to <figref idref="DRAWINGS">FIG. 3</figref>. This interface <b>200</b> determines how the EM <b>200</b> interacts with the EP. A standard Equipment Phase interface <b>210</b> may be created that applies to all Equipment Module classes. These should provide a mechanism to pass report/parameter data and provide a simple interface between the Equipment Phase and the Equipment Module.

0035At <b>220</b>, a Unit interface provides a linkage to/from a respective Unit such as described in a typical S88/S95 procedure. This interface <b>220</b> determines how the EM <b>200</b> interacts with the Unit. A standard Unit interface <b>220</b> may be created that applies to all Equipment Module classes. Equipment Modules <b>200</b> should be aware of their Unit, where the propagation of mode and faults may be facilitated via the Unit interface <b>220</b>.

0036An Equipment interface <b>230</b> provides a linkage to/from Equipment (Subordinate EM's and control modules (CM's)). This interface <b>230</b> determines how the EM <b>200</b> interacts with Equipment. A standard equipment interface can be created that applies to the Equipment Module classes.

0037At <b>240</b>, coordination control, and sequencing of equipment refers to the logic associated with commanding the state of subordinate Equipment/Control modules. Generally, coordination and sequencing is facilitated via the Equipment Interface <b>210</b>. Coordination and Sequencing may be achieved using a number of different methods, such as via hard coded logic or sequencer. The method is generally not considered part of the Equipment Module. Typically, coordination and sequencing is implementation dependant, and should not be used to determine the definition of class(es).

0038At <b>250</b>, behavior describes the functional behavior of a particular Equipment Module <b>200</b>. A number of the behaviors <b>250</b> exhibited by an Equipment Module <b>200</b> are common to Equipment Modules. Some equipment modules <b>200</b> may exhibit unique behavior. For instance, a Material Transfer may require the ability to restart in addition to under tolerance. Some differences in behavior <b>250</b> may be masked on/off using configuration commands. Generally, behavior <b>250</b> is a determining factor in establishing the definition of Equipment Module class(es).

0039At <b>260</b>, parameters (e.g., process parameters) are data items which are provided by the recipe phase, via the Equipment Phase to the Equipment Module <b>200</b>. Report (process results) data items at <b>260</b> are produced by the Equipment Module <b>200</b>, and published to the Recipe Phase via the Equipment Phase interface at <b>210</b>. Generally, equipment modules <b>200</b> inherit recipe parameters from Equipment Phases, and process these parameters. Equipment modules <b>200</b> produce report data at <b>260</b> and provide this data to the Equipment Phase via the interface <b>210</b>. A standardized data structure may be created for parameter data within the Equipment Module <b>200</b>. The Equipment Module <b>200</b> can also provide the capability to customize this data structure. A standardized data structure may be created for report data within the Equipment Module <b>200</b> which can also provide the capability to customize this data structure. Depending on the number of unique data sets required for report/parameters, the processing and production of this data may be a determining factor in the definition of Equipment Module class(es). As shown at <b>270</b>, other class components in the equipment module <b>200</b> can include mode data, permissive data, and command/status data that can be passed to/from the respective interfaces associated with the equipment module.

0040Turning to <figref idref="DRAWINGS">FIG. 3</figref>, an example equipment phase <b>300</b> that has been functionally decomposed into respective class components is illustrated. The equipment phase <b>300</b> (EP) can interface with the equipment module described above with respect to <figref idref="DRAWINGS">FIG. 2</figref>. It is to be appreciated that the equipment phase <b>300</b> is exemplary in nature and that other types of phases and/or classes are possible.

0041A phase interface <b>310</b> provides a linkage to/from a respective Recipe Phase (not shown) to control a process. This interface <b>310</b> determines how the EP <b>300</b> interacts with the Recipe Phase. A standard Phase interface may be created that applies to all Equipment Phase classes, which supports the S88 state model, or subset of the S88 state model, for example. The phase interface should also provide a component to pass report/parameter data.

0042At <b>320</b>, an Equipment Module interface provides a linkage to/from the respective Equipment Module such as depicted in <figref idref="DRAWINGS">FIG. 2</figref>. This interface determines how the EP <b>300</b> interacts with the Equipment module. A standard Equipment Module interface <b>320</b> may be created that applies to all Equipment Phase classes and should provide a component to pass report/parameter data.

0043At <b>330</b>, parameters (process parameters) are data items which are provided by the recipe phase, to the Equipment Phase <b>300</b>. The Equipment Phase <b>300</b> then provides this data to the Equipment Module. Report (process results) data items are produced by the Equipment Module, and published to the Equipment Phase <b>300</b>. The Equipment Phase then provides this data to the Equipment Phase. Generally, Equipment modules inherit recipe parameters from Equipment Phases. Such modules also produce report data and provide this data to the Equipment Phase <b>300</b>. Depending on the number of unique data sets required for report/parameters <b>330</b>, the processing and production of this data may be a determining factor in the definition of Equipment Module class(es).

0044At <b>340</b>, behavior describes the functional behavior of a particular Equipment Module. Generally, the Equipment Phase <b>300</b> should support the S88 state model, a subset of the S88 state model, or similar models. Typically, all Equipment Phases exhibit similar behavior. Differences in behavior may be masked on/off using configuration. Behavior <b>340</b> is generally not a determining factor in establishing the definition of Equipment Module class(es) described above. As shown, one or more S88 states may be controlled at <b>350</b>.

0045Referring to <figref idref="DRAWINGS">FIG. 4</figref>, example equipment module and equipment phase interactions are illustrated. As shown, an equipment module <b>400</b> sequences and coordinates equipment via one or more control modules <b>410</b>. Similar to above, the equipment module <b>410</b> may include an equipment interface <b>420</b>, a unit interface <b>430</b>, and an equipment phase interface <b>440</b> that interacts with a respective equipment phase <b>450</b>. The equipment module <b>410</b> may also include components for commands, status, modes (e.g., manual versus automatic, fault, reset), and/or permissives as shown at <b>454</b>. The equipment module <b>400</b> and the equipment phase <b>450</b> exchange phase requests and status at <b>460</b>. As shown the equipment phase <b>410</b> can include parameters, reports commands, and/or status at <b>470</b> which are exchanged via an equipment module interface <b>480</b>. The following functions and concepts can be applied to the Equipment Module class:

0046Data Structure—This Equipment Module—Equipment Verification is structured in a fashion that allows an individual to easily find and understand information issued to and produced by this module. For example, commands can be grouped in a common section, status is given in a separate section, and configuration parameters are grouped together as well.

0047States—An Equipment Module—Equipment Verification acts as a state machine for a particular grouping of equipment. The actual states are defined during implementation. Equipment Module—Equipment Verification states may be initiated by an Equipment Phase, but an Equipment Module's states does not need to follow the S88 state model.

0048Modes—This module functions via the control system in auto or manual mode.

0049Commands—An Equipment Module—Equipment Verification is commanded to a state by a state change request. In MANUAL mode this is a manual request. In AUTOMATIC mode this is an auto request.

0050Status—For each requested state the state machine can latch control module requests required to bring the EM to defined state. At this time the state machine will be in a MOVING state. This can be seen on the EM faceplate. When the control modules move to the requested state, the state machine can command the current state to the requested state and the face place can indicate that the module is no longer moving but in the requested state.

0051Faults &amp; Warnings—Module Fault section. This section has the following subsections:

0052Control Module Faults section. A fault of Control Module under the control of the EM can generate an Equipment Module fault.

0053Process Fault Section. Any other system condition which should generate an EM fault

0054State Machine section. At and given time an EM is either in Fault Mode or one of the states defined for the module.

0055Interlocks—If the process or safety interlocks are lost, the Equipment Module—Equipment Verification is de-energized. A process interlock bypass configuration has been provided to circumvent any process interlocks for the device. If at any time during energized operation of the device either interlock is not present, a device failure will occur.

0056Simulation—Equipment Module—Equipment Verification simulation is achieved indirectly within subordinate Control Modules.

0057Configuration—By modifying an Equipment Module—Equipment Verification instance's configuration data, the behavior of a particular module instance can be modified. When all module configurations are considered valid, an individual of appropriate authorization level may save the current settings. If the Equipment Module—Equipment Verification configuration settings deviate from the saved setting, an indication will appear on the HMI faceplate. An authorized individual will then have the opportunity to save current configurations or restore the previously saved configuration.

0058Turning to <figref idref="DRAWINGS">FIG. 5</figref>, state processing aspects between equipment modules and equipment phases are illustrated. An equipment module <b>500</b> includes sequence logic <b>510</b> having step numbers, number of steps, and sequence actions, that interact with various commands, status, modes, and permissives at <b>520</b>, where permissives define conditions that allow or prevent users/machines from taking actions. The sequence logic <b>510</b> receives commands <b>530</b> from an equipment phase <b>540</b> and transmits status at <b>550</b> to the equipment phase. As shown, at least one unit <b>560</b> interfaces to the equipment module <b>500</b>. As commands are generated by the equipment phase <b>540</b>, states are commanded to one or more control modules at <b>570</b>. In this example at <b>570</b>, user implemented logic processes auto requests, set point controls, and provides step completion logic. As can be appreciated, other configurations and controls can be provided.

0059Proceeding to <figref idref="DRAWINGS">FIG. 6</figref>, example state processing is shown between phase and equipment modules. An Equipment Module <b>600</b> includes core logic <b>604</b> that manages an initial step number selection for each of the defined transient phase states provided from at least one equipment phase <b>610</b>. Such logic <b>604</b> can be responsible for setting the transient phase state complete bit at <b>620</b>, for example. The Equipment Module <b>600</b> can then report back to the Equipment Phase <b>610</b> that the corresponding transient phase's state is complete at <b>630</b>. Generally, a user implemented sequence can be written using steps 1 to 99, for example. For each of the states that the user chooses to implement, the Equipment Module <b>600</b> can store the initial step number for this state. When a state change is detected by the Equipment Module <b>600</b>, it can set an active state status bit and on a one-shot set the current step number equal to the state initial step number.

0060As an example, if an Equipment Module <b>600</b> is in the Running state on step 03 of its sequence at <b>640</b> and a request is received by the Equipment Module for a state change to Aborting. The Equipment Module <b>600</b> can change the active state status bit to Aborting and on a one-shot transition the current step number to 50 at <b>650</b>. This example assumes that the user has chosen to write the Running logic steps starting at 01 and the Aborting logic steps starting at 50, as illustrated at <b>604</b>. As can be appreciated, a plurality of various state sequences and commands can be executed (e.g., aborting, holding, resetting, restarting, stopping, and so forth).

0061<figref idref="DRAWINGS">FIG. 7</figref> illustrates a state processing methodology <b>700</b> for an industrial automation system. While, for purposes of simplicity of explanation, the methodology is shown and described as a series of acts, it is to be understood and appreciated that the methodologies are not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology as described herein.

0062Proceeding to <b>710</b>, a decision is made as to whether or not a running request is received from an equipment phase. If no request is received at <b>710</b>, the process loops back to <b>710</b> and waits for a received request. If a request is received at <b>710</b>, the process proceeds to <b>714</b> and initiates an equipment module running state. At <b>720</b>, the process determines such as via status information if in fact the equipment module has made it to the running state. If not, the process waits for status at <b>730</b>. If the equipment module has made it to the running state at <b>720</b>, the process proceeds to <b>724</b>. At <b>724</b>, the process writes and initial step number for the running state. At <b>730</b>, a test is made to determine if user interface logic (UIL) has reported complete. If not, the process waits at <b>730</b> for suitable status. If the UIL has completed at <b>730</b>, the process proceeds to <b>734</b>.

0063At <b>734</b>, the process <b>700</b> enters a stopping state and proceeds to <b>740</b> where a test is made to determine whether the equipment module has stopped. If the module has not stopped, the process remains at <b>740</b> and continues to test for the stopping event. When a stopping event has been detected at <b>740</b>, the process proceeds to <b>744</b> and determines whether the user has defined a stopping state. If not, the process proceeds to <b>750</b> and sets a report data available trigger. If the user has defined a stopping state at <b>744</b>, the process proceeds to <b>754</b> and writes a stopping state initial step number. At <b>760</b>, the process checks to determine if the user interface logic (UIL) has reported complete. If not, the process remains at <b>760</b>. It the UIL has completed at <b>760</b>, the process proceeds to <b>750</b> where a report data available trigger is set. Proceeding to <b>764</b>, an equipment module complete status flag is set. At <b>770</b>, a test determines whether or not the equipment module state is complete. If not, the process waits at <b>770</b> for the state to complete. Upon completion at <b>770</b>, status is sent to the equipment phase that reports that the running state has completed. As can be appreciated, other states than running can be similarly processed between an equipment phase and an equipment module. Also, multiple equipment phase and modules can be employed wherein more than one phase communicates to one or more modules and visa versa.

0064Referring now to <figref idref="DRAWINGS">FIG. 8</figref>, module attributes <b>800</b> are illustrated. The attributes <b>800</b> depicted in <figref idref="DRAWINGS">FIG. 8</figref> include a common (or exemplary) representation that can be modules from modules. Generally, a set of standard attributes can be determined that are common to all modules. Similarly, for other types of modules described below, additional standard attributes can be defined. An example of a property <b>810</b> available on modules includes attributes such as Fault and Status at <b>814</b>. Active resource modules (e.g., equipment and personnel) can support additional properties <b>810</b> such as available/unavailable.

0065Attributes presented below are represented associations from the module to objects which may be internal in a common data model or elsewhere (e.g., CAD Files). At <b>820</b>, standard public interfaces can be provided. These interfaces <b>820</b> publish verbs <b>824</b> that are available to external systems and are documented activities that hide the complexity of the underlying code used to implement the interface. Interfaces <b>820</b> can be considered into at least two common usage scenarios. For example, interfaces <b>820</b> can be used as access points that can be used to hook in real time diagnostics, security and so forth.

0066Public verbs <b>824</b> initiate an action within the module. The activity is described to clients of the interface <b>820</b>. The implementation is considered private and is not presented to clients—for example, Open, Stop, Abort, Shut, and so forth. A data value property <b>810</b> provides public access to information that is used by the module during its operation and can be provided by request values and/or internal values (or an equivalent). The association of logic to transfer request values to internal values and vice versa are referred to as get and set logic for the value. It is noted that in a controller, if there is not a set routine to transfer request values to internal values, the internal value can overwrite the request value on the next scan providing read only capability.

0067In general, the properties <b>810</b> can be considered in at least two classifications. States have special significance for production systems and can have a specific set of values that can be represented by range or enumeration. A state can represent the current status of the primary resource being encapsulated by the module e.g., Percent open, Mode, Service (in, out), and so forth. Information that is used by the module during its operation includes access to data that is provided by interfaces <b>820</b>. e.g., Conversion Map, Name, Description, expiry date, personnel contact information. Some properties <b>810</b> can be common to all instances of resource modules (e.g., scanned copy of resource specification documents), whereas other properties <b>810</b> are specific to each module instance (e.g., Status, percent open).

0068At <b>830</b>, internal resource interfaces include interfaces from logic <b>840</b> in the module to the resource being managed at <b>850</b>, where the logic includes code and/or configuration that processes a command and/or updates state and data properties. In some cases, this can be hardware such as I/O interfaces, or in other cases it is to subordinate resource control modules that have direct interfaces. Some examples include I/O mapping, material management logic routines, and so forth. These interfaces <b>830</b> are internal to the module enabling the modules public interfaces <b>820</b> and properties <b>810</b> to be the boundary to other system components. Modules that wrap different resources but support the same public properties/interfaces can be exchanged without disrupting interfaces to other components. Generally, I/O mapping and system messaging interfaces are exposed during deployment bind processes. When bound, external interfaces <b>820</b> to runtime systems may then consider these interfaces as internal.

0069At <b>860</b>, alarm and event messages can be provided which include messages that exposed as runtime messages visible to external systems during the execution of the module. This includes alarms and events explicitly coded by the developer and system messages promoted to be visible by external systems. At <b>870</b>, one or more artifacts include information that document the operation and structure of the resource such as for example, wiring diagrams, warranties, payroll, parts supplier information, and so forth. Visualization aspects include associated graphics that present the resource state and properties to applications interacting with the resource. For example: faceplates, icons, state overlays, edit dialogs, help files. At <b>880</b>, system messages allow modules to listen for and publish data model messages to external components. Inbound messages are typically used to manage modules (configure, initialize, propagate properties, and so forth) and publish messages on module activity (resource state, data model messages, and so forth).

0070Turning to <figref idref="DRAWINGS">FIG. 9</figref>, example resource control modules <b>900</b> are illustrated. In general, resource control modules <b>900</b> provide simple control of one or more resources. The resource control module (RCM) <b>900</b> represents the logic to manage the state or data of the resource and may contain other resource control modules to achieve its respective functionality. The RCM <b>900</b> provides public interfaces via actions and properties. In some cases, an action may be a simple bit value or a request value that is interfaced to internal values in the module and in other cases more complex logic can be provided. The RCM <b>900</b> can include other resource control modules and may promote a command to be represented as segment resource control interface. Example forms of the RCM <b>900</b> include:

0071At <b>910</b>, an Equipment Control Module (Common name=“Control Module”) CM. The simplest form of basic regulatory control of equipment. Encapsulating the equipment and its control such as control of values, drives, and so forth. At <b>920</b>, a Material Control Module (MCM) can be provided. Management of Material resource instances which are represented as sub-lots including change in location, quality status, availability, order status, logic that can be performed on material sub-lots, generation of material events such as consumed, produced and moved events, sub-lot combination, expiry dates, and so forth.

0072At <b>930</b>, a Personnel Control Module (PCM) is provided. This includes management of individual people such as Active, Idle, Break states directly or via shift schedules. This also includes data associated with people such as shift time patterns, for example. Other attributes that may be managed by PCM <b>930</b> are a person's location in a plant (GPS), qualification checks, or current assignment, for example. At <b>940</b>, a Segment Control Module (SCM) includes manipulation of simple segment tasks such as piping paths, AGV paths, device state machines, robotic sequences and so forth. The SCM <b>940</b> typically performs an action on one segment such as next step to execute after the current step. At <b>950</b>, a Storage Control Module (STGCM) includes Manipulation of simple storage logic such as buffer capacity and ordering into and out of a queue for the respective storage unit or requirement.

0073<figref idref="DRAWINGS">FIG. 10</figref> illustrates a resource module <b>1000</b> for an industrial control system. Resource modules <b>1000</b> extend resource control modules described above to enable coordination of resources (equipment, people, modules and so forth) to achieve. As shown, the resource control module <b>1000</b> includes a module <b>1010</b> and a resource control interface <b>1020</b>. Resource modules <b>1000</b> are also able to represent more complex activities than resource control modules. For example, resource modules may include other resource control modules at <b>1010</b> and/or other resource modules. For example, an equipment module may leverage a subordinate material control module to represent material handling aspects or a segment module to solicit an electronic signature.

0074Before proceeding it is noted that other types of modules are possible than shown. For instance, a configuration module may include management definitions and configuration of resources—personnel, segments, equipment, segments, storage, and so forth. Another type of module includes nested modules where a module references other modules. These modules may be children of a parent module or shared from one module to another. Resource modules may include resource control modules however resource control modules should not include resource modules. Modules can include modules focused on other resource types, for example an equipment module may include equipment modules and material modules.

0075<figref idref="DRAWINGS">FIG. 11</figref> illustrates example resource modules <b>1100</b> for an industrial control system. At <b>1110</b>, an Equipment Module provides coordination of equipment modules and equipment control modules to perform a process-orientated task independent of specific material e.g., In-feed, AGV controller, Conveyor, and so forth. At <b>1120</b>, a Material Module provides coordination of material modules and material control modules to perform material focused tasks e.g., Material reservation, provision, material mass balance calculation, Bill of Material management, Work order management, and so forth. At <b>1130</b>, a Personnel Module provides coordination of personnel modules and personnel control modules to perform personnel focused tasks e.g., Electronic signature collection, Security validation, certification validation, Manual control interactions, and so forth.

0076At <b>1140</b>, a Segment Module provides coordination of segment modules and segment control modules and to execute sequences of tasks represented by segments. Segments define resource requirements and ordering that can represent most production and process activities. This module provides access to more complex tasks that require specific sequences to be followed e.g., Process Analytics Technology (PAT) integration, electronic signatures collection, defect, process deviation and fault recovery processing. The segment module <b>1140</b> may also construct a sequence to be followed that can be applied as manual, automatic or semi automatic sequences (e.g., Route, recipe execution) At <b>1150</b>, a Storage Module provides coordination of storage related activities, allocation of storage to requestors, modeling of inventory calculations and so forth. This also includes interaction with higher-level systems that manage storage and inventory information.

0077<figref idref="DRAWINGS">FIG. 12</figref> illustrates an example resource control model <b>1200</b> for an industrial control system. Resource Control Interfaces are the interfaces exposed to production management systems for resource binding and arbitration purposes. The interfaces are elements of the resource control model <b>1200</b> including procedures, operations or phases. These interfaces are made available by exposure via one or more capabilities <b>1210</b> described below. Procedures, operations and phases depicted in this model <b>1200</b> are commonly referred to in association with their module resource type such as Equipment Phase, Personnel Phase, Segment Phase, or as a generic Resource Phase where no specific resource module is required. Production management including Product Production Rules (production route or control recipe) physically bind to (reference) resource control phases to perform work. The availability of other resources <b>1220</b> such as material, equipment, personnel are considered during the binding process of product production rules to work centers (production lines, process cells, and so forth). These selection processes evaluate resource capabilities to locate the appropriate resource for the task.

0078Resource capabilities <b>1210</b> include the resource <b>1220</b> required to perform work in a production system. Consequently, resources <b>1220</b> are at the centre of, efficiency, capacity, scheduling and arbitration considerations. A resource's ability to work or be available to allow work to commence is represented as resource capability at <b>1230</b>. The existence of capability <b>1230</b> associated with a resource <b>1220</b> does not make the resource available for production; the resource's capability <b>1230</b> is associated with organizational units <b>1240</b> that are will support the respective resource capability. For example, an operator (personnel resource) may have qualifications for a Mixer in line <b>1</b>, where this qualification capability is only in effect with that specific mixer unless explicitly directed. Resource arbitration algorithms can search for resource capabilities <b>1230</b> in the scope of organizational units <b>1240</b> they are to be executed within.

0079Resources <b>1220</b> publish capabilities to organizational units <b>1240</b> for use by system processes in a given scope. Modules are a type of resource and can be accessed directly by published capabilities <b>1210</b>. However, a more common interface to Resource Modules is via verbs that are supported by the Resource Module noted above. These verbs are Resource Control elements (phases, operations, procedures . . . ) which are segments. A published capability of a resource module is typically one of the phases supported the module. Resource control interfaces are published (made available) to the outside world as capabilities <b>1210</b>. Resource modules provide the ability to promote a command to become a resource control interface.

0080Some process control systems are built using only Resource control modules (especially control modules). Examples of this are continuous processes such as petrochemical and heavy chemical plants. In order to initiate, the process takes a plant up to its running state or makes a change to the state of a series of commands that are initiated and coordinated to achieve the new state. It is also possible to promote commands from resource control modules to appear as capabilities that can be accessed as “tuning knobs” for tweaking the system between system states. As shown in the model <b>1200</b>, the resource <b>1220</b> and capability can be associated with a higher-level class or abstraction <b>1250</b>.

0081What has been described above includes various exemplary aspects. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these aspects, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the aspects described herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.