Abstract: A control system, a safety system, etc., within a process plant may each use one or more state machine function blocks that can be easily integrated into a function block diagram programming environment. Such a state machine function block may include one or more inputs, which may or may not cause a state machine implemented by the state machine function block to change states. The state machine function block may also include a plurality of outputs. Output configuration data associated with the function block may indicate values of the outputs of the function block for each of the states of the state machine. The state machine function block may use this output configuration data to determine its outputs when in a particular state.

Abstract: A process control system capable of executing a function after initiation thereof by a user includes a computer having a memory and a processing unit. A security module stored in the memory of the computer and adapted to be executed on the processing unit of the computer analyzes security information to determine whether the function should be executed. The security information is collected contemporaneously with the initiation of the function and in association therewith.

Abstract: A cause and effect function block, which can be easily integrated into a function block diagram programming environment in a process plant safety system to implement the cause and effect logic specified by a traditional cause and effect matrix, includes a set of cause inputs and a set of effect outputs. A multiplexer within the cause and effect function block receives each of the cause inputs and is coupled to one or more state machines, with a separate state machine existing for each effect output. The multiplexer decodes each of the cause inputs and, based on the cause inputs and previously identified cause and effect matrix logic, provides a trip signal to one or more of the state machines. Upon receiving a trip signal, a state machine forces an associated effect output into a tripped or safe state.

Abstract: A process plant control system includes a batch execution engine that spawns or creates an individual batch process application in a separate application process space for each batch to be run within a process plant. The batch execution engine includes communication software for communicating with one or more batch operator interfaces or other interfaces that are used to set up batch runs, a master process equipment model reflecting the current state of the equipment within the process plant and a batch execution manager that creates individual batch processes and spawns each of the individual batch processes to run in a separate application process space.

Abstract: A cause and effect function block, which can be easily integrated into a function block diagram programming environment in a process plant safety system to implement the cause and effect logic specified by a traditional cause and effect matrix, includes a set of cause inputs and a set of effect outputs. A multiplexer within the cause and effect function block receives each of the cause inputs and is coupled to one or more state machines, with a separate state machine existing for each effect output. The multiplexer decodes each of the cause inputs and, based on the cause inputs and previously identified cause and effect matrix logic, provides a trip signal to one or more of the state machines. Upon receiving a trip signal, a state machine forces an associated effect output into a tripped or safe state.

Abstract: A process control system includes an executive routine located at a first node of a process control system, one or more soft phases located at other nodes remote from the first node and communication software located in the each of the nodes to enable the executive routine to call and execute the soft phases that are at nodes remote from the first node. This operation may reduce loading or communication traffic on the batch executive node and enables the operator to interact with a soft phase at a workstation or node that is convenient to the operation of the soft phase, which makes the operator's task easier and results in faster execution of the soft phase.

Abstract: Methods and apparatus for batch process control in which a Phase Logic Module operable in accordance with the state machine model of the batch server program is embedded within a programmable controller. More specifically, a phase executed by the batch server program in a data processing device is operable in accordance with a pre-defined state machine model (typically compliant with the ISA S88.01 standard). A Phase Logic Module (PLM) is implemented within a programmable controller in accordance with the same state machine model so as to mirror the state machine operation of the batch server process within the programmable controller. The PLM is pre-implemented and standardized. Specific state logic for performing desired control in accordance with the desired batch processing is defined by a control engineer using well known languages and tools and integrated with the standard PLM state machine.