ArcGIS Pipeline Data Model (APDM)...ArcGIS Pipeline Data Model (APDM) EGUG 2003 History of the APDM • March 2002—M.J. Harden Associates, Inc., starts initial work on the model

ArcGIS Pipeline Data Model (APDM) EGUG 2003

Implementing theArcGIS Pipeline Data Model

(APDM)

Peter VeenstraM.J. Harden Associates, Inc.

APDM Technical Committee Chairperson


Introduction (Who)• Peter Veenstra

• M.J. Harden Associates, Inc. • Chairperson of APDM Technical Committee

• Who, What, Where, When, Why of the ArcGIS Pipeline Data Model


APDM (Who)• ESRI Petroleum and Pipeline Special

Interest Groups• Steering Committee/Technical Committee


APDM (Who)• Members of the Technical and Steering

Committees• Steering Committee

• Greg McCool (El Paso Corporation), Chairperson • Pamela West (ChevronTexaco), Cochairperson• Maggie Mabrey (M. J. Harden Associates, Inc.),

Secretary• Andrew Zolnai (ESRI), Membership• Ron Brush (New Century Software)• Ed Wiegele (M. J. Harden Associates, Inc.)• Mary Muse (PG&E—California Gas Transmission)• Ken Greer (CenterPoint Energy)• Danika Yeager (Colonial)


APDM (Who)• Technical Committee

• Peter Veenstra (M.J. Harden Associates, Inc.), Chairperson

• Jay Smith (M.J. Harden Associates, Inc.), Secretary• Buddy Nagel (El Paso Energy)• Theo Lawrence (Great Lakes Gas Transmission)• Tracy Thorleifson (Eagle Information Mapping)• Scott Hills (ChevronTexaco)• David Nemith (Southern Union Panhandle)• Tom Marcotte (James Sewall Co.)• Lane Powell (ESRI)


History of the APDM• March 2002—M.J. Harden Associates, Inc., starts initial work on the

model. • July 2002—The model is presented at the ESRI User Conference in San

Diego, California. An open invitation to participate in the design of the model is extended to the pipeline community.

• August 2002—The initial meeting of interested member groups occurs at ESRI in Redlands, California.

• October 2002—The Steering and Technical Committees are officially formed at the ESRI Electric/Gas Utility User Group Conference, Coeur d’Alene, Idaho.

• December 2002–June 2003—Monthly Technical and Steering Committee meetings at various member organizations take place. Intellectual property agreement, Steering Committee charter, Technical Committee mandate, operational procedures, and APDM content and structure are developed.

• March 2003—The APDM is released for public comment at the ESRI PUG meeting, Houston, Texas.

• July 2003—Version 1 of the APDM is officially released at the ESRI User Conference, San Diego, California.

• October 2003 – First revision modeling session – EGUG – Galveston, TX


What is the APDM?• Data Model Designed for Geodatabase• Built From Published Data Models• Starting Point

• Not Comprehensive, Rather Suggestive• “Sophisticated, Yet Relaxed”

• 80 Percent Pipeline Company Rule• Hot Topics: HCA, In-Line Inspections, Risk,

Integrity, Operations, Right-of-way

• Core Elements


What is the APDM?THE ARCGIS PIPELINE DATA MODEL (APDM)

ESRI Defined Class*

Abstract Class ***

Defined subtypes

Wormhole toAbstract Class

(italicized)

Key

Property1Property2

ConcreteClass1 ConcreteClass2

Property1Property2

Wormhole toConcrete Class

(non-italicized)

Notes

Property1Property2

Types of Relationships

Binary Association -Relationship between exactly two

classes

Composite Aggregation -A whole/part relationship in which the

existence of the part is dependentupon the existence of the whole**

Simple Aggregation -A whole/part relationship in which

the existence of the part is notdependent upon the existence of the

whole

Generalization -A superclass/sublass relationship

in which the subclass inherits all ofthe properties of the superclass

Superclass

Subclass

PartWhole

Whole Part

** Composite Aggregation relationships involving linear features will be implemented as Simple Aggregationrelationships.*** Class Header Boxes colored gray are 'Events'. Events 'occur' along the centerline of a pipeline system.

ConceptualClasses

AreaTypeClassAreaEventID (PK)

HighConsequenceAreaStructureEventID (FK)DimensionTie1DimensionTie2EventID (PK)

StructureOutline

GeographicalUtilityTransportation

Contact

DaysOfWeekEventID (PK)OccupantCountStructureStatusStructureTypeWeeksPerYearYearAdded

Structure

ResidentialBusinessCivic

Address

Owner

Company/Operator

AnomalyClusterEventID (FK)BPRCalculatedBPRPigBPRVarianceDepthEventID (PK)InspectionRangeEventID (FK)LengthMaximumDiameterMinimumDiameterOrientationOvalityRecommendedRemediationRPRCalculatedRPRPigPRPVarianceWidth

Anomaly

External CorrosionInternal CorrosionDentGouge

AnomalyTypeAveBPRCalculatedAveBPRPigAveBPRVarianceAveDepthAveLengthAveMaximumDiameterAveMinimumDiameterAveOrientationAveOvalityAveRPRCalculatedAveRPRPigAvePRPVarianceAveWidthEventID (PK)

