Deliverable 4: Summary of SME Meeting Minutes

Up one level to Workflow Documentation

Up two levels to Project Findings


Software Application Variations

Table 2. Software tools used in JVPR operations.

The use cases we documented utilized a large number of software application, services and systems. The software included both corporate in-house custom software and off-the shelf commercial software. These systems are integrated to varying degrees to support the workflows around JVPR.

• Field data capture and field operations management software
• SCADA, human-machine-interface and historian software for automation and real-time data
• Artificial lift and ESP monitoring and optimization software
• Maintenance management software
• Reservoir and well surveillance software
• Hydrocarbon production allocation and accounting software
• Hydrocarbon production economics and forecasting software
• Well and production data services
• Non-operated data management software
• Production data transfer and data modeling standards utilizing XML,EDI and database
• Enterprise resource management (ERP) and financial accounting software
• Regulatory reporting and compliance software
• JIB billing and technical data exchange software and services
• Land and rights management software
• Reservoir, geophysical ad technical data management software
• Reservoir modeling and simulation software
• Reserves management and reporting software
• Data analytics and visualization software
• Drilling and wellbore data management software
• Portal, reporting and dashboard software

Lack of Data Format Interoperability and PRODML Standards

Data format interoperability is one of the main complaints that have been raised by the SMEs during meetings on JVR. From each side’s perspective (Partner, Operator, or the customer) there is a need for unification of data formats across all reports.

Joint venture reporting is an ongoing work in the Energistics PRODML Special Interest Group, where the PRODML (Production Markup Language) Standards are being developed and supported. The PRODML Standards define a uniform, formal specification for the representation of production reports. As outlined in PRODML Version 1.0 and 1.1 documentation, The Product Volume Report data object specification is used to define, for example, the daily volume of oil production at each wellhead in a general hierarchy of:

  • Report
    • Facility (wellhead, separator, flowline, choke, completion, etc.)
      • Parameter Set (block valve status, reciprocating speed, available room, etc.)
        • Parameter
      • Flow (production, injection, export, import, gas lift, etc.)
        • Product (oil, water, gas, CO2, oil-gas, cuttings, etc.)
          • Period (instant, day, month, year, year-to-date, month-to-date, etc.)
            • temperature
            • pressure,
            • flow rate
            • etc.

The PRODML Special Interest Group welcomes advice in the form of new use case and industry requirements, including those for JVR needs.

PRODML Standards are compatible with other Energistics Standards, including the WITSML (Well Site Information Transfer Standard Markup Language) Standards that address transferring drilling information and RESQML (Reservoir Characterization Markup Language) that addresses transferring earth models and reservoir models. All of these families of standards define both data object schemas and web services interface specifications (also known as the application program interface (API)).


The content of information obtained through SME meetings was analyzed using affinity diagrams. Affinity diagrams organize a large number of ideas into their natural relationships and display this information in hierarchy. Currently, Figure 27 depicts the following elements from SME meetings:

1) Partner roles:
2) Data transfer;
3) Reports;
4) Reconciliation;
5) Revenue Accountant;
6) Joint Interest Billing (JIB);
7) Operator Roles;
8) Production Accounting;
9) Well Test;
10) Software Used;
11) Issues;
12) SME Suggestions.

Each element is composed of the corresponding information gathered from the SMEs. Subheadings have been included to clarify the SME’s contributions to each element. For example, Partner Roles can be divided into two categories, “data monitoring and analysis” related, and “other roles.” SME content is marked with a dark background whenever the content is not within the scope of this project. The numbers in parenthesis inside each box (where SME content is displayed) indicate the interview number from Appendix B of this report.

Figure 19a. Partner roles
Figure 19b. Data transfer
Figure 19c. Reports
Figure 19d. Reconciliation
Figure 19e. Revenue Accountant
Figure 19f. Joint Interest Billing (JIB)
Figure 19g. Operator Roles
Figure 19h. Production Accounting
Figure 19i. Well Test
Figure 19j. Software Used
Figure 19k. Issues
Figure 19l. SME Suggestions

Up one level to Workflow Documentation

Up two levels to Project Findings

Next section to: Analysis of Issues - Recommendations and Potential Solutions

Add a New Comment
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License