Well Test Device Logic Building Blocks

The CygNet Well Test Module employs the following logic building blocks. These are used to mimic the field workflow for putting wells into test mode and generating a well test record. A sequence is created using these blocks and must be stored in the XML configuration in the PNT.

See the following subsections for more information:

• UIS Command
• Set Point
• Exit
• Test
• Point Value Compare
• Script
• Monitor

UIS Command

The CygNet Well Test Module uses the UisCommand action type to send a UIS Command to a configured device. This action:

• issues standard UIS commands to a configured device, including:
  • sets the valve to the correct position
  • polls the device
• uses supplied service, facility ID, command, parameters, and optional status point
• offers a flexible parameter building model
• is relative-facility aware

For more information see the UIS Command action type for the well test configuration control or the UisCommand action type for XML configuration details.

Set Point

The CygNet Well Test Module uses the SetPoint action type to issue a SetPoint to a CygNet point. This action:

• issues the standard setpoint command to a point
• uses tag and value
• includes status update
• is relative-facility aware

For more information see the Set Point action type for the well test configuration control or the SetPoint action type for XML configuration details.

Exit

The CygNet Well Test Module uses the Exit action type to stop the current well in test mode. This action:

• stops/exits the current well in test
• has optional SetPoint capability

For more information see the Exit action type for the well test configuration control or the Exit action type for XML configuration details.

Test

The CygNet Well Test Module uses the Test action type to halt the process until the well test time has elapsed before processing the well test record. This action:

• employs a necessary wait operation to halt the process until the well test time has elapsed
• is used in host-based configurations
• is used for time-based operations such as purge or well test
• offers optional point-based wait time
• offers optional condition-based exit
• is relative-facility aware

For more information see the Test action type for the well test configuration control or the Test action type for XML configuration details.

Point Value Compare

The CygNet Well Test Module uses the PointValueCompare action type to compare two values and perform an action, if true. This action:

• evaluates an expression with two parts, compares two value positions and performs an action, if true
• provides two courses of action
• includes support for hard-coded values
• includes support for point value look-up
• is relative-facility aware

For more information see the Point Value Compare action type for the well test configuration control or the PointValueCompare action type for XML configuration details.

Script

The CygNet Well Test Module uses the Script action type to define and run a specified VB script that will process well test data and produce the values needed for the well test record. This action:

• uses a customized script to process well test record values
• stores the values needed for the well test record
• a stock script is supplied if no computation is required
• offers BSS and local file system support

For more information see the Script action type for the well test configuration control or the Script action type for XML configuration details.

Monitor

The CygNet Well Test Module uses the Monitor action type to monitor the device and take action when certain conditions occur. This action:

• is used for device-based (PLC) mode configurations
• offers configuration of multiple condition/action pairs:
  • defines a condition to evaluate
  • specifies actions to take when conditions are met
• offers optional sleep timer and time out actions

For more information see the Monitor action type for the well test configuration control or the Monitor action type for XML configuration details.