AnomalyClusterEventID (PK)InspectionDate

InspectionRange

Smart Pig RunCleaning Pig RunGeometry Pig RunLeak SurveyClose Interval SurveyVisual SurveyAerial SurveyExcavation

Contact

DateRepairedDateReportedDepthEventID (PK)LeakCauseLeakOriginLeakStatusMethodDetectedRepairType

Leak

EventID (PK)ReadingDateReadingUnitsReadingValueReadingFeatureEventID (FK)

Reading

ScadaCorrosion ControlClose Interval Survey

CPGroundBed

CPTestStation

PipeSegment

Meter

Valve

LastEventID (PK)

LastEvent

CompanyEventID (FK)ContactTypeEmailEventID (PK)FaxFirstNameLastNameMobilePagerPhone

ContactCompanyLabelCompanyNameCompanyTypeEventID (PK)

CompanyCityCountyCountryEventID (PK)StateProvinceStreet1Street2ZipPostalCode

AddressActivityDateActivityDescriptionActivityNameActivityParentEventID (FK)ActivityTypeEventID (PK)

Activity

EventID (PK)ActivityEventID (PK)Remarks

Activity

DocumentDescriptionDocumentTypeEventID (PK)FilePathFiletNameGeoMetaDataEventID (FK)

ExternalDocumentDPNameEventID (PK)

DocumentPointEventID (PK)SheetNameSheetNumberSheetType

AlignmentSheetAttributesBeginStationSeriesEventID (FK)BeginStationEndStationSeriesEventID (FK)EndStationEventID (PK)EventTypeProjectionIDRemovedDate

RemovedLineAttributesEventID (PK)EventTypeProjectionIDRemovedDateStationSeriesEventID (FK)Station

RemovedPoint

Last Revised: 10/09/2003 - Version 1.0Maintained by M.J. Harden Associates Inc./ESRI on behalf of the ESRI Pipeline Interest Group.Copyright 2002, 2003 Environment Systems Research Institute, Inc. Al l Rights Reserved.

Version 2.0 - Proposed

OBJECTID

Object

DateCollectedESRIProjectionIDEventID (PK)OriginalXOriginalYOriginalZPointEventID (FK)PositionSource

GeoMetaData

ExternalDocument

ControlPointAngleControlPointTypeEventID (PK)PIDirectionReferenceUnitsStationingValueStationSeriesEventID (FK)SymbolRotation

ControlPoint

ContinuousEngineeringHorizontalMile PostPacesSlack ChainValveSectionUnspecified

Shape

Feature

BeginStationEndStationEventID (PK)LineLoopEventID (FK)ReferenceUnitsSeriesOrderSourceSeriesEventID (FK)SinkSeriesEventID (FK)

StationSeries

EventID (PK)LineNameLineTypeProduct

LineLoopCompanyEventID (FK)EventID (PK)LineLoopEventID (FK)OperatorPercentageOperatorType

OwnerOperatorshipEventID (PK)SubSystemNameEffectiveToEventIDEffectiveFromEventID

SubSystem

EventID (PK)ParentSubsystemEventID (FK)ChildSubsystemEventID (FK)

SubSystemHierarchyEventID (PK)ParentLineLoopEventID (FK)ChildLineLoopEventID (FK)

LineLoopHierarchyCompany

ESRI Class

APDM Core

Point Polyline (MAware)

APDM Core

CreatedByCreatedDateEffectiveFromDateEffectiveToDateGroupEventID (FK)LastModifiedModifiedByOriginEventID (FK)(EventID) (PK)RemarksOperationalStatus

Audit

OBJECTID

Object

Shape

Feature

APDMAbstractClass

ESRI Class

ESRI Class

BeginStationSeriesEventID (FK)BeginStation

OnlineStationSeries

APDMClasses

(OffsetDistance)(OffsetAngle)

Point Polyline Polygon

USER DEFINED FEATURECLASSES

FeatureClasses

EventID (PK)InServiceDateManufacturerModelNumberOfNegativesNumberOfAnodesOperatingAmpsOutOperatingVoltsOutPowerSourceRatedAmpsOutRatedVoltsOutRectifierStackTypeReplacedByDate

CPRectifierAnodeSpacingBackFillMaterialCPRectifierEventID (FK)EventID (PK)InServiceDateLocationDescriptionNumberOfAnodesWaterSystem

CPGroundBedAnodeMaterialAnodeTypeAnodeWeightCPGroundBedEventID (FK)EventID (PK)InServiceDate

CPAnodeBondTypeCriticalBondEventID (PK)InServiceDate

CPBondEventID (PK)InServiceDateTestStationType

CPTestStationCableCoatingCableSizeCableTypeColorCodeEventID (PK)InServiceDateNumberOfCablesOnlineStationSeriesEventID (FK)OnlineStation

CPCable

BeginStationSeriesEventID (FK)BeginStationOffsetAngleOffsetDistance

OfflinePointCathodicProtection

Polyline

Polygon

APDMClass

Encroachments

Online PointAPDMClass

MultiPoint APDMClass

