Introduction to the ArcGIS Pipeline Data Model (APDM) Version 4.0

1. Introduction to the ArcGIS Pipeline Data Model (APDM)Version 4.0 Peter Veenstra ESRI Petroleum User Group Conference - 2006

2. Introduction Presentation about … • Introduction to the APDM • Overview of APDM Version 4.0

3. ArcGIS Pipeline Data Model (APDM) Who: Industry consortium of ESRI, pipeline vendors and operators PUG  PIG  Steering Committee, Technical Committee What:Geodatabase model for transmission pipelines Where:www.apdm.net When: PUG, ESRI User Conference, GITA Oil & Gas Why: Passionate about ESRI technology

4. Overview of the APDM • ESRI Geodatabase model for … • gas and/or liquids, onshore/offshore, gathering, transmission, or distribution pipeline systems • Focused on pipelines that use stationed position AND XY coordinates to locate positions of features on or along the pipeline • APDM  ESRI Object Model Template to handle … • multiple forms of linear referencing • ESRI route and measure technology • hierarchical/geographical organization of pipeline features • Feature behavior during centerline editing operations • Links to external systems – ERP, Document Management, Work Order MS • Core Feature\Object Classes • Abstract Classes

5. Overview of the Model • APDM is the intellectual property of ESRI • Managed in trust by the Pipe Interest Group (Petroleum User Group) • Version 1.0 Build the model • Focus on the technology, the core and conceptual classes in the model. • Version 2.0 – 3.0 Link to the Enterprise • Refine the conceptual model, expand the core • Activities, External Documents, OwnerOperator, EventID • Version 4.0 Metadata • Data content • Schema Description and Management • Object behavior • Best Practices  Interoperability

6. APDM Steering and Technical Committees • APDM 4.0 Steering Committee ·Robert Brook, New Century Software, rob.brook@newcenturysoftware.com ·Chris Elmer, Sempra Utilities, celmer@semprautilities.com ·Greg McCool, Enbridge Energy Company, greg.mccool@enbridge.com ·David Nemeth, Panhandle Energy, dbnemeth@panhandleenergy.com ·Debra Rohrer, Columbia Gas, drohrer@nisource.com ·Mark Warner, Questar Pipeline, mark.warner@questar.com ·Edward Wiegele, GE Energy, edward.wiegele@ge.com ·Craig Wilder (Chairperson), El Paso Corporation, craig.wilder@elpaso.com ·Chad Zamarin, Colonial Gas, CZamarin@colpipe.com ·Andrew Zolnai, ESRI, azolnai@esri.com ·David Frye, ESRI, dfrye@esri.com • APDM 4.0 Technical Committee • ·John Alsup, ESRI, jalsup@esri.com • · Jannette Jensen, Questar Gas Company (Secretary), jannette.jensen@questar.com • ·Theo Lawrence, Great Lakes Gas Transmission, tblawrence@glgt.com • ·Todd Murphy, Panhandle Energy Corporation, temurphy@panhandleenergy.com • ·Buddy Nagel, El Paso Corporation, buddy.nagel@elpaso.com • ·Jeff Puuri, Advantica, Jeff.Puuri@Advantica.biz • ·Fred Spickler, Photoscience Inc, fspickler@photoscience.com • ·Tracy Thorleifson, Eagle Information Mapping, jtt@eaglemap.com • ·Peter Veenstra, GE Energy (Chairperson), peter.veenstra@ge.com

7. APDM Version 4.0 • Abstract Classes (Core Attributes and Relationships) • Centerline Objects, Facility Objects, Online/Offline Objects • Response to editing the centerline • Auditing feature/object edits • Core Classes • ControlPoint, StationSeries, AltRefMeasure, Lineloop, Subsystem, SubsystemHierarchy, LineloopHierarchy, Product, OwnerOperator, SubsystemRange, Site, Activity, ActivityHierarchy, ExternalDocument • Metadata Classes • Formal definition to describe behavior of reference modes • Units, Basis, Type • Listing and APDM categorization of classes within geodatabase • Each class in the APDM will inherit from one of the APDM Abstract Classes • Online Locations for Offline Features • Listing of offline/online class pairs • Listing of calculation methods for determining derivation of online locations • Inline History and Auditing • Facilities and Non-Geometric representation of features

