Fisher-rosemount Systems, Inc

David L Deitz

William George Irwin

Grant Wilson

Godfrey Roland Sherriff

Nathan W Pettus

Mark J Nixon

Robert Burke Havekost

Dennis L Stevenson

Neil J Peterson

Ling Zhou

Christopher J Worek

Ebtesam S Tanyous

James Henry Moore, Jr

Diego M Benavides

Gary Keith Law

Trevor Duncan Schleiss

Michael George Ott

Julian Kevin Naidoo

Stephen Gerard Hammack

Aaron C Jones

Herschel Odis Koska, Ii

Dawn M Marruchella

Tusar Nanda

Will Irwin

DeeAnn G Delguzzi

Beth Filippo

Robert M Lenich

Danny H Do

Nathan William Pettus

A web services-based communication system and technique uses an information server to facilitate the communication of process control data and analysis results between a plurality of web services coupled to a communication network. A graphical user interface coupled to the network enables users to store user profile information and configuration information in a database within the information server. The information server uses the configuration information and the profile information to control the operations of a scheduler and a router within the information server to enable users to selectively view process control information via the graphical user interface and to route process control information to appropriate ones of the web services.

Web services-based communications for use with process control systems

A process control system includes module-level attributes that may be used to control access for writing information to unit module objects and module objects. A security check process examines the module-level attributes, which may include OPERMODE and OPERLOCK attributes, the values of which determine whether information may be written to unit module objects or module objects. The values of the module-level attributes may be controlled based on whether a particular module object is being used by the process control system.

Operator lock-out in batch process control systems

Systems and methods for providing an integrated HMI application for monitoring and interacting with both batch and non-batch processes in a process plant are disclosed. A plurality of independent stand-alone software objects defining various batch process interface views are embedded within a non-batch process control interface application. A blackboard service is provided for storing batch control data used by the various stand alone software objects. The blackboard service may be adapted to communicate with a batch control server to receive batch control data for populating the various batch interface views with data relating to various batch processes being carried out in the process plant and to send instructions for controlling the various batches input by users via the various batch interface views. When executed by a processor, the stand alone software objects defining the various batch interface views read data from and write data to the blackboard service to communicate data between batch process interface views and preserve contextual information between interface views to allow efficient and intuitive navigation between batch process interface views.

Complete integration of stand-alone batch operator interface capabilities into generic human machine interface using componentized objects

A method and system for equipment arbitration in a process control system are presented. The method and system include receiving a request for a first resource associated with a first area from a first resource user associated with a second area where the first and second areas are distinct. The method and system automatically determine whether the first resource is available for use by the first resource user.

Method and system for batch process arbitration in a process control system

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 batch operator interfaces used to set up batch runs, a master process equipment model reflecting the current state of the equipment 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. Each of the created batch processes includes batch logic that implements the batch run specified by the user, a copy of the process plant equipment model used to select equipment within the plant and a communication interface for communicating with controllers and other runtime equipment to implement the batch as well as for communicating with the batch execution manager.

Batch execution engine with independent batch execution processes

A configuration system for a process plant includes a routine that automatically provides an indication of the relationships between units and sub-elements of the units, such as equipment and control modules, present within a process plant to a data historian. The data historian, which may be a batch historian, stores these relationships in a configuration file or a database, collects events generated within the process plant and associates those events to the proper unit within the process plant using the stored relationships. The automatic updating of the data historian configuration file eliminates the need for a user to manually update the data historian with these relationships, either at the time the process plant is configured or each time a change is made to the configuration of the process plant.

Automatic linkage of process event data to a data historian

A software object approval system is integrated with a process control or safety system environment and, in particular, with a process control or safety system design environment to implement and manage electronic approval of new software objects created within the process control and safety system environment. The software object approval system electronically generates identification information representing a group of entities whose approval is needed prior to implementing a software object within the process control or safety system. The system may then send the software object to the entities and receive from each entity an electronic indication regarding approval of the software object. The approval system prevents the process control or safety system from implementing the software object until each entity within the group of entities approves the software object.

Integrated electronic signatures for approval of process control and safety system software objects

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.

Function-based process control verification and security in a process control system

A campaign management technique for batch processes enables a process control system user to flexibly create, edit and execute batch process campaigns. The campaign management technique uses a campaign management function that sends messages requesting batch information to a batch executive function. The batch executive function extracts the requested batch information from a database and sends responsive messages containing the requested batch information to the campaign management function. The campaign management function displays the requested batch information to a user via a graphical display and enables the user to select batch information to be included within a batch process campaign. The user can create a campaign having multiple types of batches, which can include special startup and cleanup batches. The campaign management function releases batches of a campaign for execution by the batch executive function according to a user-specified batch execution mode, which may queue a ready batch in the batch executive function prior to the completion of a currently executing batch. A user can add batches to a campaign and/or can modify or delete unreleased batches of a currently executing campaign. Additionally, the campaign management function is tightly integrated with a data historian function and a security function and automatically sends campaign execution messages to the data historian and uses the security function to control user access to the campaign management function.

Campaign management for batch processes

A software object authorization system includes the ability to select signers who must approve a software object before it is downloaded to a process control system. The signers are presented with a form allowing them to authenticate their identity with a username and a password. Signers that have authenticated their identity may approve or reject the software object. A software object is authorized when all approvals needed for that software object have been received. Authorized software objects may then be downloaded to the process control system.

Integrated electronic signatures for approval of process control system software objects

A hierarchical failure management technique uses an integrated equipment hierarchy to automatically pass failure information from control modules to unit modules. Each control module collects failure information and generates a composite failure code by mathematically combining the failure information collected by that module. Modules which are currently needed by a phase of the unit module to carry out a process automatically send respective failure codes to the unit module. The unit module selects the worst failure code from a list of failure codes within the unit module and compares the selected worst failure code to a predetermined threshold value to determine whether the process should continue.

Hierarchical failure management for process control systems

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.

Use of remote soft phases in a process control system

A process control system includes a controller that executes a control routine which performs a series of unit procedures within a process. The control routine is written or created to specify the class of unit to be used for each unit procedure, but not the actual unit itself. At the start of each unit procedure of the control routine, a dynamic unit selection routine selects a particular unit as the unit to be used during operation of that unit procedure. When called, the dynamic unit selection routine determines a set of possible units to be used, determines if each of the set of possible units is suitable for use during that unit procedure of the control routine based on a suitability criterion, prioritizes the units that meet the suitability criterion based on a priority criterion and selects the particular unit from the prioritized list of suitable units in order of priority. The dynamic unit selection routine may determine if one or more of the units on the prioritized list of suitable units is capable of being acquired and may select the first unit on the prioritized list of suitable units that is capable of being acquired as the unit to be used by the control routine.

Growing community of inventors

Austin, TX, United States of America

David L Deitz