ArcGIS Pipeline Data Model (APDM) - s3.amazonaws.com · ArcGIS Pipeline Data Model (APDM) ......

ESRI Petroleum User Group 2003ESRI Petroleum User Group 2003ESRI Petroleum User Group 2003 ArcGIS Pipeline Data ModelArcGIS ArcGIS Pipeline Data ModelPipeline Data Model

ArcGIS Pipeline Data Model (APDM)

Workshop Presentation

ArcGIS Pipeline Data Model (APDM)

Workshop Presentation

Jay SmithM.J. Harden Associates

Jay SmithM.J. Harden Associates


OutlineOutline

• Introductions• The Model

• History, The Future, Objectives, Present• Core Elements

• Station Series, Control Points, Stationing• Model Objects

• Tour of the Model• Centerline, Facility, Inspection, Operations, Cathodic,

Event Support

• Implementation Issues• Questions and Answers

• Introductions• The Model

• History, The Future, Objectives, Present• Core Elements

• Station Series, Control Points, Stationing• Model Objects

• Tour of the Model• Centerline, Facility, Inspection, Operations, Cathodic,

Event Support

• Implementation Issues• Questions and Answers

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


The ModelThe Model

• A template with core tables and attributes

• Core elements are absolute• Rest of model is totally configurable &

customizable• Designed to be implemented as ESRI

GeoDatabase• Can be an ‘event-based’ or ‘feature-based’

model

• A template with core tables and attributes

• Core elements are absolute• Rest of model is totally configurable &

customizable• Designed to be implemented as ESRI

GeoDatabase• Can be an ‘event-based’ or ‘feature-based’

model

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


HistoryHistory

• ESRI Pipeline Interest Group (PIG)• PIG Technical Committee• 1 year of effort (March 2002)• 7 meetings since August 2002• Utilize the common/best elements of

published pipeline models (PODS/ISAT)• 75 Feature Classes to 45 Feature Classes• Developed for ESRI GeoDatabase

• ESRI Pipeline Interest Group (PIG)• PIG Technical Committee• 1 year of effort (March 2002)• 7 meetings since August 2002• Utilize the common/best elements of

published pipeline models (PODS/ISAT)• 75 Feature Classes to 45 Feature Classes• Developed for ESRI GeoDatabase

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


HistoryHistory

• Technical Committee Members:• Scott Hills – Chevron Texaco• Theo Lawrence – Great Lakes Gas Trans.• Tom Marcotte – James Sewall Company• Buddy Nagel – El Paso Corporation• David Nemeth – Southern Union Panhandle• Lane Powell - ESRI• Jay Smith – M.J. Harden Associates Inc.• Fred Spickler – PhotoScience Inc.• Tracy Thorleifson – Eagle Information Mapping• Peter Veenstra – M.J. Harden Associates Inc.

• Technical Committee Members:• Scott Hills – Chevron Texaco• Theo Lawrence – Great Lakes Gas Trans.• Tom Marcotte – James Sewall Company• Buddy Nagel – El Paso Corporation• David Nemeth – Southern Union Panhandle• Lane Powell - ESRI• Jay Smith – M.J. Harden Associates Inc.• Fred Spickler – PhotoScience Inc.• Tracy Thorleifson – Eagle Information Mapping• Peter Veenstra – M.J. Harden Associates Inc.

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


FutureFuture

• Designed for ArcGIS 8.2• Version 1.0 Beta released now• Focus on ArcGIS 8.3 until July 2003

• Topology• Advanced Linear Referencing Tools

• Version 1.0 released at ESRI UC 2003• Two review sessions yearly (EGUG and

PUG)

• Designed for ArcGIS 8.2• Version 1.0 Beta released now• Focus on ArcGIS 8.3 until July 2003

• Topology• Advanced Linear Referencing Tools

• Version 1.0 released at ESRI UC 2003• Two review sessions yearly (EGUG and

PUG)

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


The Model – ObjectivesThe Model – Objectives

• Common framework for implementing Transmission Pipeline GeoDatabases

• Handle linear referencing (Stationing)• Handle absolute positioning (X,Y)• Utilize ESRI Technology

• Routes, measures, events, feature classes, subtypes, relationship classes, domains etc.

• Develop starting place• For organizations to build models• For vendors to develop applications

