Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Bridging Cross-Functional Systems Using PPDM Well Standard

245 Aufrufe

Veröffentlicht am

  • Als Erste(r) kommentieren

  • Gehören Sie zu den Ersten, denen das gefällt!

Bridging Cross-Functional Systems Using PPDM Well Standard

  1. 1. Chevron May, 2012 Bridging Cross-Functional Systems using the PPDM Well Standard PNEC - 16th Data Management Conference Munira Gandhi & Chellie Hailes
  2. 2. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 2 Munira Gandhiand Chellie Hailes Contents Overview ......................................................................................................................................... 3 Case Study - Waterflood Reservoir Management Solution............................................................ 3 Challenges ................................................................................................................................... 4 Approach Consideration ................................................................................................................. 5 Candidates for study and examination........................................................................................... 5 Well Conceptual Information Model (Internal Standard)........................................................... 6 PPDM “WIAW” (What is a Well) (Industry Standard) ................................................................ 7 Internal Standards for Definition Standards (Internal Standard) ............................................... 8 Outcome and design decisions....................................................................................................... 8 Well Head Stream and Well Reporting Stream .............................................................................. 9 Relationship between Well / Well Head Stream and Well Reporting Stream.......................... 12 Advantages of Implementation of Well Head Stream and Well Reporting Stream ................. 14 In Conclusion................................................................................................................................. 14 Benefits of the case study to the industry .................................................................................... 15
  3. 3. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 3 Overview The intent of this paper is to share with industry how the Well and its components as defined in the PPDM Well Standard is being applied to efficiently integrate cross-functional well data sources to develop and sustain a Waterflood Reservoir Management Solution. In particular, the concept of Well Head Stream and Well Reporting Stream is used to bridge the master and transactional data. Case Study - WaterfloodReservoir Management Solution The goal of the Waterflood Reservoir Management Solution is to reduce the time and effort required to access and analyze data and to optimize the waterfloods to realize their full secondary recovery potential. Waterflood Reservoir Management Solution needed to develop technology-enabled workflows and applications that can be deployed across Business Units in order to enable them to meet the Chevron Internal Standard for Waterflood Reservoir Management. Chevron internal standards as developed by the Chevron Reservoir Management group. Waterflood Reservoir Management Solution requirements included creating a data model that will suffice the following:  The model will bind information from various cross-functional systems. Solution will need to enable workflows that would require information from various cross-functional systems like Production, drilling, G&G, etc.  Engineers should be able to analyze the surface as well as sub-surface information.  Scalable, common solution for various business units. Common in terms of Data Model definitions and Implementations. Scalable and performant to serve the solution needs.  Design to be completed in a timely fashion.
  4. 4. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 4 The need to create a data model with the above requirements presents some challenges for the design. Challenges 1) Bridging of master data and transaction data from diverse data sources a. The bridging of master data and transactional data from diverse data sources that support business functions is a key to successful hydrocarbon recovery is critical to an Oil and Gas enterprise. b. The well, being the pivotal E&P asset, is the most common information entity required for bridging cross-functional data to satisfy analytical and reporting requirements. 2) Integrating diverse functional needs a. These diverse data sources include vital systems of record, data repositories and historians, and numerous process specific applications. All of these maintain some collection of master data and/or entity identifiers to support their specific function. b. As many functional systems maintain well master data specific to a set of business processes and related transactional data, a myriad of duplicate and conflicting identifiers, terms, definitions, reference values, attributes and metadata emerge – making it difficult to bridge the chasmwe call ‘integration’. 3) Lack of a common identifier a. Systems can’t communicate easily due to the lack of a common identifier for well entity amongst the various systems. b. System may have good credibility and identifier for its own use, but may not be helpful for the need of general usage. Examples include aligning master and transactional systems, G&G and drilling systems, drilling and production systems, etc…. 4) Security and information accessibility a. Systems that deal with secured and regulated information have more restriction when integrating. 5) Common Data Model a. Data Model should be implemented to meet the common goal for various business units, yet satisfies diverse business needs as each business units are so different in their own ways, presenting the complexity.
  5. 5. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 5 To overcome the enormous challenges and complexity, the following options and approach were taken into consideration. Approach Consideration Approach for Data Design Commonality Scalability Complexity Availability Extensibility Effort Level Home Grown N N Y Y N 3 Industry Standard Y Y N Y Y 2 Internal Standards Y Y N Y Y 1 Notes : Effort Level ( 1 to 3, 1 being minimum, 3 being maximum) Clearly, Industry Standard and InternalStandardswere the obviouswinners. Examination and Study of those were now essential. Candidates for study and examination Couple of vendor option and industry standards was considered for study. Based on the initiatives already in place, availability and usability in Chevron, the following were the winners for intensive study and examination for the requirements: 1. Well and Reservoir Conceptual Information Model (Internal Standard) 2. PPDM “WIAW” (What is a Well) (Industry Standard) 3. Internal Standards for Definition Standards (Internal Standard)
  6. 6. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 6 Well Conceptual Information Model (Internal Standard) Conceptual model represents Well Components from “WIAW”. The Well Components Entity definition is based on PPDM “WIAW”. The Conceptual Information Model and the attribute definitions are based on the Internal Initiatives. WELL SET WELL SET NAME WELL ENTITY NAME WELL ENTITY TYPE : [List] EXPIRY DATE WELL WELL NAME WELL NUMBER BUSINESS LIFE CYCLE PHASE : [List] LAHEE BUSINESS INTENTION : [List] BUSINESS OUTCOME : [List] PLAY TYPE : [List] PARTICIPATION : [List] WELL STATUS : [List] EXCEPTION : [List] COMPOSITION : [List] OPERATOR NAME OWNERSHIP : [List] INITIAL SPUD DATE/TIME ABANDONMENT DATE RECLAMATION DATE EXPIRY DATE WELL ORIGIN COUNTRY NAME : [List] STATE/PROVINCE/TERRITORY : [List] OPERATING ENVIRONMENT : [List] SURFACE LOCATION ATTRIBUTES LEGAL DESCRIPTION ATTRIBUTES COORDINATE SYSTEM ATTRIBUTES HOST FACILITY ATTRIBUTES WATER DEPTH ATTRIBUTES ELEVATION ATTRIBUTES EXPIRY DATE WELLHEAD STREAM WELLHEAD STREAM NAME WELLHEAD STREAM NUMBER WELLHEAD STREAM TYPE : [List] WELLHEAD STREAM ACTIVITY : [List] PRODUCTION METHOD : [List] RAW PRODUCT TYPE : [List] INJECTED METHOD : [List] INJECTION PRODUCT : [List] EXPIRY DATE WELL REPORTING STREAM REPORTING STREAM NAME REPORTING STREAM NUMBER WELL COMPONENT ENTITY RAW PRODUCT TYPE : [List] EXPIRY DATE WELLBORE WELLBORE NAME WELLBORE NUMBER DRILL START DATE/TIME DRILL END DATE/TIME DRILL OUTCOME : [List] PLUGGED DATE/TIME BUSINESS INTEREST : [List] WELLBORE STATUS : [List] WELLBORE TYPE : [List] TRAJECTORY : [List] CONTRIBUTION : [List] LAHEE PURPOSE : [List] BOTTOM/END POINT LOCATION ATTRIBUTES BOTTOM/END POINT COORDINATE ATTRIBUTES DIRECTIONAL SURVEY ATTRIBUTES DEPTH ATTRIBUTES EXPIRY DATE WELLBORE SEGMENT SEGMENT NAME SEGMENT NUMBER TOP/START DEPTH ATTRIBUTES BOTTOM/END DEPTH ATTRIBUTES EXPIRY DATE WELLBORE CONTACT INTERVAL INTERVAL NAME INTERVAL NUMBER TOP/START DEPTH ATTRIBUTES BOTTOM/END DEPTH ATTRIBUTES EXPIRY DATE WELLBORE COMPLETION COMPLETION NAME COMPLETION NUMBER COMPLETION DATE COMPLETION STATUS : [List] TOP/START DEPTH ATTRIBUTES BOTTOM/END DEPTH ATTRIBUTES EXPIRY DATE has has
  7. 7. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 7 PPDM “WIAW” (What isa Well) (Industry Standard) PPDM website is extensively helpful to understand the Well Components, as it describes the components with examples and wonderful diagrams.
  8. 8. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 8 Internal Standardsfor Definition Standards(Internal Standard) Upstream Registry of approved definitions for Entities/Attributes and business rules Chevron Internal SharePoint site that defines the standards developed by Upstream Standard/Upstream Architecture groups. Example of a standard defined for an attribute of the well component: UPSTREAMSTANDARD / UPSTREAMARCHITECTURE Information Object/ Entity Logical Attribute Logical Definition Standard Reference Value Standard Reference Code Standard Reference Value Definition WELLHEAD STREAM ACTIVITY The WELLHEAD STREAM "ACTIVITY" describesthe functioningof a Wellhead Streamover the last 24- hour period. Injecting IJ WellheadStreaminjectedinthe last24-hour period In Service IS WellheadStreamwasinservice inthe last24- hour period Not Injecting NI WellheadStreamdidnotinjectinthe last24-hour period Not Producing NP WellheadStreamdidnotproduce inthe last24- hour period Not In Service NS WellheadStreamwasnotinservice inthe last24- hour period Producing PR WellheadStreamproducedinthe last24-hour period Outcome and designdecisions Outcome and design decisions based on the study of the above three candidates (standards):  Use Well Conceptual Information Model as it clearly defines the relationship between Well and its components  Use PPDM “WIAW” definitions, diagrams and examples  Use Internal Standards for Definition for Entities/Attributes needed for Reservoir Management Solution  Introduce and Implement Well Head Stream and Well Reporting Stream to integrate Master data with Transactional data.
  9. 9. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 9 Well Head Stream and Well Reporting Stream
  10. 10. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 10
  11. 11. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 11
  12. 12. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 12 Relationship between Well/ Well Head Stream and WellReportingStream WELL SET WELL SET NAME WELL ENTITY NAME WELL ENTITY TYPE : [List] EXPIRY DATE WELL WELL NAME WELL NUMBER BUSINESS LIFE CYCLE PHASE : [List] LAHEE BUSINESS INTENTION : [List] BUSINESS OUTCOME : [List] PLAY TYPE : [List] PARTICIPATION : [List] WELL STATUS : [List] EXCEPTION : [List] COMPOSITION : [List] OPERATOR NAME OWNERSHIP : [List] INITIAL SPUD DATE/TIME ABANDONMENT DATE RECLAMATION DATE EXPIRY DATE WELL ORIGIN COUNTRY NAME : [List] STATE/PROVINCE/TERRITORY : [List] OPERATING ENVIRONMENT : [List] SURFACE LOCATION ATTRIBUTES LEGAL DESCRIPTION ATTRIBUTES COORDINATE SYSTEM ATTRIBUTES HOST FACILITY ATTRIBUTES WATER DEPTH ATTRIBUTES ELEVATION ATTRIBUTES EXPIRY DATE WELLHEAD STREAM WELLHEAD STREAM NAME WELLHEAD STREAM NUMBER WELLHEAD STREAM TYPE : [List] WELLHEAD STREAM ACTIVITY : [List] PRODUCTION METHOD : [List] RAW PRODUCT TYPE : [List] INJECTED METHOD : [List] INJECTION PRODUCT : [List] EXPIRY DATE WELL REPORTING STREAM REPORTING STREAM NAME REPORTING STREAM NUMBER WELL COMPONENT ENTITY RAW PRODUCT TYPE : [List] EXPIRY DATE WELLBORE WELLBORE NAME WELLBORE NUMBER DRILL START DATE/TIME DRILL END DATE/TIME DRILL OUTCOME : [List] PLUGGED DATE/TIME BUSINESS INTEREST : [List] WELLBORE STATUS : [List] WELLBORE TYPE : [List] TRAJECTORY : [List] CONTRIBUTION : [List] LAHEE PURPOSE : [List] BOTTOM/END POINT LOCATION ATTRIBUTES BOTTOM/END POINT COORDINATE ATTRIBUTES DIRECTIONAL SURVEY ATTRIBUTES DEPTH ATTRIBUTES EXPIRY DATE WELLBORE SEGMENT SEGMENT NAME SEGMENT NUMBER TOP/START DEPTH ATTRIBUTES BOTTOM/END DEPTH ATTRIBUTES EXPIRY DATE WELLBORE CONTACT INTERVAL INTERVAL NAME INTERVAL NUMBER TYPE : [List] TOP/START DEPTH ATTRIBUTES BOTTOM/END DEPTH ATTRIBUTES EXPIRY DATE WELLBORE COMPLETION COMPLETION NAME COMPLETION NUMBER COMPLETION DATE COMPLETION STATUS : [List] TOP/START DEPTH ATTRIBUTES BOTTOM/END DEPTH ATTRIBUTES EXPIRY DATE has has Assumption of the relationship based on the conceptual information model:  Wellbore Contact Interval of different types (Perforation, zone, reservoir, etc) provides the master data for the well component at that sub-surface level.  Well Reporting Stream created for each wellbore contact interval ties to provide the production/transactional data for that level. Implementation can mandate creating a stream for each wellbore contact interval, and so production data if allocated properly then can be reported at that granular level.
  13. 13. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 13  Well reporting stream transactional information can be rolled up at the well head stream.  [List] means list of the attributes defined by the internal standards and/or PPDM standards. Example : UPSTREAMSTANDARD / UPSTREAMARCHITECTURE Information Object / Entity Logical Attribute Logical Definition Standard Reference Value Standard Reference Code Standard Re WELLBORE CONTACT INTERVAL INTERVAL TYPE The WELLBORE CONTACT INTERVAL"CONTACTINTERVAL TYPE" denotesthe kindof contact interval - a categorizationtospecifyan interval'scorrelationtoanother definedinformationobject. For example,aWellboreContact Interval definedtocorrelate withthe informationobject "reservoir"wouldcarrya Contact Interval Type = "Reservoir"anditsLikewisea Wellbore ContactInterval definedtocorrelate withthe informationobject"zone" wouldcarry a Contact Interval Type = "Zone". RESERVOIR RV The "RESERVOIR"Wellb depthrange withinaWe perforationsthatcorrela Wellbore andthe Reserv ZONE ZN The "ZONE" Wellbore Co range withina Wellbore correlate tothe intersec minorinterval withinaF PERFORATED PF The "PERFORATED" Wel depthrange withinaWe perforationscreatedtop one or more Reservoirs. SLIDING SLEEVE SS The "SLIDING SLEEVE" W measureddepthrange w shutoff or openingof flo orderto regulate pressu leasttwodefined"slidin trackingof activitybetw positioning. OPEN HOLE OH An "OPEN HOLE" Wellbo depthrange that establi Wellbore where nocasin the productionzone.
  14. 14. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 14 Advantagesof Implementation of Well Head Streamand Well Reporting Stream Well Head Stream and Well Reporting Stream lets us use the (master) Well Components (Well , Well Origin, Wellbore, Wellbore Contact Interval) with the (transactional) Well Components (Well Head Stream, Well Reporting Stream) easily and flexibly Well Reporting Stream can be flexibly used to report at surface and/or sub surface level Subsurface objects (Zone, Perforation, Sand) can now be defined easily for that Well by the Wellbore Contact Interval, and the Well Reporting Stream can then tie the transactional (allocation) of the volumes at that level Wellbore Completion and Completion definition is vague and have been used differently, so introducing and implementing Well Head Stream and Well Reporting Stream helps to solve that Clarify easily the stream which ties to the transaction “Money Entity” information Well Head Stream with the attributes like Entity level and Entity type, can be flexibly joined with any of the Well Components (Well, Well Origin, Wellbore, Wellbore Completion and/or Well Set) PPDM diagrams and “WIAW” booklet helps to explain the concept clearly to non- technical folks In Conclusion: Following requirements and challenges were met:  Scalable, Common Solution o Industry and Internal Standards does provide a common solution and a common platform o Industry and Internal standards does provide scalability and usability  Bridging the Cross Functional Systems o Master and Transactional system can be integrated with Use of the Well Head Stream and Well Reporting Stream o Other Cross functional systems can be integrated with the Master data and eventually can be integrated o Doesn’t resolve the data quality between this system, but helps with crossing the bridge a little easier  Surface and Sub-Surface information will be available o Well Reporting Stream and Wellbore Contact Interval relationship makes the Sub-Surface information available
  15. 15. Bridging Cross-FunctionalSystemsusing the PPDM WellStandard 15 Requirements and Challenges were met by implementing the Industry Standard – PPDM “WIAW”, and the internal Standards – Well Conceptual Information Model together. Using the PPDM definitions and internal standard definition for entity/attribute keeps all together. Issues like lack of identifier, data quality and data gaps are not resolved, but the model and use of common definitions brings in an opportunity to discuss the gaps and to resolve them. Benefits of the case study to the industry PPDM “WIAW” and the PPDM Well Group have defined the well components in extensive details. The Waterflood reservoir solution implementation proves the robustness of those concepts along with Chevron Internal standards. Challenges listed in the case study are known industry wide, and needs to be dealt, so the case study shows the approach taken by Chevron to tackle some of those challenges. Industry wide challenge of bridging the cross-functional systems is handled efficiently and explained comprehensively by the above case study.

×