APDM 6.0 ArcGIS Pipeline Data Model Peter Veenstra APDM Standing - PowerPoint PPT Presentation

APDM 6.0 ArcGIS Pipeline Data Model Peter Veenstra APDM Standing Committee

Abstract • The purpose of this workshop is to review the final release of the ArcGIS Pipeline Data Model (APDM) version 6.0. • Changes include; – simplification of the data model structure, – a focus on supporting gathering systems – full support for both geometric/feature-based and event-table based implementation of the model. • An overview of the resources available for the APDM 6.0 implementation will be provided including a preview of the latest APDM.net website. • An overview of how the model has been implemented in Sparx System Enterprise Architect UML Modeling software will be provided. • Lastly, the current state of data models and best practices available to pipeline operators and GIS practitioners will be outlined as an aid to helping pipeline operators understand the options available for managing pipeline data within a GIS.

Introductions • APDM Standing Committee Co-Chairs – Tom Coolidge – ESRI Pipeline Industry Manager – Peter Veenstra – Willbros Engineering • APDM Standing Committee – Justin Anderson – Enbridge Houston – Jeff Allen – Coler and Colantonio – Patrick Baes – Global Information Systems – Ron Brush – New Century Software – Eric James – Colonial Pipeline – John Linehan – JP Kenny – Tracy Thorleifson – Eagle Information Management – 1 open position • www.apdm.net • www.esri.com/industries/pipeline/community/datamodel • https://www.linkedin.com/groups/APDM-ArcGIS-Pipeline-Data-Model- 155824/about

Overview • Part 1 - Changes in APDM 6.0 • Part 2 - ArcGIS Pipeline Data Model (APDM) • Part 3 – APDM 6.0 in Enterprise Architect • Part 4 - State of Data Models – ArcGIS Pipeline Data Model (APDM) – PODS Relational – PODS ESRI Spatial • Part 5 - Thoughts on Pipeline Data Models

Part 1 - Changes in APDM • Why do we do this? • High level changes (Change Log)(Logical)(Physical) – Metadata Tables – Corrections – New Abstract Classes (more refined) – Relationship to LineLoop for ‘online’ features – Less ‘example’ classes – Activity and Document CrossRef – Better Site Location Tables – EventOffset Attribute Part 1 1 of 11

Changes in APDM 6.0 • APDM is a Template – it has always been a starting point from which more comprehensive data models can be developed • Contrary to popular belief APDM was never intended to be a ‘be-all-end-all’ repository of pipeline data • It has always been a design specification for how pipeline data is created, edited, and how that data responds to alterations/modifications to the pipeline centerline • Optional classes have been reduced to keep the model in- line with being template • Changes to the core have been additive rather than deleting, merging, splitting classes and elements Part 1 2 of 11

APDM 6.0 – Why change? • Represents changes to the core elements of the data model • Maintain compatibility with changes in core ESRI technology – guiding principle • Stay in sync with PODS ESRI Spatial Data Model • Get in-step with ESRI message towards data models and GIS as a service – location, services, data exchange, integration – simpler template to start with – helps smaller operators and gathering companies Part 1 3 of 11

Part 1 4 of 10

MetaData Tables • ReferenceMode, ClassMetaData, OnlineLocationClass – remain the same • Add RelationshipMetaData, DomainList, DomainMetaData, DomainClass are new Part 1 5 of 11

Abstract Classes [Object] OnlineEvent OBJECTID CLEditResponse <d> CLValidityTolerance <d> StationSeries EventOffset LineLoopEventID (fk) LineLoop APDMObject RouteEventID (fk) GlobalID EventID (pk) • APDMFeature and APDMObject PipelineID TagID OnlineFacilityEvent OnlinePointEvent OnlinePolylineEvent • Event-based Abstract Classes – Tables not InServiceDate Measure BeginMeasure Site [ObjectArchive] InstallationDate SeriesEventID EndMeasure CreatedBy OperationalStatus <d> Station BeginSeriesEventID CreatedDate SiteEventID (fk) Poiint_X BeginStation Feature Classes EffectiveFromDate Point_Y EndSeriesEventID EffectiveToDate Point_Z EndStation HistoricalState <d> Status <d> Status <d> LastModified SymbolRotation ModifiedBy OnlinePointFacilityEvent OnlinePolylineFacilityEvent OriginEventID Measure BeginMeasure <OnlineFeatureClass> ProcessFlag SeriesEventID EndMeasure Remarks Station BeginSeriesEventID OnlinePointForOfflineFeatureEvent OnlinePolylineForOfflineFeatureEvent Point_X BeginStation OffsetAngle BeginOffsetAngle Point_Y EndSeriesEventID OffsetDistance BeginOffsetDistance Point_Z EndStation StationLocated <d> EndOffsetAngle SymbolRotation EndOffsetDistance StationLocated <d> FittingEvent <OfflineFeatureClass> DateManufactured Grade <d> InletConnectionType <d> InletDiameter <d> InletWallThickness <d> Manufacturer <d> Material <d> PressureRating <d> Part 1 6 of 11

