PIDX Field Ticketing update

1
PIDX Field Ticketing update

• Terry Thomas
• eContext Development Manager, eInitiatives
• Schlumberger
• Chris Foster
• Lead, Business Information Solutions
• EnCana

2

• Agenda
• Pilot progress to date
• Learnings so far
• Status and next steps
• Benefits to date

3

• Timeline

Initial engagement and demos
PIDX Working Committee established
Business Processes draft completed
Software changes and implementation guide
completed
Pilot started
4

• Pilot progress
• PIDX Field Tickets were successfully exchanged in
  August between test systems (using real data)
• Field tickets successfully exchanged in
  production in EnCanas Medicine Hat BU
• multiple jobs per AFE
• multiple jobs per day
• both manned and unmanned locations

5
(No Transcript)
6

• Learnings so far
• Process on physical signature amended by EnCana
• If signature is provided in the PIDX xml, DCR
  will load the charges in an approved state. No
  dispute would ever be received
• Audits will be performed to satisfy internal
  requirements
• If no signature (unmanned location), charges are
  loaded as pending and approval can be obtained
  through DCR

7
Signature provided?
8

• Learnings so far
• Matching assets is as challenging as expected
• Scribing errors on AFE number
• AFE number may be used multiple times
• Well Name truncated by different systems
• UWI has differing formats
• Issue is not insurmountable
• Need to adopt consistent format standards as part
  of BPG?

9

• Learnings so far
• Algorithms for matching invoice and FT must be
  enhanced
• Sub line items are causing difficulties in
  matching to invoice
• Should sub line items be added to the PIDX
  standard?

10

• Benefits
• No human keying required on either side
• Cost capture improvements seen from 10 down to
  0.1
• Simplification of ticket approval in unmanned
  locations
• Reconciliation to invoice expected to provide
  further value

11

• Next steps
• Full production test with all drilling locations
  in Medicine Hat BU
• Software changes to implement
• Enhanced asset matching capabilities
• Improved reconciliation algorithms
• Support for physical signature as approval

12

• Next steps
• EnCana has included DCR requirement in all 2008
  RFPs
• Completions on ramping will begin in November
  2007

13
(No Transcript)