Petroleum Production Reporting System 2000

PPRS IT Requirements

Petroleum Production Reporting System 2000

September 2016

P. Harrison | First published Aug 2000 | Last updated Sep 2016 1

© Crown copyright 2016

You may re-use this information (not including logos) free of charge in any format or medium, under theterms of the Open Government Licence.

To view this licence, visit
or write to the Information Policy Team,The National Archives, Kew, London TW9 4DU,
or email: .

Any enquiries regarding this publication should be sent to phil.harrison@

P. Harrison | First published Aug 2000 | Last updated Sep 2016 1

Contents

Data Submission

1Background

1.1Tables 1 – 6

1.2Data File Formats

1.3Combined Units

1.4Validation Rules

1.5DTD Files

2Guide to DTD and XML Definitions

3Completeness of Data and Timing of Submission to the OGA

3.1Timing

3.2XML reporting

3.3Submission Methods

Table A - Field Returns – Data Specification

Table B - Terminal Returns – Data Specification

Table C - Validation Rules

P. Harrison | First published Aug 2000 | Last updated Sep 2016 1

Data Submission

1Background

1.1Tables 1 – 6

These tables provide the Company Production Engineer with an overview of the physical data required by the OGA each month. However, these are not sufficient to define exchange file structures and data types or the Validation Rules with which data must comply.

1.2Data File Formats

The format of data files to be sent to the OGA is based on an Internet compliant standard called XML, (Extensible Mark up Language), which defines a method of exchanging structured data. The structure of an XML file is defined by another file called a Document Type Definition or DTD for short. The XML file includes actual data reported and the DTD defines the structure of the data expected. Each monthly PPRS return for a Reporting Unit must be sent to the OGA as a single XML text file and this must comply with a DTD given in this document.

1.3Combined Units

For IT purposes, Tables 1-3 for Field Reporting Units have therefore been combined into one table in this Annex (Table “A” Field Returns – Data Specifications) which shows the additional information defining data types and Validation Rules. Tables 4-6 for Terminal Reporting Units have been combined into a similar table (Table “B” – Terminal Returns – Data Specifications) which shows the additional information defining data types and Validation Rules.

1.4Validation Rules

Validation Rules are listed in Table C and must be complied with when submitting data. The structure expected for a field return is defined in the DTDs and these can be found on the OGA website.

1.5DTD Files