Inspections

Event Support

Online Polyline

OBJECTID

Object ESRI Class

Attributes … (listed above)

Audit APDM AbstractClass

APDMCore Point Polyline Polygon

The ESRI Object Class is the highest object in the conceptual object model. Object Class models a TABLE whichcontains rows (or features). Each row in an object class has a unique identifier called ObjectID which is created andmaintained within ArcSDE.OBJECTID: System applied table-level unique identifier (Long Integer)

Offline polyline features may be located on the centerline by one or more ‘online polyline’ featuresrepresenting the intersection of the polygon by the centerline. Property parcels that are intersected bythe centerline would create ‘right of way’ ‘online polylines’.

Offline polyline features may be located on the centerline by one or more ‘online polyline’ features.The range of where a foreign pipeline encroaches within a certain distance of the centerline would becreated as a ‘online polyline’ or series of ‘online polylines’.

Offline point features may be located on the centerline by one or more ‘online point’ features. Astructure within 1000ft of one or more StationSeries would record one ‘online point’ feature at theclosest point on each StationSeries feature.

The APDM Audit Class is an abstract class containing attributes which are inherited by all APDMobjects. The Audit class attributes are:

CreatedBy: The ID of the user who added the row to the tableCreatedDate: The date/time stamp when the row was added to the tableEffectiveFromDate: The start date the event was placed ‘In Service’EffectiveToDate: The end date the event was ‘retired’, ‘removed’ or ‘abandoned’GroupEventID: ForeignKey used to link 2 or more features together as a single feature.LastModified: The date the row was last modifiedModifiedBy: The ID of the user who last modified the row in the tableOriginEventID: The parent ID of the feature this feature was created fromEventID: A globally unique Identifier for every 'event' or 'feature' in the systemRemarks: For general comments, tags, or descriptions.Status: Description of the current status of the object

Feature is an object class that contains geometrydenoting the class to be a FeatureClass. Geometry isstored in the Shape attribute. Points, Polylines andPolygons are the most common forms of geometry inthe APDM Model. Each child of the feature object willinherit the Shape attribute and become aFeatureClass.Shape: A BLOB containing a geometry object Offline features are primary located by XY and NOT by linear referencing or stationed

position. These features typically include landbase data.

A Geodatabase can store both features in featureclasses and events in object classes. A feature is arow containing actual geometry. An event is a row with virtual geometry either point or polyline. The

APDM allows storage of geographic events as features and events.

Point features are drawn at a specific measure (or distance) along a route. Polyline features start at aspecified measure along a route and then follow the route to a second specified measure. Both

polyline and point events are considered ‘spatially coincident’ with the route feature. The concept ofstationed position along a station series is directly analogous to the construct of measures and routes.

An online feature (or event) is located exactly on the centerline of the pipeline system. A onlinefeature can be a point feature or a polyline feature. Point features can be placed anywhere along

the length of a station series. Linear features can begin or end at any position along a station seriesand all intervening vertices between the begin/end point of the linear feature must be geometrically

coincident with the underlying station series. Geometrically coincident means that online linearfeatures and the underlying station series share the same vertices.

To become an ‘online’ feature - the feature is located by BOTH XY location AND M or Stationedposition along a station series or route. Referenced Point features are located by

'BeginStationSeriesEventID' and ‘BeginStation’ attributes. Referenced Polyline features below thisclass will inherit the 'end' attributes.

BeginStationSeriesEventID: ID of the route that the measured or referenced event occurs on.Station: The measure or station value along the route or station series the event occurs at. (the

position along the line from the start of the line)Note: Referenced features contain geometry and thus can also be located by the coordinate values

contained therein. However, Events to not contain geometry and therefore can only be located viameasure along a route..

An Online Point feature may contain offset distance and angle attributes to help locate anotherrelated feature for which the ‘online point’ feature contains reference information. The best example

of this is a Structure (offline point) has no reference information but has one or more ‘online point’features that store reference information and offset information by which the referenced location of

the structure can be determined.

SubSystem (Object Class - Table)

OwnerOperatorShip (Object Class - Table)

Activity (Object Class - Table)

ActivityEvent (Object Class - Table)

Address (Object Class - Table)

Company (Object Class - Table)

Contact (Object Class - Table)

LastEvent (Object Class - Table)

ExternalDocument (Object Class - Table)

GeoMetaData (Object Class - Table)

LineLoop (Object Class - Table)

Reading (Object Class - Table)

LineLoopHierarchy (Object Class - Table)

SubSystemHierarchy (Object Class - Table)

GeoDatabaseTransmission (Featuredataset)

CPCable (Polyline Feature Class)

CPAnode (Point Feature Class)

CPBond (Point Feature Class)

CPGroundBed (Point Feature Class)

CPRectifier (Point Feature Class)CPTestStation (Point Feature Class)

StationSeries (Polyline Feature Class - MAware)

ControlPoint (Point Feature Class)

LinearEncroachment (Polyline Feature Class)

LineCrossing (Point Feature Class)

Structure (Point Feature Class)

HighConsequenceArea (Polygon Feature Class)

StuctureOutline (Polygon Feature Class)

