Business Process Work Group

1

• Business Process Work Group
• Field Ticket Project
• (Tony Aming, Michael Lanier, John Stukes and
  Laura Wang)
• January 29th, 2009

2
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process recommendation
• Next Steps
• Wrap-up

3
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process recommendation
• Next Steps
• Wrap-up

4
Anti-trust Statement

• Meeting participants should observe the following
  antitrust guidance
• No discussion of any companys confidential or
  proprietary information
• No discussion or agreements, either explicit or
  implicit, regarding prices of particular products
  or services provided by or received by a company
• No forecasting of prices for goods or services
• No discussion of any companys purchasing plans
  for particular products or services
• No agreement among participants regarding the
  purchase or sale of a product or service
  purchasing and selling decisions are independent
  company decisions
• No disparagement of any products or third party
  entities or individuals, particularly any vendor

5
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process recommendation
• Next Steps
• Wrap-up

6
Introduction

• Name
• Company
• Role
• Expectations

7
Next Steps Field Ticket?from Dec 9th Meeting

• Review Business Process Guideline (Jan. 16, 2009)
• Approve
• Provide comments
• Review Implementation Guide (Jan. 16, 2009)
• Approve
• Provide comments
• Finalise additional messaging requirements (Jan.
  16, 2009)
• Eg. Approver contact details
• Prepare PTP for Pro-Forma Invoice Message
  (Jan.16, 2009)
• Project team meetings
• Other

8
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process recommendation
• Next Steps
• Wrap-up

9
Clarify and agree definitions and terminology
and document in the PIDD (Petroleum Industry Data
Dictionary) Documents available in 3901 Field
Ticket purpose, structure and sequence of line
items FieldTicketResponse purpose, structure,
sequence of line items Links to purchasing
documents contracts Transmission timing business
process Routing fields, routing definition,
process to handle incorrect routing information,
requirements for routing to specific field
locations Data elements and required information
do we have the fields necessary to link to both
purchasing documents and invoice documents / meet
trading partner requirements Attachments how
to manage  Develop business process guidelines
governing the Field Ticket process and business
requirements.
Field Ticket - PTP Scope
10
The goal of this initiative is to develop
initial business processes between trading
partners to support standalone exchange of field
tickets electronically between trading partners.

Field Ticket - PTP Goal
11
Business Process Guidelines documentation
including Use Case(s), diagrams, best
practicesRequirements if any for message
modificationsPIDDClarify and agree terminology
and definitionsUpdate PIDD entries throughout
life of the projectWorkgroup chair is
responsible for ensuring PIDD is updated
Field Ticket - PTP Deliverables
12
To be very clear, the Field Ticket is an
ESTIMATE of work performed and products
delivered. While pricing may be included, we are
not suggesting that an approved Field Ticket
automatically corresponds to approved, final
pricing. Date 12/13/2006
Field Ticket - Purpose
13
Field Ticket PilotEnCana - Schlumberger
14
Process Requirements

• information needed (preferably with order)
  should include work location The operator needs
  to provide this information as it would be
  confusing if everyone has their own codes.
• Matching Buyer/Supplier Assets remains a
  challenge
• Required data (AFE, WBS, UWI)
• AFE number may be used multiple times
• Well Master data different systems
• (UWI) has differing formats

15
Learnings and Challenges

• A unique identifier for the Field Ticket that
  will be referenced on the invoice and facilitate
  processing should also be included.
• Process and algorithms for matching invoice and
  FT must be enhanced
• Field Ticket line Items to Invoice Line items
• Field Ticket most often does not exactly match
  Invoice
• Re-Calculations must be consistent (Net price,
  Discounts) Field Tickets vs. Invoice

16
Learnings and Challenges

• Routing and other internal information used to
  facilitate processing may be added as appropriate
  by the trading partner.
• It was noted that if on site, the supplier and
  buyer will generally review a field ticket and
  agree upon the details and any resulting changes
  to be made by the supplier prior to approval.
• A mutually agreed dispute resolution process
  should be in place prior to transmission of
  electronic messages.
• No attachments to the Field Ticket/Field Ticket
  Response. The FT and FTR documents include
  elements for Reference Information and Comments.

17
Learnings and Challenges

• Suppliers may have limitations on creating
  Digital Field Tickets at time of delivery
• When is the PIDX Field Ticket generated
• (Field, Sales Order, Invoice)

18
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process Recommendation
• Next Steps
• Wrap-up

19
Field Ticket- Benefits

• No human keying required on either side
• Early detailed Validation and Approval of work
  done
• Managing Commitments
• Two-way match the Field Ticket to Invoice
• Simplification of ticket approval for unmanned
  locations
• Systematic reconciliation of invoice to Field
  Tickets

20
Field Ticket - Business Process Flow
21
Field Ticket Business Process Guideline
22
Field Ticket Implementation Guide
23
Field Ticket Message Requirements

• BMWG Field Ticket Response Message missing
  approver Contact details (Reviewing)
• Asset
• Removal of pricing, discounts, allowances, etc.
• Other?

24
Field Ticket PIDD Requirements

• Approver Contact details of Field Ticket Response
• Others

25
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process recommendation
• Next Steps
• Wrap-up

26
Next Steps Field Ticket

• Finalise the Business Process Guideline.
• (BPWG) Feb 10th, 2009?
• Finalise the Field Ticket implementation Guide.
• (BMWG) Feb 10th, 2009?
• Update PIDD.
• (BMWG) Feb 10th, 2009?
• Finalise and prepare to send final materials to
  SG chair for release coordination
• Propose results for inclusion to RP 3910
• (BPWG and BMWG)

27
Next Steps Field Ticket

• Vote at BPWG Meeting on March 12th
• Send final Business Process Guideline to SG
  chair for release coordination
• Post publication materials to PIDX site for
  review and comment (Complete by April 30, 2009)
• Email notification of posted materials to PIDX
  member community and additional distribution
  lists as appropriate
• Collect and distribute comments (June 2009)
• Others

28
What Well Cover

• Welcome
• Anti-trust Statement
• Introduction
• Field Ticket Project Team Proposal (PTP)
• Field Ticket Business Process recommendation
• Next Steps
• Wrap-up

29
Thank You!
anthony.aming_at_bakerhughes.com mlanier_at_miswaco.com
jstukes_at_ofs-portal.com lwang_at_ofs-portal.com
30
Approach to Projects

• Standards Development Process
• PHASE 1 Project Team Proposal (PTP)
• PHASE 2 Project Implementation
• PHASE 3 Ballot Publication
• Develop Plan
• Hit Milestones
• Meetings
• Reporting

31
Project Team Proposal
32
Project Implementation
33
Ballot Publication
34
BPWG Project Survey - Results
35
BPWG Project Survey - Results