Processing and Storing Well Test Results

Once the well test action sequence completes, the well test contents must be generated. Since the values for the well test record can come from various locations due to the unique configurations at the field-level, a programmable approach in the form of a VBScript is required. After the test is complete, a Script action is necessary to process the results.

The path to the script file is configured in the Script action type in the well test configuration XML. A sample script is provided to illustrate the concept of processing supplied arguments and providing the necessary output that the CygNet Well Test module expects in order to process a well test record. The sample VBScript will need to be customized for the user's specific environment.

See Sample Well Test Screens and Scripts for more information.

About Well Test Dates

The CygNet Well Test module uses the same timestamp for the date and time of the actual well test supplied within the well test record (retrieved via script) and the date and time when the well test record is posted to the VHS (the VHS entry date). To avoid confusion the date provided in the well test record is the same as the entry date in the VHS. See Timestamps for more information about CygNet timestamps.

Script File Tokens

The VBScript referenced in the Script action type must output the well test values. The script action is expecting the well test variables to be returned in a specific way.

Single Well Test Record

There are seven (7) reserved token names that can be used to specify the value for a given process variable. For single well test records, the script tokens need to output in the following format:

Historical Well Test Record

The historical well test record needs to indicate the type of output, so it will start with the %HISTORICAL% token. The start of each record will start with the %RECORD% token. The tokens and value used for an individual record are similar to those used for the single well test record format. The main difference is that historical records will not have a %FACILITYTAG% token, but they will have a %POSITION% token instead. The %POSITION% token and its subsequent value are used to lookup the facility tag. The position that is defined in the Header section of the well test configuration XML is the same position value used in the lookup. Typically, a device isn’t going to know the facility tag. It typically only knows of the position it is are currently on. So, the %POSITION% token is used to figure out the well facility tag to post the well test result to.

For historical records, the script tokens need to output in the following format:

Script Processing

The oil, water, and gas values come from the separator facility, which is specified in the Tag property on the Headers page of the well test configuration control ('tag' attribute of the <Header> element of the XML configuration). The duration, facility tag, and timestamp values come from the Well facility, which is specified in the Tag property on the Wells section of the well test configuration control ('tag' attribute of the <Well> element). All values are concatenated and passed into the script. The generic script then turns around and passes those same values back out in the appropriate format. From there, the XML record gets generated and posted to the VHS as a Blob string.

Script Engine Process and VHS Blob Storage

Well test records are stored as XML strings in VHS entries for each configured well. The module will pass out the tokens and the values, and generate an XML string and publish it to the "Result" UDC specified in the UDC configuration on the General page of the well test configuration control (or if configured, the override UDC specified in the Script action type).

The Microsoft script engine exits after it has executed a user-provided VBScript file, waiting at most 10 seconds to exit. The Well Test results are stored in VHS blobs in the following manner:

• Retrieve the Well Test XML results produced by the configured VBScript file.
• Extract only the %DATETIME% value from the results.
• Look for the point with the configured UDC (e.g., "WELLTEST") in its associated CVS (UIS, HSS, etc.).
  • If not there, log an error and stop processing, since the point must be pre-configured in the PNT like all other CygNet Well Test points.
• Update the current value of the point in the CVS, setting both the value and the timestamp to the %DATETIME% value.
  • The value is in the form "YYMMddhhmmssxxxx" (e.g., 2503250805040000).
  • This is the same convention used by the method for storing a Header's PendingWellQueue and ActiveWell/ActionQueue in VHS blobs, described here.
  • If a valid %DATETIME% value cannot be extracted from the Well Test XML results, the current system time is used instead.
• Wait for that value to propagate to the VHS and, when it arrives, update the VHS blob associated with that entry.
  • The %STATUS% value is maintained within the Well Test XML results and is displayed properly in the Canvas Well Test Detail.can screen.
• If a HistoryEntry with a matching timestamp already exists, overwrite the existing VHS blob with the new Well Test XML results (the last one in wins).

Export Well Test Record

The following is a sample script procedure to export the values in the correct manner.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
'---------------------------------------------------------------------
' Standard output method
'---------------------------------------------------------------------
Sub WriteOutput(Oil, Water, Gas, Duration, Status, RecordTimeStamp)
    ConstoilToken = "%OIL%"
    ConstwaterToken = "%WATER%"
    ConstgasToken = "%GAS%"
    ConstdurationToken = "%DURATION%"
    ConststatusToken = "%STATUS%"
    ConsttimeStampToken = "%DATETIME%"
    ConstfacilityTagToken = "%FACILITYTAG%"
     
    SetobjStdOut = WScript.StdOut
    objStdOut.Write oilToken
    objStdOut.Write Oil
    objStdOut.WriteBlankLines(1)
    objStdOut.Write waterToken
    objStdOut.Write Water
    objStdOut.WriteBlankLines(1)
    objStdOut.Write gasToken
    objStdOut.Write Gas
    objStdOut.WriteBlankLines(1)
    objStdOut.Write durationToken
    objStdOut.Write Duration
    objStdOut.WriteBlankLines(1)
    objStdOut.Write statusToken
    objStdOut.Write Status
    objStdOut.WriteBlankLines(1)
    objStdOut.Write timeStampToken
    objStdOut.Write RecordTimeStamp
End Sub

Retrieving Well Test Records

Any third-party application can retrieve well test records using the CygNet.API.WellTest. See Retrieving Well Test Records for more information.