PipeSegment (Polyline Feature Class)

Casing (Polyline Feature Class)

Vessel (Point Feature Class)

Appurtenance (Point Feature Class)

Closure (Point Feature Class)

Coating (Polyline Feature Class)

Elbow (Point Feature Class)

Meter (Point Feature Class)NonStationedPipe (Polyline Feature Class)

PiggingStructure (Polyline Feature Class)

PipeJoinMethod (Point Feature Class)

Reducer (Point Feature Class)

Sleeve (Polyline Feature Class)

Tap (Point Feature Class)

Tee (Point Feature Class)

Valve (Point Feature Class)

InspectionRange (Polyline Feature Class)

Leak (Point Feature Class)

Anomaly (Point Feature Class)AnomalyCluster (MultiPoint Feature Class)

OperatingPressure (Polyline Feature Class)

SiteBoundary (Polygon Feature Class)

ElevationPoint (Point Feature Class)

FieldNote (Point Feature Class)

HCAClass (Polyline Feature Class)

Marker (Point Feature Class)

PressureTest (Polyline Feature Class)

RightOfWay (Polyline Feature Class)

RiskAnalysis (Polyline Feature Class)

DocumentPoint (Point Feature Class)

AlignmentSheet (Polygon Feature Class)

RemovedLine (Polyline Feature Class)

RemovedPoint (Point Feature Class)

Pipe_Topology (ESRI Topology)

Catalog View

ESRI TopologyPipe_Topology

FeatureClass RankStationSeries 1ControlPoint 1

Pipe Segment 2Online Referenced Line 5Online Referenced Point 5

Participating feature classes and ranks

Sample Topology RulesFeatureClass

Point Must be Covered By Line

Must Not OverlapMust Be Covered By Feature Class Of

Must Be Single PartPoint Must Be Covered By Line

Point Must Be Covered By LinePoint Must Be Covered By Line

FeatureClassStationSeries

Pipe Segment

Pipe Segment

Pipe SegmentPipe Segment

FeatureClassControlPoints

StationSeriesStationSeries

StationSeriesTap

TeeValve

Event (Object)

Some ‘offline point’ feature MAY contain a single reference to a station series viastationed position and offset distance and angle. Cathodic protection devices that servea single mainline fall into this category.

Station Series form the ROUTES which are used to locate all referencedevents/features on or along the pipeline system. StationSeries are MAwarePolyline features. StationSeries have one or more subtypes each representinga alternate reference measurement (or Stationing) system.

ControlPoints represent “known points of stationing at a specific XY location”along the pipeline. Two or more ControlPoints represent the vertices of aStationSeries feature for the same subtype (Measurement System). EachControlPoint will have a single station value representing the measure value atthe vertex of the StationSeries on which the ControlPoint is located.

LineLoop represents one level of hierarchy or organization of StationSeriesfeatures in the APDM. A LineLoop typically represents a mainline or a branchand can be comprised of one or more StationSeries features.

CoatingConditionCoatingLengthCoatingLocationCoatingMaterialCoatingMillCoatingSourceEventID (PK)InServiceDateInternalCoating

CoatingEventID (PK)GradeInServiceDateNominalDiameterSleeveLengthSleeveTypeWallThickness

SleeveCasingLengthCrossingTypeEventID (PK)FilledInServiceDateInsulatorTypeOutsideDiameterSealTypeShortedVentedWallThickness

CasingAppurtenanceTypeEventID (PK)InServiceDate

AppurtenanceEventID (PK)InServiceDateManufacturerSerialNumberVesselType

Vessel

DiameterEventID (PK)InServiceDatePipeTypeWallThickness

NonStationedPipeBarrelDiameterBarrelGradeBarrelWallThicknessEventID (PK)InServiceDateManufacturerMaterialStructureLengthPressureRating

PiggingStructure

LauncherReceiver

BendRadiusDateManufacturedEventID (PK)GirthWeldGradeInletWallThicknessInServiceDateLongitudinalSeamManufacturerMaterialMillLocationMillTestPressureOutsideDiameterOutletWallThicknessPipeTypePreTestedPressureRatingSegmentLengthSpecification

PipeSegment

PipeBendTransition

DateManufacturedGradeInletConnectionTypeInletDiameterInletWallThicknessInServiceDateManufacturerMaterialPressureRatingSpecification

Fitting

EventID (PK)MeterFunctionMeterNameMeterNumberMeterTypeRemoteNetworkedSerialNumber

MeterElbowAngleElbowRadiusEventID (PK)

ElbowBranchConnectionTypeBranchDiameterBranchWallThicknessEventID (PK)ScaperBarsTeeSizeTeeType

Tee

Full On TeeTapping TeeSplit TeeWide Open Tee

OutletConnectionTypeOutletDiameterOutletWallThicknessEventID (PK)ReducerSizeReducerType

ReducerClosureTypeEventID (PK)

Closure

AutomatedEventID (PK)InletConnectionTypeInletDiameterInServiceDateManufacturerNormalPositionOperatorTypeOutletConnectionTypeOutletDiameterPresentPositionPressureRatingValveFunctionValveNumber

Valve