• Common framework for implementing Transmission Pipeline GeoDatabases

• Handle linear referencing (Stationing)• Handle absolute positioning (X,Y)• Utilize ESRI Technology

• Routes, measures, events, feature classes, subtypes, relationship classes, domains etc.

• Develop starting place• For organizations to build models• For vendors to develop applications

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


The PresentThe Present

• Huge variation in how data is modeled from pipeline company to pipeline company

• Model developed according to two guidelines:•What do 80% of pipeline companies require•What is absolutely required by government regulations (FERC, DOT, etc.)

• Model presented for review• Need feedback

•What is missing – technology, implementation?

• Huge variation in how data is modeled from pipeline company to pipeline company

• Model developed according to two guidelines:•What do 80% of pipeline companies require•What is absolutely required by government regulations (FERC, DOT, etc.)

• Model presented for review• Need feedback

•What is missing – technology, implementation?

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


Core ModelCore Model

• Station Series• Control Points• Stationing• Model Objects

• Online Referenced Networked• Online Referenced Non-Networked• On or Offline Referenced• Not Referenced• Object Class• Core Elements

• Station Series• Control Points• Stationing• Model Objects

• Online Referenced Networked• Online Referenced Non-Networked• On or Offline Referenced• Not Referenced• Object Class• Core Elements

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Core Model: Station SeriesCore Model: 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)• Participate in Geometric Network with

control points

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

only one Station Series (Route)• Participate in Geometric Network with

control points

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Core Model: Station SeriesCore Model: Station SeriesIntroduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core

Statio

n Ser

ies

1 (Route

)

Station

Series 2

(Rou

te)

Station Equation

0+00

100+00

225+00

400+00

250+00

600+00

-EventID : esriFieldTypeInteger-Hierarchy1 : esriFieldTypeString-Hierarchy2 : esriFieldTypeString-Hierarchy3 : esriFieldTypeString-LineLoopEventID : esriFieldTypeInteger-SeriesType : roStationSeriesPipeType = 1«SubtypeField» -SubTypeCD : esriFieldTypeInteger = 1

StationSeries{GeometryType = esriGeometryPolyline,

HasM = True,HasZ = False}

-SubTypeCD : esriFieldTypeInteger = 1

Subtypes::Series

200+00


Core Model: Control PointsCore Model: 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

• Subtyped as: End Points or Internal Points• Each control point has one or more station

values associated with it

• 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

• Subtyped as: End Points or Internal Points• Each control point has one or more station

values associated with it

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Core Model: Control PointsCore Model: Control PointsIntroduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core

-ControlPointAngle : esriFieldTypeString-ControlPointType : roControlPointType = 1-EventID : esriFieldTypeInteger-PIDirection : roControlPointDirection = 1«SubtypeField» -SubTypeCD : esriFieldTypeInteger = 1

ControlPoint{AncillaryRole = esriNCARNone,

GeometryType = esriGeometryPoint,HasM = False,HasZ = False}

-SubTypeCD : esriFieldTypeInteger = 1Subtypes::InternalPoint

-SubTypeCD : esriFieldTypeInteger = 2Subtypes::EndPoint

+FieldType = esriFieldTypeInteger+MergePolicy = esriMPTDefaultValue+SplitPolicy = esriSPTDefaultValue+PI = 1+Known Point = 2+GPS Point = 3+Monument = 4+Crossing Location = 5+Unknown (Verified) = 6+Unknown = 7

«CodedValueDomain»Centerline_Domains::roControlPointType

End Point

End Point

End Point

Internal Point

Internal Point

Internal Point


Core Model: StationingCore Model: Stationing

• Stored in object class (ITable)• Station values along station series

(measures along route) at a single control point

• Relates to one station series and one control point

• A control point can have one or more station values

• Stored in object class (ITable)• Station values along station series

(measures along route) at a single control point

• Relates to one station series and one control point

• A control point can have one or more station values

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Core Model: StationingCore Model: StationingIntroduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core

Statio

n Ser

ies

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




Core Model: StationingCore Model: StationingIntroduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core

-ControlPointAngle : esriFieldTypeString-ControlPointType : roControlPointType = 1-EventID : esriFieldTypeInteger-PIDirection : roControlPointDirection = 1«SubtypeField» -SubTypeCD : esriFieldTypeInteger = 1

