Abstract: A system and method for managing function blocks within a process control system for a process plant includes accessing an initial cause and effect matrix (CEM) having a set of causes and a set of effects. The system and method may then define a set of related groups within the initial CEM including: (i) accessing a set of rules associated with the set of related groups, (ii) identifying a portion of the set of causes that are related to a portion of the set of effects according to the set of rules and based on at least a portion of the corresponding cause-effect pairs, and (iii) rearranging the portion of the set of causes and the portion of the set of effects such that the portion of the corresponding cause-effect pairs are rearranged.

Abstract: Disclosed herein are techniques for automatically distributing device identification amongst components of a process control loop in a process plant while the loop is communicatively disconnected from the plant's back-end environment or control room. A field device's identification is stored in a memory of a component of the loop (which may be the field device or a proxy) and is used for commissioning the field device. While the loop remains disconnected, the field device's identification is distributed to the memory of another component of the loop and used for commissioning a portion of the loop including the field device and the another component. Additional distribution to other components for commissioning other loop portions is possible. Distribution may be triggered by the completion of certain commissioning activities, the establishment of communicative connections between components, and/or other conditions.

Abstract: An I/O-abstracted configuration is defined for a field device that has not yet been assigned or allocated to communicate via a particular I/O device or I/O network within a plant, and this configuration is stored in a device placeholder object in a back-end environment of the plant. Thereafter other objects, modules, applications, user interfaces, etc., that are to execute in the back-end environment of the plant to communicate with the field device during on-line operation of the plant may be designed, built, configured, and tested using the device placeholder object without any actual communications with the field device and without assigning the device placeholder object to a particular I/O channel or I/O network.

Abstract: A system tag identifying a device of a process control loop is determined/derived from a unique identifier of the device while the loop is communicatively disconnected from a process plant's back-end environment or control room. The system tag may be stored at the device itself or at a proxy that is disposed in the field of the process plant (e.g., at another component of the loop). One or more commissioning activities that include the device are performed in the field using the device's system tag, and at least some of the field commissioning activities may be automatically triggered based on the derivation of system tag. Upon the loop being communicatively connected to the back-end environment of the plant, the device's system tag known to the loop in the field is synchronized with the device's system tag known to the back-end of the process plant.

Abstract: During commissioning activities of a process plant, a device placeholder object that stores an I/O-abstracted configuration of a particular field device within the plant is created and stored in a device in the back-end environment of the plant and a further configuration file is stored in or for the particular field device in the field equipment environment of the plant. The device placeholder object, which will eventually be associated with the particular field device, and the field device configuration file are used to perform separate commissioning activities in each of these plant environments before the field devices are configured to communicate with a process controller via a particular I/O network within the plant. Thereafter, a binding application performs a discovery process to detect the I/O communication path through which each field device is connected to the back-end environment.

Abstract: An I/O-abstracted configuration is defined for a field device that has not yet been assigned or allocated to communicate via a particular I/O device, and the field device (and optionally portions of the process control loop of which the field device is a part) is commissioned based on contents of its I/O-abstracted configuration. The field device's I/O-abstracted configuration is stored in an instance of a device placeholder object, which may be common to multiple types of devices and multiple types of I/O. A property of the device placeholder object may be exposed based on the value entered for another property, and the device placeholder object may store abstracted values as well as explicit or discrete values that are descriptive of the field device and its behavior. Upon I/O-assignment or allocation, values held in the device's I/O-abstracted configuration may be transferred to or otherwise synchronized with the device's as-built configuration.

Abstract: Techniques for automatically testing an entire process control loop, such as after components and portions of the loop have been commissioned separately, or after run-time operation begins, enable the process control loop to be tested without an operator in a back-end environment of a process plant coordinating with an operator in a field environment of the process plant to supply inputs and/or generate various conditions at the loop. Instead, a single operator performs a single operation to initiate an automatic loop test, or in some implementations, no user input is needed to initiate and/or perform the automatic loop test. Automatic loop testing includes automatically causing a field device to operate in a plurality of test states and determining whether resultant loop behaviors are expected behaviors. Multiple loops may be tested concurrently or distinct in time. An automatic loop test result is generated and may be presented via a user interface.

