Valid Implementation of APDM...Valid Implementation the APDM APDM Technical Presentation Abstract Classes • Abstract classes are the templates from which behavior (defined as attributes

Valid Implementation of APDM

ArcGIS Pipeline Data Model (APDM)Version 4.0

Publication Date: 2008-02-26

Valid Implementation the APDM

APDM Technical Presentation

Overview

•What is the APDM?•Why Implement APDM?•Interoperability•Valid Implementations – Examples



What is the APDM?• APDM (ArcGIS Pipeline Data Model)

is a ESRI Geodatabase template for the Pipeline Industry supporting Gas or Liquids, Gathering, Transmission, or Distribution Pipelines.

• Concentrates on defining and documenting CORE features using the “80% Typical” rule – these are features and phenomena that 80% or more of all pipeline companies track information on or use as part of their daily operations.

• APDM is implemented on ESRI’sGeodatabase Object-Relational Geographic Information System Model

• The APDM is starting point that can be extended and implemented to suit the needs of a business

APDM describes a pipeline by defining…• Core Elements - 24 tables that define:

• the pipeline centerline (route, series, corridor)

• activities (work orders, inspections etc.)

• external documents (document version, reports, design drawings, spreadsheets, photos etc.)

• ownership and company hierarchy (upstream, downstream, holding companies)

• product delivered• Sites• Reference modes (Measure, Station,

KM/Mile Post)• Behavior, through the use of ABSTRACT

classes, of pipeline features when they are created in the database, edited as part of the database individually or as part of a change to the pipeline centerline.



Abstract Classes• Abstract classes are the templates from which behavior (defined as attributes in

the class and relationships to other classes) are passed down to concrete feature/object classes in the APDM Geodatabase using a concept called ‘Inheritance’

• Control point inherit behavior from the CenterlinePoint Abstract Class• Elbows, Valves, and Flanges inherit behavior from the OnlinePointFacility

Abstract Class• Structures inherit behavior from the OfflinePoint Abstract Class

• Abstract class defines a specific set of behavior for a specific set of features particularly for edit operations:

• Control points will act this way when the XY or M (Station) value is altered• Elbows, Valves and Flanges will act this way when the centerline they are

located on is edited (a two point re-route occurs, the route is trimmed back or extended)

• Structures located within 660 feet of the centerline will act this way when the centerline is edited (the cease to impact the delineation of HCA)



• Elbow is a Concrete Class which inherits from…

• Fitting which inherits from …• OnlinePointFacility which inherits from …• OnlineFacility which inherits from …• OnlineFeature which inherits from …• FeatureArchive which inherits from …• Feature which inherits from …• Object



APDM Design Rationale• Core Features and Abstract Classes allow for customized and

individualized implementations with a standard ‘core’ for flexibility and interoperability

• Core features and Abstract Classes allow APDM Technical Committee to concentrate on capturing and defining behavior of pipeline features rather than rigorous definition of the featureattributes themselves

• APDM was designed to be implemented and maintained in ESRI Geodatabase without the need for custom application code

• It is relatively simple to represent other data models within the APDM using the CORE classes

• Features can be located on or along a pipeline by either/or bothabsolute positioning (Coordinates) and/or linear referencing (Route/Measure,Mile/KMPost)

• A combination of feature classes and event tables is allowed within a single APDM Geodatabase.



Interoperability (or what makes it valid)

•By implementing a CORE set of classes and by ensuring that all NEW classes added to the model implement the attributes and relationships of the ABSTRACT class that describes the newly created Feature/Object class = Valid APDM

•Data can be exchanged via all APDM models who implement the CORE and adhere to the ABSTRACT Class definitions



What can you do then?

• Well anything as long as the core classes, relationships between then and the ABSTRACT classes are used to define any new feature or object classes you add to the model.

• Add attributes to the core classes• Add new feature/object classes to the model using the ABSTRACT

classes as templates• You can use the example classes• You can add attributes to the existing classes• You can add new classes• You can remove example classes

• Any class that you add or remove to/from the model must be registered in the APDMClass metadata table



OBJECTID

Object

CalculateARM RefModeSubtypeValue (pk)RefModeSubtypeDescriptionRefModeUnits RefModeBasis RefModeType

ReferenceModeAPDMClassType ClassEventID (pk)ClassNameRequiresGeometry

APDMClass

AltRefMeasure

OriginClassEventID (fk)OnlineLocationClassEventID (fk)OnlineLocationMechanism

OnlineLocationClasses

Metadata

StationSeries

ControlPoint

AltRefMeasure

CPOnlineLocation

RemovedPoint

RemovedLine

The metadata classes represent a set of object classes that are used to hold information about the reference

modes, information about each concrete class inheriting from an ‘APDM Abstract Class’ and

information about which ‘offline’ APDM classes have related ‘online’ polyline or ‘online’ point classes.



Examples of APDM Implementations

• Non-stationed using Absolute Coordinates• Stationed Core w/ Example Classes as Feature Classes

• Stationed Core w/ Example Classes as Event Object Classes or Tables

• Stationed Core w/ combination of example, custom classes implemented as feature classes or object classes/event-tables.

• Stationed Core w/ one object class/event-table and many related object classes/tables.



Examples of APDM Implementations• Non-stationed using Absolute Coordinates (XYZ Only)

Core Abstract



Examples of APDM Implementations• Stationed Core w/ Example Classes as Feature Classes (XYZ and M)

Core Abstract

M

M



Examples of APDM Implementations• Stationed Core w/ Example Classes as Event Object Classes or Tables M)

Core AbstractM



Examples of APDM Implementations• Stationed Core w/ Example Classes as Feature Classes and Event Classes (XYZ and M)

Core Abstract

M

M

M



Examples of APDM Implementations• Stationed Core w/ one object class/event-table and many related object classes/tables. M)

Core M Abstract



Summary – Conclusions – Ramblings …

• This is an ESRI model

• ESRI is not in the habit of being a standards organization

• All ESRI Models are templates

• They can expand to suit the needs of your business

• The idea is to maintain flexibility AND capture logic in the database about complex pipeline data editing and data management operations



The truth is out there …

Documents

Valid Implementation of APDM...Valid Implementation the APDM APDM Technical Presentation Abstract Classes • Abstract classes are the templates from which behavior (defined as attributes