8. ArcGIS Pipeline Data Model (APDM) • APDM Logical Model Poster – shows abstract classes, metadata classes, core classes and example concrete classes

9. Abstract Classes

10. Abstract Classes • Object based abstract classes showing centerline objects, facility objects and non-facility objects

11. Abstract Classes • Feature based abstract classes showing centerline objects, online/offline objects, facility objects and ‘online’ location objects

12. Abstract Classes- Inheritance • Example showing how a ‘concrete’ class is derived via inheritance from the APDM abstract classes

13. Core Classes • Represent the core classes within the model that must be implemented • These classes represent critical parts of a pipeline reflecting centerline editing and integration with other enterprise systems • ControlPoint – known points of XY and station value location for a given reference mode • StationSeries – a route feature built from control point for a given reference mode • AltRefMeasure – stores alternate reference mode information for online features • Lineloop – a series of connected station series forming a ‘line’ or ‘route’ • LineloopHierarchy – ability to categorize lineloops into logical groupings • Subsystem – an area or zone along the pipeline used to break it up into logical regions • SubsystemHierarchy – ability to categorize subsystems into logical groupings • SubsystemRange – the ‘online’ location of a subsystem along the centerline • Product – the product transported by the pipeline • OwnerOperator – owner and operator information for the assets of a pipeline • Site – any site boundary on or along the pipeline • Activity – things that ‘happen’ during the operation and maintenance of a pipeline • ActivityHierarchy – ability to categorize activities into logical groupings • ExternalDocument – reports, regulatory and source documents that specifiy or document assets and events on or along the pipeline

14. Metadata Classes • Describes the internal structure of the model for validation and verification

15. Implementing APDM • APDM is built for the geodatabase • It is an object model • It describes feature editing behavior • It provides meta-data or meta-models that can be integrated with other data models • APDM Core  APDM Tables  Add/modify classes and attributes • APDM Core  PODS Business/Feature/Event Tables  Add/modify classes and attributes • APDM Core  ISAT Business/Feature/Event Tables  Add/modify classes and attributes • APDM Core  Any pipeline data model business tables …  Add /modify classes and attributes • Implement APDM Abstract Tables and Core Tables

16. Compliance and Interoperability • The purpose of APDM is to capture the ‘behavior’ of pipeline events, features and objects within an geodatabase object model • The purpose of APDM 4.0 abstract, metadata and core classes is to provide a standard for judging APDM compliance to allow true interoperability between vendor applications and data models • Interoperability could be assessed by development of a standard set of editing, reporting and analysis applications that could be applied to any APDM geodatabase

17. Current Status of the APDM • Yearly cycle • Accrual of ideas and feedback – ESRI UC  Gita Oil & Gas (Summer to Fall) • Technical Committee develop new aspects of model (Fall through Winter  ESRI PUG) • Model Release (Spring  ESRI UC) • Planned Events • APDM Pre-Conference Workshop – Saturday, August 12th • http://www.esri.com/events/uc/sessions/uc_precons.html • Scheduled release of proposed changes (V4.0) • Logical Model Poster, Physical Model UML (Visio 2002 format) available from www.apdm.net/downloads.htm • White paper will be released in sections over the next 2-3 weeks for review up until 05/2006

18. Contact Information • Online Resources (APDM) • www.apdm.net • APDM Model and white paper, UML, XMI, logical model • www.esri.com\datamodels • APDM Technical and Steering Committees • Andrew Zolnai azolnai@esri.com • Craig Wilder craig.wilder@elpaso.com • Peter Veenstra peter.veenstra@og.ge.com