Angle ValveBall ValveBlock ValveCheck ValveControl ValveCurb ValveGate ValvePlug Valve

EventID (PK)InServiceDateInsulatedJoinTypeManufacturerPressureRating

PipeJoinMethod

WeldCouplingFlangeScrewElectro Stop

BranchConnectionTypeCapacityCapacityUnitsCappedEventID (PK)FlowDirectionInServiceDateManufacturerMeteredPressureRatingTapSizeTapTypeTappingMethod

Tap

Tap FittingTap Fabrication

Facilities Online PointOnline Polyline APDMClassAPDMClass

APDMAbstractClass

APDMCore

Polyline

EventID (PK)FieldNoteType

FieldNote

CulturalEnvironmentalFacilityGeoPoliticalHydrologyLine CrossingOperationsRoutingTransportation

GeoMetaData

EventID (PK)FeatureElevationGroundElevationMeasurementDateWaterElevation

ElevationPointEventID (PK)InServiceDateMarkerNumber

Marker

Mile PostAerial MarkerMonumentSurvey PointPig Signal (AGM)

EventID (PK)SiteNameSiteType

SiteBoundaryClassTypeClassSourceClassLengthEventID (PK)

HCAClassEventID (PK)MinAdjustedPressureMinDesignPressurePreTestTestDateTestDurationTestMediumTestNameTestType

PressureTestConsequenceEconomicConsequenceEnvironmentalConsequenceLifeConsequencePropertyEventID (PK)POFConstructionPOFInternalCorrosionPOFMaterialsPOFOutsideForcePOFThirdPartyTotalConsequenceTotalPOFTotalRisk

RiskAnalysisActualPressureAgreedToPressureCalculatedPressureEventID (PK)PressureTypeVerifiedByEventID (FK)

OperatingPressure

Contact

EasementWidthEventID (PK)ParcelNumberROWTypeTraverseLength

RightOfWay

Address

LineLoop

OperationsOffline Point APDMClass Online Polyline APDMClass Polygon

Facility feature classes model the physicalappurtenances or devices found on or along a

pipeline system.

Cathodic Protection feature classes model the devices used to monitor and prevent corrosionfrom occurring to other facilities on or along the pipeline system.

CPRectifier, CPGroundBed, CPAnode, CPTestStation, CPBond are all Offline Features thathave a single onl ine location.

CPCable may or may not have a single end connected-to or located-on the centerline.

Encroachment feature classes model any physicalfeature or boundary that might impact the operationand/or regulated safety compliance of the pipeline

system.

LineCrossings represent linear features that intersectthe centerline and therefore must have one or more

LineCrossingLocations (Online Points).

Structures are Offline Points that may have zero ormore StructureLocations (Online Points) on zero ormore centerlines typically within 1000 feet (304.8

meters) of the structure.

Inspection feature classes model the results ofin-line or physical inspection of the pipeline for

anomalies, corrosion and other possiblehazards or defects.

Event Support feature and object classes contain the meta-data, reports,documents, and customer/contact information that pertain to the regulation

and operation of the pipeline system.

Operational feature classes model terrain,survey, pressure testing, right-of-way,

operations and installations information on oralong the pipeline system.

Control Point and Station Serieshave the same subtypes which areused to differentiate betweendifferent forms of stationing (linearreferencing).

SymbolRotation(OffsetDistance)(OffsetAngle)

PointEndStationSeriesEventID (FK)EndStation

Polyline

(BeginStationSeriesEventID)(BeginStation)

OfflineFeatures onthe Centerline

Features not onthe Centerline

ESRI Class

Centerline

APDMClass

Polyline

ClearanceCrossingTypeEventID (PK)LinearEncroachmentTypeNameOrientation

LineCrossing

Online Point

EventID (PK)LineCrossingEventID

LineCrossingLocationEventID (PK)LineCrossingEventID

StructureLocation

Point

ESRI ClassESRI ClassESRI Class

ESRI ClassInspectionRange

BeginStationSeriesEventID (FK)BeginStationOffsetAngleOffsetDistance

Each implementation of the APDM can take the conceptual classes and derive more specializedfeature and object classes that meet the business requirements of the organization.


What is the APDM?• Standard Versus Template• PODS—Pipeline Open Data System• ISAT—Integrated Spatial Analysis

Technology• ISPDM—Industry Standard Pipeline Data

Management• Relational Database Management Systems• Object-Relational Systems: Geodatabase


Linear Referencing (What !?!)• Station Series

• Connected linear features• Contain stationing information• Station Series = Route• Station Equations• All referenced features relate to one and only

one Station Series (Route)


Stat

ion

Serie

s 1

(Rou

te)

Station

Series 2

(Rou

te)

Station Equation

0+00

100+00

225+00

400+00

250+00

600+00

200+00

-SubTypeCD : esriFieldTypeInteger = 1Centerline_Subtypes::Continuous

-SubTypeCD : esriFieldTypeInteger = 2Centerline_Subtypes::Engineering

-SubTypeCD : esriFieldTypeInteger = 3Centerline_Subtypes::Horizontal

-SubTypeCD : esriFieldTypeInteger = 4Centerline_Subtypes::Milepost

