The core mission of PIDX is to improve business efficiency within the oil and gas industry by promoting interoperability between IT systems. RP3901 (an API Recommended Practice) is comprised of numerous XML Schema files that define the allowable data structures for a variety of procurement transactions that support both the upstream and downstream oil and gas sectors.

The links below provide access to the latest PIDX specification as well as previously released specifications. A recommendation issued by the business messages work group (BMWG) in early 2006 adjusted the PIDX namespace and versioning XML Schema architecture so that each release will now be referred to by the month and year of its release (e.g., ‘Feb 2006’).

3901 Publications

The PIDX RP3901 (Recommended Practice) is a specification that enables automation of various aspects of the oil and gas supply chain. The specification makes this automation possible by providing a library of XML Schema files with which trading partners can develop software systems that will be interoperable with other PIDX-enabled companies. The specification also contains documentation that describes how the specification can be used within a broader business process perspective.

• PIDX v1.0
• PIDX v1.2
• PIDX v1.3
• Feb 2006
• Sep 2007

XSDdoc

XSDdoc is an XML Schema documentation application that transforms plain XML Schema files into cross-referenced, hyperlinked HTML documents and provides a detailed functional report for each schema component. XSDdoc makes it easy to navigate through a large collection of XML vocabulary.

• PIDX v1.0
• PIDX v1.2
• PIDX v1.3
• Feb 2006

RP3901 Support Documents

Implementation Guide

The purpose of the PIDX Implementation Guideline document is to assist trading partners to implement and use the PIDX XML instance (data) documents. Each group of trading partners may have specific implementation requirements and the PIDX Implementation Guide describes a generalized process to identify those requirements and establish an agreement to meet each trading partner's business process and associated data requirements. This document supports the 3901 XML specifications with RNIF Transaction, Routing, Package (TRP) protocol and will promote increased interoperability between oil and gas IT systems and will reduce systems development cycle times.

• Implementation Guide v1.0
• Implementation Guide v2.0

AS2

In April 2005, PIDX, the Petroleum Industry Data Exchange, the American Petroleum Institute's (API) committee on Electronic Business, adopted AS2 as an additional TRP (Transaction, Routing, Package) protocol within the PIDX Recommended Practice 3901 - PIDX XML Transaction Standards. PIDX developed these standards for use in oil and gas B2B e-commerce. After significant research, it was determined that AS2 represented a secure, low-cost option for communications that would help lower the barrier to entry to e-commerce for small and medium businesses (SMB).

A significant factor in the acceptance of AS2 by PIDX and petroleum industry trading partners was the certified interoperability tested by Drummond Group. Knowing that DGI AS2 Interoperability Certified vendor products are compatible has removed a significant and costly barrier to e-commerce for SMBs. The potential lowered costs of entry, secure transport and multiple attachment handling are key functions provided by AS2 that fulfill the upstream oil and gas transaction requirements. More information on the Drummond Interoperability Certification and the vendors that support the PIDX requirements can be found here.

• AS/2 Usage Guideline v 1.2

Business Process Guidelines

Business Process Guidelines (BPGs) are intended to guide trading partners as they implement PIDX standard messages in support of business requirements. As issues are identified, Business Process Work Group members work together to define solutions and processes intended to guide the industry toward a common goal with enough flexibility to meet trading partner requirements.

• Business Process Guidelines