Abstract: An apparatus for terminating a controlled-impedance cable that employs compliant contact assemblies permanently attached to the cable signal conductors and, optionally, to the cable ground shield to provide a compliant interface between the cable and another electrical device. An anchor block has signal and ground through apertures to hold the signal and ground contacts that are permanently attached to the signal conductor and shield, either directly or by using a coupler. In one form, the coupler is a rectangular sheet that is crimped onto the signal conductor. In another form, the coupling has a generally S shape. The signal conductor extends through a hole at an angle and is captured. The contact is permanently attached to the coupling to form the contact assembly. For a twinaxial cable, two couplings are attached to the signal conductors and two more bridged couplings are attached to the two drain wires.

Abstract: A system and method for enabling access to information included in a safety requirement specification (SRS) for a process plant, the process plant controlled by a process control system including displaying, in a user interface, a cause and effect matrix (CEM) having a set of elements including a set of causes and a set of effects, wherein each of the set of causes represents a condition within the process plant and each of the set of effects represents an effect to be performed within the process plant, and wherein at least some of the set of causes and the set of effects are related as cause-effect pairs whereby the corresponding effect activates in response to an occurrence of the corresponding condition.

Abstract: A system and method for managing function blocks within a process control system for a process plant includes accessing an initial cause and effect matrix (CEM) having a set of causes and a set of effects. The system and method may then define a set of related groups within the initial CEM including: (i) accessing a set of rules associated with the set of related groups, (ii) identifying a portion of the set of causes that are related to a portion of the set of effects according to the set of rules and based on at least a portion of the corresponding cause-effect pairs, and (iii) rearranging the portion of the set of causes and the portion of the set of effects such that the portion of the corresponding cause-effect pairs are rearranged.

Abstract: A connector assembly for terminating cables to a PCB. An interface of compliant contacts within in a cylindrical disk of dielectric material and a boss with the cable attached reciprocate within a cylindrical sleeve with the interface toward the PCB. Springs bias the interface and boss toward the PCB. The sleeve, interface, boss/cable assembly, and springs are slid into a barrel that has a pair of pawls extending paraxially from the proximal end. The pawls combine with paraxial alignment fingers on the sleeve. In the unattached position, the circular alignment posts fit into round PCB holes. As the connector is pushed toward the PC, the sleeve contacts the PCB and stops, but the barrel continues until it is free to rotate to an attached position where the pawl fingers slide under the PCB. An optional locking mechanism locks the barrel in the attached position.

Abstract: During commissioning activities of a process plant, a device placeholder object that stores an I/O-abstracted configuration of a particular field device within the plant is created and stored in a device in the back-end environment of the plant and a further configuration file is stored in or for the particular field device in the field equipment environment of the plant. The device placeholder object, which will eventually be associated with the particular field device, and the field device configuration file are used to perform separate commissioning activities in each of these plant environments before the field devices are configured to communicate with a process controller via a particular I/O network within the plant. Thereafter, a binding application performs a discovery process to detect the I/O communication path through which each field device is connected to the back-end environment.

Abstract: An I/O-abstracted configuration is defined for a field device that has not yet been assigned or allocated to communicate via a particular I/O device, and the field device (and optionally portions of the process control loop of which the field device is a part) is commissioned based on contents of its I/O-abstracted configuration. The field device's I/O-abstracted configuration is stored in an instance of a device placeholder object, which may be common to multiple types of devices and multiple types of I/O. A property of the device placeholder object may be exposed based on the value entered for another property, and the device placeholder object may store abstracted values as well as explicit or discrete values that are descriptive of the field device and its behavior. Upon I/O-assignment or allocation, values held in the device's I/O-abstracted configuration may be transferred to or otherwise synchronized with the device's as-built configuration.

Abstract: An I/O-abstracted configuration is defined for a field device that has not yet been assigned or allocated to communicate via a particular I/O device or I/O network within a plant, and this configuration is stored in a device placeholder object in a back-end environment of the plant. Thereafter other objects, modules, applications, user interfaces, etc., that are to execute in the back-end environment of the plant to communicate with the field device during on-line operation of the plant may be designed, built, configured, and tested using the device placeholder object without any actual communications with the field device and without assigning the device placeholder object to a particular I/O channel or I/O network.

