7.1.1 Use Case 1 and 2: Direct Exchange of Production Data Between Partners

Topic Version1Published12/09/2016
For StandardPRODML v2.0

Use Case 1: Receive from a partner

Use Case 2: Transmit to a partner

Use Case Name

Direct Exchange Of Production Data Between Partners




Terry Kite (Merrick)


Bill Logsdon/Ashraf Wardeh (Oxy) and William Gilmore (Accenture)


Provide production data for a fixed duration necessary for monitoring, decision-making, forecasting and reporting, and financial record-keeping associated with operated properties to others with working and/or revenue interest in those properties.

Business Requirement

Discharge contractual obligations

Assess ongoing participation in properties operated by others (OBO)

Evaluate current operations of OBO properties

Comply with financial and reporting obligations related to OBO properties

Forecast future potential of OBO properties

Business Value

Better operational insight supporting improved decision making and/or requests for operational changes

Improved estimate of future production potential (reserve estimates/reporting; marketing deliverability, etc.)

Timelier data for booking related financial transactions, governmental/financial reporting, etc.

reduce the cost and effort of both providing data and consuming data through a consistent standard (currently each company tends to have their own solutions so each party has to develop a separate solution for each partner in order to load their data

Summary Description

For producing properties that are subject to joint operating agreements, the Operating Partner is responsible for collecting operational information on those properties and determining well-level and facility-level production volumes by product (or flow stream). They are also typically responsible for providing this information to the other parties in the agreement (Non-operating Partners). The Non-operating Partner uses this data to update its own data store(s) that support making operational decisions, estimating reserves, reporting to outside parties and booking related financial transactions. Although typically transmitted on a regular on-going basis, the Non-operating Partner may from time to time request data that encompasses prior periods to verify and/or complete its own data store. Likewise, the operating partner may at times advise non-operating partners of prior period adjustments and re-issue previously transmitted data that has been amended.


Non-operating Partner; Operating Partner; non-working interest partners (e.g., royalty owners)


Agreed upon periodic schedule (daily, weekly, monthly, etc.)

Out-of-Schedule request by Non-operating partner


Non-operating Partner has a revenue and/or working interest in a producing property operated by the Operating Partner

Operating Partner has collected and verified operating data and performed necessary calculations to determine gross well-level production data.

Primary or Typical Scenario

The data is transmitted from the operating partner to interested parties (working interest partner, royalty owner, inter-departmental use, etc.) on a regular basis encompassing all new data since the previous report (note: new well or facility may include historical data. For records representing the aggregation of data over a period of time, the duration of each record is typically fixed (full day, partial day, week, month, etc.) in a report, but there can be multiple reports each consisting of different data ranges and record durations.

Alternative Scenarios

Operating Partner amends production related information previously reported to the Non-operating Partner as part of the agreed upon periodic reporting process. The Operating Partner transmits the report with all modified data, including producing period.

Non-operating partner wishes to refresh their production history on a property or properties in which they have an interest (to verify the accuracy of their data, to fill gaps in their data store, outages, etc.). They would request that the Operating Partner transmit a report over a specified date range using a specific record duration (day, week, month, etc.).

A non-operating partner that has not been tracking operating information on a well may need a one-time issue of all historical data to establish a starting point.

It may be necessary to distinguish between data exchanges which are intended to over-write old records or whether the transmission is of new data.


Non-operating Partner has data necessary to assemble a production history for the property adequate for making operational decisions, estimating reserves, reporting to outside parties and booking related financial transactions.

Business Rules


Data Requirements

Well identifier

Production date and period

Total produced volume of oil, water and gas

Injection volumes (oil, water or gas); allocated and raw

Pressures (tubing, casing, etc.)


Sales volumes (oil, gas)

Fuel volumes (gas)

Flare/Vent volumes (gas)

Downtime/Deferred Production

Hours (minimum)

Volume Deferred

Comment (minimum

Formatted reason code/description)

Start date/time

End date/time

Operations comments

Well tests (Oil/Water/Gas 24 hour rates and test date)

Last modified date/time

Overwrite/new data flag

Extended Requirements:

Well Type

Well Status

Artificial Lift History

Well Maintenance History

Facility measurement data

Measurement point identifier (NB facility identification may not be a standard)

Measurement point type (tank, meter, etc.)

Inventory (tank volumes)

Volume flowed (meters)

Fluid characteristics (temperature, pressure, density, etc.)

Pressures/temperatures (vessels/equipment)