1 / 31

Enterprise Upstream/ Wellcore Integration

Enterprise Upstream/ Wellcore Integration. Jim Pennington & Nitin Kumar, Nov 3, 2010. Agenda. Background Business Process Overview Technical Overview Questions/Discussion. EU/ Wellcore Integration. Background. The Well Lifecycle. Background. Geology & Prognosis. AFE Management.

keene
Download Presentation

Enterprise Upstream/ Wellcore Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enterprise Upstream/Wellcore Integration Jim Pennington & Nitin Kumar, Nov 3, 2010

  2. Agenda • Background • Business Process Overview • Technical Overview • Questions/Discussion

  3. EU/Wellcore Integration Background

  4. The Well Lifecycle Background Geology & Prognosis AFE Management Construction Drilling Facilities & Pipeline Workovers Opportunity Inventory Regulatory & Compliance Completions Production & Revenue Reclamation & Abandonment Reserves Management Surface & Mineral Land Operations Planner & Rig Scheduler Capital & Operations Cost Management Workflow for Routing, Approvals, & Notifications Wellcore Enterprise Upstream

  5. Background Reporting Operations Accounting AFE’s Costs

  6. Integration Objectives • Minimize the number of systems that end users must interface with to get their jobs done • Synchronize AFE identifiers across systems to allow cross system reporting • Provide some measure of Accounting control over the AFE approval process • Centralize the creation of Parties and Report Centers to control duplicates, enforce naming standards and use same identifiers across systems

  7. Integration Objectives • Use the same Report Centers (cost centers) in Wellcore, EU and Accounts Payable so that costs coded in AP can flow to Wellcore and can be used to accumulate actual costs to compare with budget

  8. Fundamental Assumptions • Parties will be created and maintained in TEL. When Parties are approved they flow to EU Base. EU Base will be the source of integration data for Parties. • Report Centers will be created and maintained in EU Base. • Operations AFEs will be created and routed for approval in Wellcore. Non-operations AFEs will be created and approved in EU.

  9. Three Integration Flows – High Level Tobin Enterprise Land EnterpriseUpstream Parties Ops AFEs 3 Parties 1 Report Centers Wellcore 2

  10. Two More Optional Integrations 2. Field capture costs for Accruals 1. Actual costs for Budget comparison Financials Wellcore Actual Costs Field Costs Wellcore Enterprise Upstream (AFE)

  11. EU/Wellcore Integration Business Process Overview

  12. Parties Integration – Business Process • Vendors and JIB Partners are the Parties that must be interfaced from EU to Wellcore • Vendors in EU = Vendors in Wellcore • JIB Parties in EU = AFE Participants in Wellcore • Not all Vendors in EU are needed in Wellcore, un-needed Vendors must be excluded • Partners have a role of JIB in EU • Vendors will use a user-defined role of WCVNDR • Business process: No user-defined role=WCVNDR should be assigned to a Party without role=VENDOR

  13. Parties Integration – Business Process • Parties Integration is initiated when a new party is added or when a party is updated. • Basic Party information is extracted from EU and sent to Wellcore. • A new Party with role of JIB or WCVNDR in EU = new Vendor or Participant in Wellcore. • If Party info is updated in EU, the Party info is interfaced to Wellcore and updated there.

  14. Parties Integration – Business Process • When a new Vendor or Participant is added in Wellcore a report/alert is sent to the Wellcore Administrators to let them know they can add additional information not available in EU. • Participant WI is interfaced from EU to Wellcoreone time when the Party is associated with an AFE in EU/Oracle and DOI is assigned. • Generic vendor with the name “PLEASE ADD VENDOR” is available for emergency use.

  15. Parties Integration – Business Process

  16. RC Integration – Business Process • In Wellcore an AFE can be associated with four types of Sites • Wells…………………..EU RC Type = WELL • Pads……………………EU RC Type = WPAD • Facilities………………EU RC Type = WFAC • Pipelines………………EU RC Type = WPIP • All RCs are created in EU • The objective is to integrate those RCs that will be associated with an AFE in Wellcore.

  17. RC Integration – Business Process • Rollup hierarchy in Wellcore is a four-level structure (Company, Business Unit, Project, Area/Phase). These are set up manually in Wellcore. • Potential well surface locations are identified by the Well Planning group and communicated to EU Central Data Administration where they are set up as planning wells. • Alternatively, wells acquired through acquisition are set up in EU. • Integration to Wellcore is initiated.

  18. RC Integration – Business Process • As the time to raise an AFE for drilling a well draws near, Operations sends a request to the EU CDA group for the Wells, Pads, Facilities and Pipelines that will be associated with the AFE. CDA sets them up in EU. • Integration to Wellcore is initiated. • Issue: How to determine the Wellcore rollup hierarchy for WFAC, WPIP, WPAD as they are not part of the EU corporate RC hierarchy

  19. Report Centers Integration

  20. AFE Integration – Business Process • AFE’s for Operations are initiated in Wellcore. Initially the AFE number is autogenerated as a sequential number starting with “TEMP.” • The AFE is routed for approval. Through the sign-off process it comes to Accounting as final sign-off. Accounting changes the TEMP number to whatever number they want. • At final sign-off the AFE is interfaced to EU via the AFE XP.

  21. AFE Integration – Business Process • AFE Headers and Details are interfaced from Wellcore to EU. • AFE RC Associations and DOI ownership percentages are not interfaced. • A notification is sent to the EU AFE user(s) to update the AFE RC Associations and DOI in EU. • The AFE status is set to Pending in EU until partner sign-off is received; then it is manually updated to Approved.

  22. AFE Integration – Business Process • If an AFE is revised or supplemented in Wellcore the revision or supplement is interfaced to EU. • When an AFE is closed in Wellcore, the status in EU is changed to “Soft-Close” via the interface.

  23. AFE Integration

  24. EU/Wellcore Integration Technical Overview

  25. Parties Integration – Technical Overview • Oracle Workflow Business Event for Parties is seeded in EU. • p2es.EnterpriseUpstream.eb.party.role.create • p2es.EnterpriseUpstream.eb.party.role.update • P2 Professional Services (Consulting) developed a PL/SQL package to extract Party information. Execution is controlled by subscription to the Parties Business Events or can be scheduled. • Wellcore Development supports staging tables and associated integration packages to bring the Party information into Wellcore as Participant or Vendor.

  26. Parties Integration – Technical Overview EU WELLCORE ST_IN_VENDORS EB_PARTIES EB_SITES EB_PARTY_SITE_ROLES ST_IN_PARTICIPANTS Party Identifer = EB_PARTIES.USER_KEY || EB_PARTY_SITE_ROLES.SITE_SEQUENCE ST_IN_VENDORS. ENTITY_ID ST_IN_PARTICIPANTS. PARTICIPANT_ID

  27. RC Integration – Technical Overview • Oracle Workflow Business Event for Report Centers is seeded in EU. • p2es.EnterpriseUpstream.eb.ReportCenter.create • p2es.EnterpriseUpstream.eb.ReportCenter.update • P2 Professional Services (Consulting) developed a PL/SQL package to extract RC information. Execution is controlled by subscription to the RC Business Events or can be scheduled. • Wellcore Development supports staging tables and associated integration packages to bring the RC information into Wellcore.

  28. RC Integration – Technical Overview EU WELLCORE ST_IN_WELLS ST_IN_PADS ST_IN_FACILITIES ST_IN_PIPELINE EB_REPORT_CENTERS EU_COMPLETIONS_DV EB_RC_HIERARCHY_FLAT_V EU_WELLS ST_IN_WELLS. WELL_ID ST_IN_PADS. PAD_ID ST_IN_FACILITIES. FACILITY_ID ST_IN_PIPELINE. PROPERTY_NUMBER RC Identifier = EB_REPORT_CENTERS.USER_KEY

  29. AFE Integration – Technical Overview • P2 Professional Services (Consulting) developed a PL/SQL package to extract AFE information. Execution is scheduled in Wellcore. The package extracts newly approved AFEs and loads it to the EU AFE XP staging tables. • P2 Development supports a standard integration point (AFE XP) which has staging tables and validation processes to edit the data and bring valid data into the EU application tables.

  30. AFE Integration – Technical Overview EU WELLCORE AFE AFE_VERSION HIERARCHY_LABELS MAJOR_CODE MINOR_CODE EE_AFES_XP EE_LINE_ITEM_XP AFE Identifier = AFE.AFE_NUMBER EE_AFES_XP. AFE_NUMBER

  31. Questions

More Related