-SubTypeCD : esriFieldTypeInteger = 5Centerline_Subtypes::Slack Chain

-SubTypeCD : esriFieldTypeInteger = 7Centerline_Subtypes::Unspecified

-SubTypeCD : esriFieldTypeInteger = 6Centerline_Subtypes::Valve Section

-BeginStation : esriFieldTypeDouble = 0.00-EndStation : esriFieldTypeDouble = 0.00-EventID : esriFieldTypeString-LineLoopEventID : esriFieldTypeString-ReferenceUnits : clReferenceUnits = 1«SubtypeField» -SubTypeCD : esriFieldTypeInteger = 7-SourceSeriesEventID : esriFieldTypeString-SinkSeriesEventID : esriFieldTypeString-SeriesOrder : esriFieldTypeInteger

StationSeries{GeometryType = esriGeometryPolyline,

HasM = True,HasZ = False}


Linear Referencing• Control Points

• Point feature representing:• Known XY location (GPS, Monument, Line Crossing)• Known stationed position (Historic Stationing)• Point of Inflection (Horizontal/Vertical bend)

• Control Points are vertices and end points of station series

• Same subtypes as Station Series• Each control point has one station values

associated with it.


-ControlPointAngle : esriFieldTypeString-ControlPointType : clControlPointType = 1-EventID : esriFieldTypeString-PIDirection : clControlPointDirection = 1-ReferenceUnits : clReferenceUnits = 1-StationingValue : esriFieldTypeDouble = 0.00-StationSeriesEventID : esriFieldTypeString«SubtypeField» -SubTypeCD : esriFieldTypeInteger = 7-SymbolRotation : gnAngle = 0.00

ControlPoint{GeometryType = esriGeometryPoint,

HasM = True,HasZ = False}

-SubTypeCD : esriFieldTypeInteger = 1Centerline_Subtypes::Continuous

-SubTypeCD : esriFieldTypeInteger = 2Centerline_Subtypes::Engineering

-SubTypeCD : esriFieldTypeInteger = 3Centerline_Subtypes::Horizontal

-SubTypeCD : esriFieldTypeInteger = 4Centerline_Subtypes::Milepost

-SubTypeCD : esriFieldTypeInteger = 5Centerline_Subtypes::Slack Chain

-SubTypeCD : esriFieldTypeInteger = 7Centerline_Subtypes::Unspecified

-SubTypeCD : esriFieldTypeInteger = 6Centerline_Subtypes::Valve Section


Stat

ion

Serie

s 1

(SS1

)Station

Series 2

(SS2)

CP1, SS1, 0+00, Slack ChainCP1, SS1, 2.3, Mile PostCP1, SS1, 34+00, Historical

CP2

225+00

400+00

250+00

600+00

CP1

CP3CP4

CP5

CP6

CP2, SS1, 100+00,Slack ChainCP2, SS1, 3.9, Mile PostCP2, SS1, 750+00, Historical


CP4, SS1, 225+00, Slack ChainCP4, SS2, 250+00, Slack ChainCP4, SS1, 7.9, Mile PostCP4, SS1, 1356+00, HistoricalCP4, SS2, 7.9, Mile Post

200+00

100+00

0+00




Rout

e 1

Rou

te 2

Measure 225

Measure 250

Measure 600

Measure 200

Measure 100

Measure 400

Measure 0


Core Model• All features in APDM are one

of six defined types; online point, online polyline, offline point, offline polyline, offline polygon, core element

• Features are ‘referenced’ by the centerline or they are not referenced

• Features have inherent absolute position• Events are generated solely on relative position• All ‘events’ or ‘features’ must have globally

unique indentifier: EventID• EventID is used for all relates.


Online Point/Polyline• Point or Linear Feature• Geometrically constrained to centerline• Begin/End position located by stationing• Participates in Topology

Station Series

Measure 225

Measure 100

Measure 0

Pipe SegmentValve

Reducer

ClosureControl Point

Closure – StationSeriesEventID 235, Station 0+00

PipeSegment BeginStationSeriesEventID 235, BeginStation 0+00EndStationSeriesEventID 235, EndStation 30+00

Valve – StationSeriesEventID 235, Station 30+00


Valve – StationSeriesEventID 235, Station 165+00


Reducer – StationSeriesEventID 235, Station 225+00


Online Point/Polyline

Station Series

Measure 225

Measure 100

Measure 0CoatingPressure Test

Leak

Control Point

PressureTest BeginStationSeriesEventID 235, BeginStation 5+00EndStationSeriesEventID 235, EndStation 125+00

Coating BeginStationSeriesEventID 235, BeginStation 115+00EndStationSeriesEventID 235, EndStation 165+00

Leak StationSeriesEventID 235, Station 195+00

Coating BeginStationSeriesEventID 235, BeginStation 25+00EndStationSeriesEventID 235, EndStation 55+00


Offline Point/Polyline/Polygon• Point, Linear or Polygonal Feature• Usually exists off the centerline• Does not participate in Topology

Station Series

Measure 225

Measure 100

Measure 0

Reference Line

HCA AreaStructure

Control Point

