Page Contents:

Other Pages:

There are many operators in most countries, most operators operate in multiple countries, and different reports may be required by separate agencies within each country. Most agencies require multiple reports from each operator. These reporting activities are mandated by local laws and contracts which each specify unique data content, format and deadlines. Within at least one country, the United States, each state has established distinct, multiple reporting requirements. Further, even the simplest code values (i.e., status) and commonly understood concepts (i.e., location) are locally defined.

A distinct information flow is defined for each operator-regulator pair, and these flows can involve multiple exchanges - such as initial filings, deficiency requests, corrections and acceptance notifications. Each exchange may require an authentication protocol, such as an authorized signature or notification of receipt. Some exchanges may be conducted by email and spreadsheet, others by EDI, while many still require paper documents.

There is a common set of concepts present in many of these exchanges - namely basic production, injection, sales and disposal statistics. These data are consistently found in regulatory reports at the levels of wells, platforms, terminals and/or licenses. These data are provided at both significant events (e.g., new well completions) and on a schedule (e.g., monthly and annual reporting).

POSC recognizes that the operator-agency information exchange is only one of several that deal with this set of data - other important exchanges occur from agency to vendor, agency to agency, vendor to operator, operator to operator, etc. The requirements for these exchanges overlap with operator-agency data, and specifications for these exchanges must be consistent and compatible.

Obviously, this is an area where useful standards will provide significant benefits to operators and regulators alike. POSC's vision is to apply emerging 'structured data' technology, such as XML, to this widespread problem for the benefit of the E&P industry. POSC will not deliver a 'one size fits all' specification, however, as it is inconceivable that regulatory agencies would agree upon a standard information specification or that industry could arrange simultaneous, worldwide implementation.

This project works toward a basic XML specification for operator-agency segment of the production reporting problem. This specification is not intended to be adopted per se, but rather this specification is intended to be the base from which local, customized specifications can be defined as necessary.

• homonyms - resolving two concepts that have the same 'name' but are in fact different
• synonyms -  consolidating conflicts when the same concept is known by two or more 'names'
• codes - compiling, consolidating and resolving lists of standard values so that codes may be used consistently and correctly
• structures - establishing the rules by which one concept is dependent upon other concepts
• identifiers - creating rules for the identification of a concept, and promulgating standard identifiers and identification schemes

POSC is uniquely situated as an industry supported, vendor neutral organization with worldwide influence. In addition, POSC is uniquely qualified to initiate and conduct this type of project. These qualifications include:

• a decade of experience in E&P standards
• a history of successful industry collaborative efforts
• the demonstrated ability in delivering XML-based specifications and systems

• The general deliverables will be the base XML specification, additional supporting technologies and the supporting documentation. The supporting technologies would include the necessary components to implement the basic deliverables as designed in this project.
• One or more specific efforts will be conducted to create specific implementations based upon the customized needs of the participants. The participants in these specific efforts should include at least one regulatory agency, one operator and an implementation vendor. Each effort will provide detailed, specialized feedback to the project to ensure that the general deliverables will support their customizations.

• a base XML specification (DTD or XML Schema)
• the documentation for the base XML specification
• a sample XML data file covering all data items
• an XSLT providing web-based XML file creation capabilities
• an XSLT providing hardcopy representation of the base XML file
• a data utility to load ProductionML/Reporting files into Epicentre

The deliverables of the specific efforts and their availability will be determined by the participants in each effort. These deliverables should include a description of the customizations (modifications and extensions) to the base XML specification as well as a mapping to it. At least this information should be provided back to the general project.

It is our goal to determine if sufficient interest for this project exists within industry before starting it. Once interest has been verified, a project plan will be distributed to interested parties prior to an open meeting to formally establish this project.

If you are interested in participating, or would like further information, contact John Bobbitt by email (bobbitt@posc.org) or by phone (+1.713.267.5174).