The DTDs and a comprehensive selection of sample XML files are available for downloading from the Web site. Further information on XML is available on ( The Web site covers issues such as,

• How to report repeating groups with no data
• How to report PARTIAL returns
• How to report FULL returns
• How to report a zero return

2Guide to DTD and XML Definitions

Entries in Tables “A” and “B” have been used to name the data tags within the DTD files and the XML files. Data nametags used in the DTD can be classified into the following types:

• Overall Return Tag has value ‘PPRS_RETURN’ used to tag the return as a whole
• Data Group Name tags used to tag a list of other Data Groups or Individual Data Items
• Data Group Name tags used to tag a Repeating Data Group
• Note. All data tags and any other character data within are in UPPER CASE.
• Individual Data Item tags – used to tag actual data to be reported

The tag names used in the DTD files are based on the Data/Stream Descriptions and Data Items given in Tables A and B as follows:

• if the Data/Stream Description is not a repeating group but has more than one Data Item associated with it, the Data Group Name tag used in the DTD is the same as the Data/ Stream Description. However, the spaces are replaced by underscores (e.g., Oil Production becomes tag OIL_PRODUCTION). Individual Data Item tags referenced by this group are the same as the corresponding Data Item names in Tables A and B, but again with spaces replaced by underscores. So for Oil Production the DTD syntax is:

<!ELEMENT OIL_PRODUCTION (OIL_PRODUCTION_VOLUME, OIL_PRODUCTION_DENSITY)>

<!ELEMENT OIL_PRODUCTION_VOLUME (#PCDATA)>

<!ELEMENT OIL_PRODUCTION_DENSITY (#PCDATA)>

• if the Data/Stream Description is a repeating group then the Repeating Data Group tag is the Data/Stream Description, with spaces replaced by underscores, followed by the text ‘_REPEATING_GROUP’. (E.g. Inter Field Transfer of Oil becomes INTER_FIELD_TRANSFER_OF_OIL_REPEATING_GROUP). This is then followed in brackets by the Data/ Stream Name, again with spaces replaced by underscores, and an asterisk to indicate repetition. Thus for Inter Field Transfer of Oil the entry in the DTD is,
  <!ELEMENT INTERFIELD_TRANSFER_OF_OIL_REPEATING_GROUP (INTER_FIELD_TRANSFER_OF_OIL*)> followed by the DTD definition of the group INTER_FIELD_TRANSFER_OF_OIL

• if the Data/Stream Description refers to only one Data Item (e.g. Produced Water refers to Produced Water Volume), then the tag used in the DTD is the Data Item name with spaces replaced by underscores (e.g. PRODUCED_WATER_VOLUME)

3Completeness of Data and Timing of Submission to the OGA

3.1Timing

All PPRS returns for a given month’s production must arrive at the OGA by the 30th day of the following month. Some return types are expected to report some data earlier by the 16th of the month. Data required by the 16th of the month and that required on the 30th are identified in Tables 1 - 6. These early returns by the 16th are known as “PARTIAL” returns and can report only selected data items leaving the rest blank. The returns by the 30th are known as “FULL” and must report the data expected including that sent earlier.
Any additional data sent in a PARTIAL return but not required as early data may be ignored by the OGA because it is still expected in a FULL return. The FULL return received by the OGA will overwrite the PARTIAL data. A Company may send a FULL return at any time before the 30th of the month, there is no requirement to wait. The DTD defines a “RETURN_COMPLETENESS” tag that may have values ‘FULL’ or ‘PARTIAL’. The XML file to be sent must include this and identifies whether it is a FULL or PARTIAL return.

3.2XML reporting

The appropriate monthly XML file should be created separately for each individual Reporting Unit and contain the relevant monthly data. The XML file should be e-mailed as a text attachment to the following e-mail address:

3.3Submission Methods

Current Method.

Via email as a plain text attachment. It is envisaged that many of the larger companies with automated production allocation systems will prefer this method as it can be made fully automated. On receipt at the OGA, the attachment will be removed and processed – with success or failure resulting in an email acknowledgement being returned to a nominated list of company email addressees. If errors are encountered, the file will be returned via e-mail to correct and re-submit as a new XML file. The emphasis is on the Operators’ internal QC procedures to get the files in a format to load directly onto the OGA computers.

Future plans.

“Upload File” via the Energy Portal Website. This will provide an instantaneous Validation and loading. Any errors will be reported at the time of the operation.

Table A - Field Returns –Data Specification

Reporting Unit Types Data Types

P – Oil Field Exporting to PipelineCharacter (x) = UPPER CASE ALPHANUMERIC not longer than (x) characters

T – Onshore Oil Field or Offshore Tanker LoaderNumber (x) = Number with no more than (x) decimal places

G - Dry Gas FieldInteger = whole number, no decimal point

Table B -Terminal Returns – Data Specification

Reporting Unit Types Data Types

P – Oil Field Exporting to PipelineCharacter (x) = UPPER CASE ALPHANUMERIC not longer than (x) characters

T – Onshore Oil Field or Offshore Tanker LoaderNumber (x) = Number with no more than (x) decimal places

G - Dry Gas FieldInteger = whole number, no decimal point

Table C - Validation Rules

When constructing a PPRS XML file, all tags defined in the relevant DTD must be included. This is even if reported data within the tags is blank or zero, with the exception of repeating data groups that are explained below in Rule 30. This applies to both ‘FULL’ returns and ‘PARTIAL’ returns. Tables A and B indicate which data items must be reported and which rules apply. If a data item is not required, report a blank or zero value within the XML tags.

© Crown copyright 2016