ControlPoint{AncillaryRole = esriNCARNone,

GeometryType = esriGeometryPoint,HasM = False,HasZ = False}

-EventID : esriFieldTypeInteger-Hierarchy1 : esriFieldTypeString-Hierarchy2 : esriFieldTypeString-Hierarchy3 : esriFieldTypeString-LineLoopEventID : esriFieldTypeInteger-SeriesType : roStationSeriesPipeType = 1«SubtypeField» -SubTypeCD : esriFieldTypeInteger = 1

StationSeries{GeometryType = esriGeometryPolyline,

HasM = True,HasZ = False}

-ControlPointEventID : esriFieldTypeInteger-EventID : esriFieldTypeInteger-StationSeriesEventID : esriFieldTypeInteger-StationingType : roReferenceMeasureType = 1-StationingValue : esriFieldTypeDouble = 0.00

Event_Support::Stationing

+FieldType = esriFieldTypeInteger+MergePolicy = esriMPTDefaultValue+SplitPolicy = esriSPTDefaultValue+As-Built Slope-Chain Station = 1+As-Built Horizontal Station = 2+Milepost based on Slope-Chain Station = 3+Milepost based on Horizontal Station = 4+3D Distance from Beginning of Discharge = 5+Engineering Stationing = 6+Unknown = 7

«CodedValueDomain»Centerline_Domains::roReferenceMeasureType

-NetworkType : esriNetworkType = esriNTUtilityNetwork

«GeometricNetwork»Routing_GeoNet


Core Model: StationingCore Model: Stationing

Route

1

Rou

te 2Measure 225

Measure 250

Measure 600

Measure 200

Measure 100

Measure 400

Measure 0

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Core ModelCore Model

• All features in GeoDatabase are one of six defined model types

• All referenced features must relate toa station series feature for relative

positioning• 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.

• All features in GeoDatabase are one of six defined model types

• All referenced features must relate toa station series feature for relative

positioning• 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.

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Core Model: Model ObjectsCore Model: Model Objects

• Online Referenced Networked (ORN)• Point

• StationSeriesEventID, Station• Line

• Begin/EndStationSeriesEventID, Begin/End Station

• Online Referenced Not-Networked (ORNN)• Point/Line

• As above

• On or Offline Referenced (OOR)• Point

• OffsetDistance, OffsetAngle, OffsetSide• Line

• Begin/End Offset – Distance/Angle/Side

• Not Referenced (NR)

• Online Referenced Networked (ORN)• Point

• StationSeriesEventID, Station• Line

• Begin/EndStationSeriesEventID, Begin/End Station

• Online Referenced Not-Networked (ORNN)• Point/Line

• As above

• On or Offline Referenced (OOR)• Point

• OffsetDistance, OffsetAngle, OffsetSide• Line

• Begin/End Offset – Distance/Angle/Side

• Not Referenced (NR)

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


Core Model: DefinitionsCore Model: Definitions

• Referenced – position on or along thecenterline can be determined by station series and station value

• Online – feature or event is ‘geometrically constrained’ to the edge of a station series feature

• Networked – online referenced feature that participates in Geometric Network

• Offline – referenced feature that is located off of the centerline

• Referenced – position on or along thecenterline can be determined by station series and station value

• Online – feature or event is ‘geometrically constrained’ to the edge of a station series feature

• Networked – online referenced feature that participates in Geometric Network

• Offline – referenced feature that is located off of the centerline

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


Core Model: ORNCore Model: ORN

• Online Referenced Networked Feature• Point or Linear Feature• Geometrically constrained to centerline• Begin/End position located by stationing• Participates in a Geometric Network

• Pipes, Valves, Reducers, Closures

• Online Referenced Networked Feature• Point or Linear Feature• Geometrically constrained to centerline• Begin/End position located by stationing• Participates in a Geometric Network

• Pipes, Valves, Reducers, Closures

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A

Station SeriesMeasure 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


Core Model: ORNNCore Model: ORNN

• Online Referenced Not-Networked• Point or Linear Feature

• Geometrically constrained to centerline• Does not participate in Geometric Network

• Leaks, Pressure Tests, Coating

• Online Referenced Not-Networked• Point or Linear Feature