Relate to Lineloop • Direct relationship from online features to LineLoop • Designed to support feature-based gathering systems with no underlying stationing – have pipes related directly to a ‘lineloop’ grouping • Keeps hierarchy without need for stationing • If you have geometric features representing your pipes and not stationing then you can place these features, relate them to a line and be on-your- way. • Can implement Geometric-Networks OOTB Part 1 7 of 11

Less Example Classes • APDM is really a ‘design standard’ • Meets the minimum requirements for handling transmission and also gathering systems • Cleaner starting point • Less documentation to maintain • It can always be grown • Simpler and more technology focused • Example classes are still available in version 4.0 and 5.0 documentation via www.apdm.net Part 1 8 of 11

Activity CrossRef APDMObject NonFacilityObject AuditObject • Why do (did) we have audit tables? • Remove all audit tables from database ActivityHierarchy ActivityCrossRef ClassName (fk) <d> ParentActivityEventID (fk) • Each feature class and table relates to FeatureEventID ChildActivityEventID (fk) ActivityDocumentCrossRef Comments ExternalDocumentEventID (fk) CommentBy CommentDate ActivityCrossRef Activity • Intersection or M-N table between Activity and ActivityDate ActivityDescription ActivityName ActivityType <d> rest of database • Less tables, less relationship classes, Bend • Single source for tying/grouping/querying what Branch Company are stored in separate tables or were implicitly Coating ControlPoint joined by geographic location ConditionOrAnomaly Etc... Part 1 9 of 11

NonFacilityObject AuditObject Document CrossRef • Same construct as activities ActivityDocumentCrossRef ExternalDocumentEventID (fk) • Remove all M-N relationships between Activity ExternalDocument ActivityDate DocumentDescription ExternalDocument and audit tables from ActivityDescription DocumentType <d> ActivityName FileName ActivityType <d> FilePath database FileServer Hyperlink AltHyperlink • Each feature class and table relates to DocumentCrossRef DocumentCrossRef ClassName (fk) <d> • Less tables, less relationship classes, FeatureEventID FeatureAttributeName ExternalDocumentEventID (fk) ExternalDocumentReference • Single source for tying/grouping/querying what Bend are stored in separate tables or were implicitly Branch joined by document Company Coating ControlPoint ConditionOrAnomaly Etc ... Part 1 10 of 11

Site Location/EventOffset • Added SitePoint, SiteLayout and SitePolygon Tables • Added EventOffset field for all online event types – Allows OOTB ArcMap ‘Add Route Event’ tool to add events but offset from pipeline centerline – Useful for showing results of inspections over time or multiple inspections Part 1 11 of 11

Part II - APDM • ArcGIS Pipeline Data Model • Built for ESRI Geodatabase – Leverage ESR • Useful starting place • Describes in detail how pipeline data respond to centerline edits, location placement, and how editing can be performed on them • Standing Committee of 10 operators and vendors • Meet at PUG, GITA O&G and ESRI UC • Website – www.apdm.net and www.esri.com Part 2 1 of 1

Part III - APDM and Case Tools • Visio and UML and APDM • Alternative in Enterprise Architect Software (www.sparxsystems.com) – Is a Case Tool – Is ESRI Business Partner – Is ESRI’s preferred choice – Uses XML Workspace Import to build schema – not additive (need XML schema diff) – Scripts • for validation, • for organization • to import an existing Visio and XML Workspace into EA Part 3 1 of 2

Part III – APDM 6.0 in Enterprise Architect • Base Functionality - toolbar, diagrams, packages, hyperlinks, documentation • Import from Visio UML and from ArcGIS XML WorkspaceOrganization of Model • Validation of output XML Workspace before import into ArcCatalog • Modularization • Base Line (Documentation, Delta) • Multiple Inheritance (Abstract Class Hierarchy) • Script and Query Engine Part 3 2 of 2