HCA Area BeginStationSeriesEventID 235, BeginStation 15+00Offset Angle 75’, Offset Distance 200ft, Offset Side: RightEndStationSeriesEventID 235, EndStation 65+00Offset Angle 90’, Offset Distance 175ft, Offset Side: Right

Structure StationSeriesEventID 235, Station 135+00,Offset Angle 135’, Offset Distance 85 ft, Offset Side: Right

Structure StationSeriesEventID 235, Station 95+00, Offset Angle 90’, Offset Distance 125ft, Offset Side: Left


Offline Point/Line/Polygon• Pass-through Polygons, Transportation

Networks, Hydrology, Environmental, Operational, and Cultural features

• Object Classes• Activities, External Documents, GeoMetaData,

Contacts, Companies etc.

Measure 225

Measure 100

Measure 0Grea

t Western

Railway

Parcels

Station Series

Operating Areas


Model Tour: Centerline• Objects that form the centerline• Linear Referencing Mechanism

• StationSeries – routes of stationing, contains hierarchy information

• ControlPoint – points of known station position, PI’s• LineLoop – a collection of station series that

comprise a single ‘line’• GeoMetaData – source information for control points• OwnerOperatorship – Line Loop owner/operator

percentages


Model Tour: Facility• Physical elements that comprise Pipeline

• Coating (PLFc), Sleeve (PLFc), Casing (PLFc), Appertenance (PtFc), Vessel (PtFc)

• NonStationedPipe (PLFc), PiggingStructure (PLFc)• Pipe Segment (PLFc), Valve (PtFc), Fittings (Meter,

Elbow, Tee, Reducer, Closure) (PtFc), PipeJoinMethod (PtFc), Tap (PtFc)


Model Tour: Inspection• Inspection and Integrity• Generic classes• Huge variance in applications and data

• Anomaly (PtFc) – anomaly or deformity in pipe• AnomalyCluster (mPtFc) – cluster of anomalies• InspectionRange (PLFc) – linear inspection – eg.

Leak Survey, Inline PIG Run, Aerial Survey, Close Interval Survey


Model Tour: Operations• Regulatory and Operations

• On or Offline Referenced• FieldNote (PtFc) – Field Data Collection• ElevationPoint (PtFc) – ground, pipe water

elevations• Marker (PtFc) – monuments, Mile Posts, PIG Signals• SiteBoundary (POFc) – Meter Stations, Compressor

Stations, Easements etc.• HCAClass (PLFc), PressureTest (PLFc), RiskAnalysis

(PLFc), OperatingPressure (PLFc), RightOfWay(PLFc)


Model Tour: Cathodic• Corrosion Management• Kept generic• Based on Distribution Model

• On or OffLine Referenced• CPRectifier (PtFc)• GPGroundBed (PtFc)• CPAnode (PtFc)• CPBond (PtFc)• CPTestStation (PtFc)• CPCable (PLFc)


Model Tour: Encroachments• Encroachments on the pipeline• Encroachments within the Class

Corridor• HighConsequenceAreas (POFc), StructureOutlines

(POFc)• LineCrossing (PtFc)• LinearEncroachment (PLFc), Structure (PtFc)


Model Tour: Event Support• Object Classes to support:

• History, Mapping, Documentation• Activity (OC) – any activity that occurs• ActivityEvents (OC) – events that are part of an

activity• AlignmentSheet (POFc) – sheet boundary and info• Company (OC) – companies, contractors, divisions• Contact (OC) – any person in the system• DataSet (OC) – FeatureDataSet MetaData• DocumentPoint (OC) – multi-hyperlinked feature• ExternalDocument (OC) – source document links• GeoMetaData (OC) – point source meta data• RemovedLine/Point (PL/PTFc) – removed features• LastEventID (OC)– holds the last EventID


Top Ten Reasons to use APDM

From the home office in Waverly, Iowa ……

The top ten reasons for using the ArcGIS Pipeline Data Model to implement your Gas/Liquids Transmission Pipeline Geographic Information System

(What, and Why)


Scalable

FAST Data Access

Transactions

SubTypes

Relationships

Domains

Geometry Model

ArcObjects

• APDM is built on ESRI Geodatabase• Leader in GIS Software• Highly functional, easy-to-use off-the-shelf GIS software• Powered for the enterprise by ArcSDE …• Flexible Object-Relational Data Model that provides …

• Both referential and spatial integrity• Enforced link between features and attributes• Complex relationships, multiuser long transactions,

security, scalability, topology, extended object behavior, geoprocessing, raster-based analysis, state-of-the-art map display and cartographic production, web integration, disconnected editing

• “ESRI is the 'epicenter' of what is happening in GIS now and in the future.” David McGuire, ESRI

Security

Multi-User

Top Ten Reasons to use APDMRDBMSTCP/IP


• APDM is a model with a simple core …• Station Series, Control Points, Line Loops, Pipe

Segments, Online Points, Online Polylines, Offline Points

• APDM is a data model that can be that can be readily expanded with object behavior … complex potential and possibilities … you define behavior!

Alignment SheetAnomaly

AnomalyClusterAppurtenance

AnodeBond

CableGround Bed

