Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Gas Contract Nominations file – Import from text file

Gas Contract Nominations file – Import from text file

  • Last UpdatedApr 24, 2025
  • 2 minute read

By default, the Gas Contract Nominations application can read data from text files placed in the %DNADataRoot%\RealTime\Temp\CustomApps\nom folder.

Each nomination file must be named to reflect the gas day and cycle for which it applies. The file name format is as follows:

  • yyyyMMdd_<Cycle>.txt .

  • yyyyMMdd – Gas date that the file needs to load.

  • yyyy – Year.

  • MM – Month (01-12).

  • dd – Day (01-31).

  • Cycle – ONT (Timely), EVE (Evening), ID1 (Intra-Day 1) and ID2 (Intra-Day 2).

For example, "20140516_EVE.txt" is the nomination input file for the evening cycle on May 16, 2014.

Note: The nom2xml.exe process only processes a file if the date matches the current date and the cycle schedule is correct.

The contents of each file are records with comma-separated values based on the following format:

Field

Description and Constraints

Point Name

Ignored by the driver, but can be used as a record description (up to 31 characters).

Point Code

A prefix is added to the point code, and the resultant string must match the AVEVA Enterprise SCADA gas contract name. The default prefix is "m".

Receipt or Delivery

R (Receipt) or D (Delivery)

Scheduled Quantity (V)

Volume (in Mmcf) (Double)

Scheduled Quantity (E)

Energy (in Dekatherm) (Double)

Cycle

ONT (Timely), EVE (Evening), ID1 (Intra-Day 1) or ID2 (Intra-Day 2)

Mnemonic for the NAESB nomination cycle for which this nomination applies.

Gas Day

Gas day for which the nomination applies. Allowable formats:

  • "yyyyMMdd"

  • "MM/dd/yyyy"

  • "M/d/yyyy"

  • "yyyy-MM-dd"

  • "yyyy-M-d"

    Notes: Quotation marks are optional.

    The date must take one of the above formats. For example, if the content of a file reads ",805084,R, 0.00,0.0,ONT,16/05/2014", the system will reject the record.

Important: The system considers leading or trailing spaces in text fields (for example, "Point Name" or "Point Code") as part of the field value.

Example

,801518,R,196.98,0.0,ONT,20140516

,801521,D,346.62,0.0,ONT,20140516

,801522,D,0.14,0.0,ONT,20140516

,805084,R,0.00,0.0,ONT,20140516

AC_NGPL-FLOW,801662,D,29.46,0.0,ONT,20140516

ANR_CUSTR-FLOW,002024,R,98.75, 0.0,ONT,20140516

ANR_DELHI-FLOW,801501,D,98.31,0.0,ONT,20140516

AOLY-FLOW,801525,D,0.00,0.0,ONT,20140516

Notes - General

  • The Gas Contract Nominations (GCN) application only uses either the volume or energy for a given record, depending on how the gas contract has been configured. Set the unused field to 0.0. In the above example, only the volume is used.

  • The default gas contract schedule is as follows:

    • Evening (EVE) 22:00

    • Intra-Day 1 (ID1) 14:00

    • Intra-Day 2 (ID2) 20:45

    • Timely (ONT) 16:30

  • As Noted previously, the default point code prefix is "m".

  • Various default settings can be modified, including the gas contract schedule and point code prefix. For further information on GCN, refer to the AVEVA Pipeline Operations for Gas Administrator documentation.

Notes - File Handling

  • If both the filename and content are valid, the application processes, and then silently deletes, the file.

  • If the filename is invalid, the application renames the file <filename>.orig.

  • If the filename is valid, the application processes the file line by line.

    • If the application does not encounter an unexpected error, but does locate some invalid records, it silently deletes the file and appends the invalid lines to <filename>.err.

    • If the application encounters an unexpected error -- such as a corrupt file -- it renames the file to <filename>.orig.