• Geometrically constrained to centerline• Does not participate in Geometric Network

• Leaks, Pressure Tests, Coating

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


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


Core Model: OORCore Model: OOR

• On or Offline Referenced• Point or Linear Feature• Usually exists off the centerline• Does not participate in Geometric Network

• Structures, Ground Beds, HCA Areas

• On or Offline Referenced• Point or Linear Feature• Usually exists off the centerline• Does not participate in Geometric Network

• Structures, Ground Beds, HCA Areas

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A


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


Core Model: OtherCore Model: Other

• Not Referenced• Pass-through Polygons, Transportation

Networks, Hydrology, Environmental, Operational, and Cultural features

• Object Classes• Activities, External Documents, GeoMetaData,

Contacts, Companies etc.

• Not Referenced• Pass-through Polygons, Transportation

Networks, Hydrology, Environmental, Operational, and Cultural features

• Object Classes• Activities, External Documents, GeoMetaData,

Contacts, Companies etc.

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Introduction

History

Future

Objectives

Present

Core

Model Tour

Implementation

Q & A

Measure 225

Measure 100

Measure 0Great Western Railway

Parcels

Station Series

Operating Areas


Tour of the ModelTour of the Model

• Model comprised of logical grouping of FeatureDataSets:• Centerline – routing and stationing• Facility – pipes, valves and other fittings• Inspection – inspection ranges, anomalies,

leaks• Operations – pressure tests, risk analysis, HCA• Cathodic – cathodic protection features• Event Support – administrative, activites,

history, documentation and comments• Subtypes, Relationship Classes and Domains

• Model comprised of logical grouping of FeatureDataSets:• Centerline – routing and stationing• Facility – pipes, valves and other fittings• Inspection – inspection ranges, anomalies,

leaks• Operations – pressure tests, risk analysis, HCA• Cathodic – cathodic protection features• Event Support – administrative, activites,

history, documentation and comments• Subtypes, Relationship Classes and Domains

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: CenterlineModel Tour: Centerline

• Objects that form the centerline• Linear Referencing Mechanism• Form Routing Geometric Network

• StationSeries (PLFc) – routes of stationing, contains hierarchy information

• ControlPoint (PtFc) – points of known station position, PI’s

• LineLoop (OC)– a collection of station series that comprise a single ‘line’

• GeoMetaData (OC)– source information for control points

• OwnerOperatorship (OC) – Line Loop owner/operator percentages

• Objects that form the centerline• Linear Referencing Mechanism• Form Routing Geometric Network

• StationSeries (PLFc) – routes of stationing, contains hierarchy information

• ControlPoint (PtFc) – points of known station position, PI’s

• LineLoop (OC)– a collection of station series that comprise a single ‘line’

• GeoMetaData (OC)– source information for control points

• OwnerOperatorship (OC) – Line Loop owner/operator percentages

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: FacilityModel Tour: Facility

• Physical elements that comprise Pipeline

• Typically form Geometric Network• Online Referenced Not Networked

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

• Not Referenced• NonStationedPipe (PLFc), PiggingStructure (PLFc)