RectifierTest Station

CasingClosure

CoatingDocument Point

ElbowElevation Point

Field NoteHCAClass

High ConsequenceInspection Range

LeakLine CrossingEncroachments

Meter

Non Stationed PipeOperating Pressure

Pigging StructurePipe JointPressure Test

ReducerRemoved Line

Removed PointRight of Way

Risk AnalysisSite Boundary

SleeveStructure

Structure OutlineTap

TeeValve

Vessel



Top Ten Reasons to use APDM• APDM can store both features and events

• Features are static geometry contained in the row that describes the feature

• Events are ‘dynamic’ geometry that are generated from a specified route and measured position along the route

• Features are excellent for modeling facilities and permanent features on or along a pipeline

• Events are excellent for modeling dynamically segmented features, the results of analysis, and ephemeral features such as inspections, anomalies, risk analysis, pressure tests


Top Ten Reasons to use APDM• APDM translates to-from existing pipeline

RDBMS data models …• PODS—Pipeline Open Data System• ISAT—Integrated Spatial Analysis Technology• ISPDM—Industry Standard Pipeline Data Management

• Similar core features: • Centerline (Control Points, Station Series, Routes)• Online/Offline Referenced Features (Pipes, Valves etc.)• Hierarchy (Station Series, Line Loop etc.)

• All Pipeline models incorporate stationing (Route/Measure & Centerline) as mechanism for linear referencing


Top Ten Reasons to use APDM• APDM is a true GIS model …

• Geometry stored as features in relative and absolute spatial position to other features

• Out-of-the-box data maintenance• Out-of-the-box data analysis• MAPS

• If a picture is worth a 1000 words then a map is worth a 1000000 words …


Top Ten Reasons to use APDM• A Template not a Standard• Open Model – Extendable• Works w/ ArcGIS/ArcSDE 8.3 (OOB)

• Designed for the GeoDatabase• Built from published data models• Starting Place to build Enterprise GIS

• Not comprehensive, rather suggestive• “Relaxed yet sophisticated”• 80% Pipeline Companies Implement RULE• Hot Topics: HCA, Inline Inspection, Integrity,

RISK


Top Ten Reasons to use APDM• Integrated Enterprise Solution• Geodatabase – Versioning – Work Flow• RDBMS Core – relates to external systems• GIS Core – features to attributes• Applications

APDM

PODS

ISAT

DW

II


Top Ten Reasons to use APDM• Data Maintenance

• Topology, Snapping, Relationship Classes, Subtypes, Domains

• Spatial Analysis• Buffer, Overlay, Intersection, Proximity,

Distance, Visualization (2D, 3D, Animated), Business, Routing

• Mapping and Reporting• RDBMS server• Views• Stored Procedures



Petroleum

• Part of ESRI Model Family

Petroleum

Gas Distribution

Geology

Transportation

Cadastral

Street Centerline

Right of Way Census

Environmental



• COOL• Cost effective• Object Oriented• Linear Referenced Data Model

• GIS Driven• Feature Driven• Enterprise Driven


The Future of APDM• Regular meetings

• ESRI Electric and Gas Utility User Group Meeting (September/October)• ESRI Petroleum User Group Meeting (March)• APDM User Group Meeting at the ESRI User Conference (July/August)

• Elected positions on the Steering and Technical Committees

• More information?• M.J. Harden and ESRI Booths


More Information• ESRI Web Site: www.esri.com\petroleum

• UML Model—APDM_V1.vsd (Visio 2002 format) AVAILABLE (PUG Members)

• XMI Repository—APDM_V1xmi.xml (requires uml.dtd)AVAILABLE (PUG Members)

• White Paper—APDMWhitePaper.pdf (Adobe Acrobat)AVAILABLE (Open)

• Logical Model (Visio 2002 format, PowerPoint)AVAILABLE (Open)

• Security and Privacy Issues With Sample Data


DisclaimerTHIS PRESENTATION AND RELATED MATERIALS ARE PROVIDED TO THE ARCGIS

PIPELINE DATA MODEL USER GROUP MEETING "AS IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED INCLUDING, BUT NOT LIMITED TO,

WARRANTIES OF PERFORMANCE, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. PARTICIPANTS IN THE ARCGIS PIPELINE DATA MODEL USER GROUP MEETING BEAR ALL RISK AS TO THE QUALITY AND PERFORMANCE OF THE

PRESENTATION, SOFTWARE, AND RELATED MATERIALS.

[email protected]

Thank you!

Implementing theArcGIS Pipeline Data Model (APDM)Introduction (Who)APDM (Who)APDM (Who)APDM (Who)History of the APDMWhat is the APDM?What is the APDM?What is the APDM?Linear Referencing (What !?!)Linear ReferencingCore ModelOnline Point/PolylineOnline Point/PolylineOffline Point/Polyline/PolygonOffline Point/Line/PolygonModel Tour: CenterlineModel Tour: FacilityModel Tour: InspectionModel Tour: OperationsModel Tour: CathodicModel Tour: EncroachmentsModel Tour: Event SupportTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMTop Ten Reasons to use APDMThe Future of APDMMore InformationDisclaimer