Abstract: A system tag identifying a device of a process control loop is determined/derived from a unique identifier of the device while the loop is communicatively disconnected from a process plant's back-end environment or control room. The system tag may be stored at the device itself or at a proxy that is disposed in the field of the process plant (e.g., at another component of the loop). One or more commissioning activities that include the device are performed in the field using the device's system tag, and at least some of the field commissioning activities may be automatically triggered based on the derivation of system tag. Upon the loop being communicatively connected to the back-end environment of the plant, the device's system tag known to the loop in the field is synchronized with the device's system tag known to the back-end of the process plant.

Abstract: Techniques for automatically testing an entire process control loop, such as after components and portions of the loop have been commissioned separately, or after run-time operation begins, enable the process control loop to be tested without an operator in a back-end environment of a process plant coordinating with an operator in a field environment of the process plant to supply inputs and/or generate various conditions at the loop. Instead, a single operator performs a single operation to initiate an automatic loop test, or in some implementations, no user input is needed to initiate and/or perform the automatic loop test. Automatic loop testing includes automatically causing a field device to operate in a plurality of test states and determining whether resultant loop behaviors are expected behaviors. Multiple loops may be tested concurrently or distinct in time. An automatic loop test result is generated and may be presented via a user interface.

Abstract: An apparatus for terminating a controlled-impedance cable using compliant electrical contacts to provide an interface to another device. The terminator includes a conductive ground block for securing the cable by its ground shield and providing a common ground. Once the cable is anchored in the ground block, the block face and cable ends are dressed to make a reliable electrical contact with the compliant signal contact that electrically connects the cable center conductor to the device. An insulating or conductive plate mounted to the ground block holds the signal contact and optional ground contacts that electrically connect the ground block to the ground plane of the device. The ground contacts surround the signal contact in a pattern that closely mimics the impedance environment of the cable. When using a conductive plate, the signal contact is insulated from the plate by an insulating centering plug or a non-conductive coating.

Abstract: An apparatus for terminating a controlled-impedance cable using compliant electrical contacts to provide an interface to another device. The terminator includes an anchor block for securing the cable. Optionally, the anchor block is electrically non-conductive. A conductive ferrule is installed on the cable shield and the cable end is dressed. The ferrule/cable assembly is installed in a through hole in the anchor block so the cable end is flush with the anchor block face. An insulating or conductive plate mounted to the anchor block holds the signal contact that electrically connects the center conductor to the device and optional ground contacts that electrically connect the ferrule to the device. The ground contacts surround the signal contact in a pattern that closely mimics the impedance environment of the cable. When using a conductive plate, the signal contact is insulated from the plate by an insulating centering plug or a non-conductive coating.

Abstract: An apparatus for terminating a controlled-impedance cable using compliant electrical contacts to provide an interface to another device. The terminator includes a conductive ground block for securing the cable by its ground shield and providing a common ground. Once the cable is anchored in the ground block, the block face and cable ends are dressed to make a reliable electrical contact with the compliant signal contact that electrically connects the cable center conductor to the device. An insulating or conductive plate mounted to the ground block holds the signal contact and optional ground contacts that electrically connect the ground block to the ground plane of the device. The ground contacts surround the signal contact in a pattern that closely mimics the impedance environment of the cable. When using a conductive plate, the signal contact is insulated from the plate by an insulating centering plug or a non-conductive coating.

Abstract: An apparatus for terminating a controlled-impedance cable using compliant electrical contacts to provide an interface to another device. The terminator includes an anchor block for securing the cable. Optionally, the anchor block is electrically non-conductive. A conductive ferrule is installed on the cable shield and the cable end is dressed. The ferrule/cable assembly is installed in a through hole in the anchor block so the cable end is flush with the anchor block face. An insulating or conductive plate mounted to the anchor block holds the signal contact that electrically connects the center conductor to the device and optional ground contacts that electrically connect the ferrule to the device. The ground contacts surround the signal contact in a pattern that closely mimics the impedance environment of the cable. When using a conductive plate, the signal contact is insulated from the plate by an insulating centering plug or a non-conductive coating.