• Online Referenced Networked• Pipe Segment (PLFc), Valve (PtFc), Fittings (Meter,

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

• Physical elements that comprise Pipeline

• Typically form Geometric Network• Online Referenced Not Networked

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

• Not Referenced• NonStationedPipe (PLFc), PiggingStructure (PLFc)

• Online Referenced Networked• Pipe Segment (PLFc), Valve (PtFc), Fittings (Meter,

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

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: InspectionModel Tour: Inspection

• Inspection and Integrity• Generic classes• Huge variance in applications and data• Does not form GeoMetric Network

• Online Referenced• 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

• Inspection and Integrity• Generic classes• Huge variance in applications and data• Does not form GeoMetric Network

• Online Referenced• 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

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: OperationsModel Tour: Operations

• Regulatory and Operations• Does not form Geometric Network

• On or Offline Referenced• FieldNote (PtFc) – Field Data Collection• ElevationPoint (PtFc) – ground, pipe water elevations• Marker (PtFc) – monuments, Mile Posts, PIG Signals

• Not Referenced• SiteBoundary (POFc) – Meter Stations, Compressor

Stations, Easements etc.

• Online Referenced• HCAClass (PLFc), PressureTest (PLFc), RiskAnalysis

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

• Regulatory and Operations• Does not form Geometric Network

• On or Offline Referenced• FieldNote (PtFc) – Field Data Collection• ElevationPoint (PtFc) – ground, pipe water elevations• Marker (PtFc) – monuments, Mile Posts, PIG Signals

• Not Referenced• SiteBoundary (POFc) – Meter Stations, Compressor

Stations, Easements etc.

• Online Referenced• HCAClass (PLFc), PressureTest (PLFc), RiskAnalysis

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

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: CathodicModel Tour: Cathodic

• Corrosion Management• Kept generic• Based on Distribution Model• Not Geometric Network

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

• Online Referenced• CPCable (PLFc)

• Corrosion Management• Kept generic• Based on Distribution Model• Not Geometric Network

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

• Online Referenced• CPCable (PLFc)

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: EncroachmentsModel Tour: Encroachments

• Encroachments on the pipeline• Encroachments within the Class

Corridor• Does not form Geometric Network

• Not Referenced• HighConsequenceAreas (POFc), StructureOutlines

(POFc)

• Online Referenced• LineCrossing (PtFc)

• On or Offline Referenced• LinearEncroachment (PLFc), Structure (PtFc)

• Encroachments on the pipeline• Encroachments within the Class

Corridor• Does not form Geometric Network

• Not Referenced• HighConsequenceAreas (POFc), StructureOutlines

(POFc)

• Online Referenced• LineCrossing (PtFc)

• On or Offline Referenced• LinearEncroachment (PLFc), Structure (PtFc)

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: Event SupportModel 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

• 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

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: GeoDBModel Tour: GeoDB

• Subtypes• Relationship Classes• Domains

• Subtypes• Relationship Classes• Domains

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Model Tour: Missing?Model Tour: Missing?

• Landbase – Parcels• Operations – Class Corridors• Fittings – make then ORN features• Integrity – different data formats from PIG

runs• Cathodic – variance between companies• Inspections – Readings, Surveys – what

belongs in the GIS and what in RDBMS?

• Landbase – Parcels• Operations – Class Corridors• Fittings – make then ORN features• Integrity – different data formats from PIG

runs• Cathodic – variance between companies• Inspections – Readings, Surveys – what

belongs in the GIS and what in RDBMS?

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Implementation IssuesImplementation Issues

• Event and/or Feature approach• Getting Data into the Model• Future Documentation

• Event and/or Feature approach• Getting Data into the Model• Future Documentation

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Points to RememberPoints to Remember

• Utilize GeoDatabase and GIS to fullest capability• Parcels, Transportation Networks, Land Survey,

Political Boundaries can exist as feature classes in model – powerful analysis tool

• No model can be everything to everyone• Choose what your GIS implementation is going

to solve and create a suitable model

• Utilize the core elements to handle linear referencing

• Test potential classes against ORN, ORNN, OOR, NR and Centerline class types

• Utilize GeoDatabase and GIS to fullest capability• Parcels, Transportation Networks, Land Survey,

Political Boundaries can exist as feature classes in model – powerful analysis tool

• No model can be everything to everyone• Choose what your GIS implementation is going

to solve and create a suitable model

• Utilize the core elements to handle linear referencing

• Test potential classes against ORN, ORNN, OOR, NR and Centerline class types


DownloadingDownloading

• Building the GeoDatabase• Error building the model – Schema Wizard Bug

• www.esri.com\petroleum• www.esri.com\datamodels

Introduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Questions and AnswersQuestions and AnswersIntroduction

History

Future

Objectives

Present

Model Tour

Implementation

Q & A

Core


Contact InformationContact Information

• Andrew Zolnai – Petroleum Manager –ESRI [email protected]@esri.com

• Peter Veenstra – Chairperson APDM Technical Committee – M.J. Harden Associates – [email protected]

• Any member of the PIG Steering and Technical Committees


Thank you.Thank you.

ArcGIS Pipeline Data Model (APDM) - s3.amazonaws.com · ArcGIS Pipeline Data Model (APDM) ......

Documents

Transcript of ArcGIS Pipeline Data Model (APDM) - s3.amazonaws.com · ArcGIS Pipeline Data Model (APDM) ......