WORKSHOP : IMPLEMENTASI
APDM
15 Juli 2011
Klasifikasi Data Model APDM
Jenis Model Kategori Model
Jenis Model
Logical Model Merupakan Model Konseptual Menggambarkan Overview Data Model
Keseluruhan Physical Model
Merupakan Template Data Model dalam format Visio
Dapat diexport kedalam format XML Format XML digunakan sebagai basis
perancangan Data Model Geodatabase pada ArcGIS
Kategori Model
Abstract & Metadata Classes Framework dari APDM Informasi Header Data Model Dibutuhkan pada proses desain Geodatabase Sifatnya tidak “concrete” hanya muncul pada
Logical dan Physical Design Core Classes Optional Classess
Kategori Model
Abstract & Metadata Classes Core Classes
Merupakan Objects, Features, Relationship Classes dan Domain terkait dari struktur APDM
Mendefinisikan Centerline Features (Obyek Jalur), Stationing Attributes (Batas Jalur) dan Elemen-elemen Data terkait lainnya
Sifatnya “concrete” dan eksis secara fisik pada Geodatabase
Optional Classess Template Data Model acuan sebagai starting point
untuk perancangan Geodatabase sifatnya optional
Kategori Model
Kesimpulan : APDM merupakan Template Dasar yang
digunakan untuk merancang Geodatabase APDM lebih diarahkan pada data-data berbasis
Spasial Penggunaan Template “Optional Classess”
Sifatnya optional Dapat digantikan dengan Data Model lain : PODS, ISATS
atau Data Model spesifik Perusahaan Tetap mengikuti Aturan “Abstract Classess dan
Metadata” APDM
Abstract Classes : ObjectsAbstract & Metadata Classes
GroupEventIDOperationalStatus <d>
CenterlineObject
InstrumentParameterLineLoopHierarchySubSystemHierarchyActivityHierarchy
ActivityAddressCISReadingCompanyContactExternalDocumentGeoMetaDataMeterReadingOwnerOperatorProduct
AltRefMeasureLineLoopSubSystem
Shape[Feature]
CreatedByCreatedDateEffectiveFromDateEffectiveToDateEventID (pk)HistoricalState <d>LastModifiedModifiedByOriginEventIDProcessFlagRemarks
[FeatureArchive]
OBJECTID[Object]
OperationalStatus <d>CenterlinePolyline
BeginStationCLEditResponse <d>CLValidityTolerance <d>EndStationGroupEventIDStationSeriesEventID (fk)
CenterlinePolylineEvent
StationSeries
SubSystemRange
CLControl <d>CLStationEditResponse <d>CLXYEditResponse <d>CLZEditResponse <d>GroupEventIDOperationalStatus <d>StationSeriesEventID (fk)SymbolRotation
CenterlinePointCLEditResponse <d>CLValidityTolerance <d>StationSeriesEventID (fk)
OnlineFeatureStatus <d>
OfflineFeature
AlignmentSheetHighConsequenceAreaLineCrossingRemovedLineStructureOutline
InServiceDateInstallationDateOperationalStatus <d>
OfflineFacility
Site
SiteEventID (fk)SymbolRotation
OfflinePointFacilitySymbolRotation
OfflinePoint
InServiceDateInstallationDateOperationalStatus <d>SiteEventID (fk)
OnlineFacility
StationSymbolRotation
OnlinePointFacility
AppurtenanceInstrumentPipeJoinMethodTapValveVessel
DateManufacturedGrade <d>InletConnectionType <d>InletDiameter <d>InletWallThickness <d>Manufacturer <d>Material <d>PressureRating <d>Specification <d>
Fitting
ClosureElbowMeter
ReducerTee
BeginStationEndStationGroupEventID
OnlinePolylineFacility
BeginStationEndStationGroupEventIDStatus <d>
OnlinePolylineHCAClassInspectionRange
LineCrossingEasementOperatingPressure
PressureTestRightOfWayRiskAnalysis
StationStatus <d>SymbolRotation
OnlinePoint
AnomalyAnomalyPointElevationPoint
LeakFieldNote
<OfflineFeature>EventID (fk)OffsetAngleOffsetDistance
OnlinePointForOfflineFeatureBeginOffsetAngleBeginOffsetDistanceEndOffsetAngleEndOffsetDistance<OfflineFeature>EventID (fk)
OnlinePolylineForOfflineFeature
StationSeries
StationSeries
Site
<OfflineFeatureClass>
<classname>EventID (fk)ActivityDateActivityEventID (fk)
<classname>Audit
<Any APDMparent class>
Activity
ExternalDocument <fc>Audit
AltRefMeasure
OBJECTIDObject
CalculateARM <d>RefModeSubtypeValue (pk)RefModeSubtypeDescriptionRefModeUnits <d>RefModeBasis <d>RefModeType <d>StartStation
ReferenceModeAPDMClassType <d>ClassEventID (pk)ClassName
APDMClass
AltRefMeasure
OriginClassEventID (fk)OnlineLocationClassEventID (fk)OnlineLocationMechanism <d>
OnlineLocationClasses
Metadata
SiteEventID (fk)OfflineNonPointFacility
Site
StationSeries
ControlPoint
AltRefMeasure
CPOnlineLocation
EventID (pk)APDMObject
OBJECTID[Object]
CreatedByCreatedDateEffectiveFromDateEffectiveToDateHistoricalState <d>LastModifiedModifiedByOriginEventIDProcessFlagRemarks
[ObjectArchive]
Status <d>NonFacilityObject
ControlPoint
DocumentPointFieldNote
RemovedPointSitePointStructure
CPCablePIGStructure CPAnode
CPBondCPGroundBed
CPRectifierCPTestStation
Marker
CasingCoating
PipeSegmentSleeve
CPOnlineLocationLineCrossingLocation
StructureLocation
This section describes the ‘APDM Abstract Classes’ and ‘APDM Metadata’ tables. This diagram shows the inheritance of attributes andrelationships from the top-most classes down to the lower classes. Inheritance means that a concrete feature or object class inherits the
attributes, relationships and potential geometry types from all the classes above it (following the lines and the arrow heads pointingupwards). All classes are shown with ‘light yellow’ header boxes with the exception of the ‘Audit’ classes which are shown in ‘light green’.Standard ESRI classes are shown with ‘white’ attribute boxes and ‘APDM Abstract Classes’ are shown with ‘light blue’ attribute boxes. The
‘gray’ boxes show feature and object classes that inherit directly from the specified parent ‘APDM Class’. [Square Brackets] around the titleof a class means that no concrete feature/object class can inherit directly from this class. Note that for a class to belong to APDM it must
inherit from one of the specified ‘APDM Abstract Classes’ otherwise it is considered to be only an ESRI class with no significance orrelevance to the APDM. The feature class and object class icons denote which geometry type concrete ‘child’ classes may implement.
The metadata classes represent a set of object classes that are used to hold information about the reference modes, information abouteach concrete class inheriting from an ‘APDM Abstract Class’ and information about which ‘offline’ APDM classes have related ‘online’
polyline or ‘online’ point classes.
<OnlineFeatureClass>
RemovedPoint
RemovedLine
InServiceDateInstallationDateOperationalStatus <d>SiteEventID (fk)
FacilityObject
ValveOperator
Site
<Online<FC>ForOfflineClass>
APDM Core
Abstract Classes : Object based
APDMObject
Object
ObjectArchive
CenterlineObject NonFacilityObject
AltRefMeasureLineLoopSubSystem
<classname>Audit
<parent class>
Activity
ExternalDocument
<fc>Audit
ActivityExternalDocumentOwnerOperator
ActivityHierarchyLineLoopHierarcySubSystemHierarchy
FacilityObject
Abstract Classes : Feature based
Feature
FeatureArchive
Object
CenterlinePolyline
CenterlinePolylineEvent
StationSeries
CenterlinePoint
ControlPoint
OnlineFeatureOfflineFeature OfflineFacility
Site
OfflinePointFacility
OfflinePoint
OnlineFacility
OnlinePointFacility
Fitting
OnlinePolylineFacility
OnlinePolyline OnlinePoint
OnlinePointForOfflineFeature
OnlinePolylineForOfflineFeature
StationSeries
StationSeries
Site
<OnlineFeature>
AltRefMeasure
OfflineNonPointFacility
Site
SubSystemRange
Abstract Classes : Inheritance
Example of APDM Inheritance
ESRI Simple Object
Relationship Wormhole
Inheritance
Relationship Cardinality
APDM Abstract Class
APDM Concrete Class
Shape[Feature]
CreatedByCreatedDateEffectiveFromDateEffectiveToDateEventID (pk)HistoricalState <d>LastModifiedModifiedByOriginEventIDProcessFlagRemarks
[FeatureArchive]
OBJECTID[Object]
CLEditResponse <d>CLValidityTolerance <d>StationSeriesEventID (fk)
OnlineFeature
InstallationDateInServiceDateOperationalStatus <d>SiteEventID (fk)
OnlineFacility
StationSymbolRotation
OnlinePointFacility
DateManufacturedGradeInletConnectionType <d>InletDiameter <d>InletWallThickness <d>Manufacturer <d>Material <d>PressureRating <d>Specification <d>
Fitting
StationSeries
Site
AltRefMeasure
Elbow
ElbowAngle <d>ElbowRadius <d>
DateManufacturedGradeInletConnectionType <d>InletDiameter <d>InletWallThickness <d>Manufacturer <d>Material <d>PressureRating <d>Specification <d>
StationSymbolRotation
InstallationDateInServiceDateOperationalStatus <d>SiteEventID (fk)
CLEditResponse <d>CLValidityTolerance <d>StationSeriesEventID (fk)
CreatedByCreatedDateEffectiveFromDateEffectiveToDateEventID (pk)HistoricalState <d>LastModifiedModifiedByOriginEventIDProcessFlagRemarks
ShapeOBJECTID
Elbow
StationSeries
Site
AltRefMeasure
Registered classesin the
geodatabase musthave an Object ID
Field
Feature classeswill have a
geometry field
These fields areused for trackinginline history and
for archiving. Eachfield as a particular
purpose.
The feature class is anonline feature and isprimarily located by
stationed position(indicated by the the
relationships toStationSeries and
AltRefMeasure). Thisfeature will respond toedits on the centerlineusing values stored inthe CLEditResponse
andCLValidityTolerance
fields.
These attributesindicate that the
feature class is goingto store facility objectsthat are installed and
put into servicetransporting product.The relationship with
to Site allows thefeature to be stored
without geometry.
The concrete class(Elbow) will be a point
feature and needs asingle station value.
An elbow isconsidered a fitting
and inherits thestandard attributes
that describe thephysical aspects of a
fitting.
The elbow featureclass is a concrete
implementation of theAPDM abstract class
inheritance tree.
Elbows are modeledin this APDM as aM-Aware PointFeature Class.
This feature classinherits all theattributes andrelationships fromit’s ancestor orparent APDMabstract classes.
Additional attributescan be added to thisclass describing ordefining the featuresin this class asunique instances ofelbows.
Attributes andrelationshipsinherited fromAPDM abstractclass must beimplementedwithout alteration tonames orcardinality.
Note: Diagramming the APDM abstractclasses in this manner saves on
duplication of attributes in the depictionof each concrete class in the logical
model diagram.
The Elbow featureclass will appear in
the APDMgeodatabase with
the followingattributes and
relationships havinginherited them from
a set of APDMabstract classes.
Metadata Classess
OBJECTIDObject
CalculateARM <d>RefModeSubtypeValue (pk)RefModeSubtypeDescriptionRefModeUnits <d>RefModeBasis <d>RefModeType <d>StartStation
ReferenceModeAPDMClassType <d>ClassEventID (pk)ClassName
APDMClass
AltRefMeasure
OriginClassEventID (fk)OnlineLocationClassEventID (fk)OnlineLocationMechanism <d>
OnlineLocationClasses
Metadata
StationSeries
ControlPoint
AltRefMeasure
CPOnlineLocation
RemovedPoint
RemovedLine
APDM Core
Core Classes
Station Series Control Points Stationing Model Objects
Online Referenced Networked Online Referenced Non-Networked On or Offline Referenced Not Referenced Object Class Core Elements
Core ClassesObjectOBJECTID
AttributesEventID
GroupEventIDOriginEventID
OperationalStatus
AuditCreatedBy
CreatedDateEffectiveFromDate
EffectiveToDateLastModifiedModifiedBy
LineLoopLineName
FeatureSHAPE
ControlPointStation
StationSeriesEventID
StationSeriesBeginStationEndStation
FromSeriesEventIDSeriesOrder
ToSeriesEventID
OnlineStationSeriesEventID
(Begin)Station
Offline
Online Point(OffsetDistance) if Location
(OffsetAngle) if LocationSymbolRotation
(OfflineEventID) if Location
Online PolylineEndStation
(OfflineEventID) if Location
PipeSegment
Offline Point(Buffer)
Offline Polyline(Buffer/Easement)
Offline Polygon(Buffer)
Core Classes: Station Series
ArcGIS Pipeline Data Model
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
Core Classes: Station Series
ArcGIS Pipeline Data Model
Station Serie
s 1 (Route)
Station Series 2 (Route)
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 Classes: Control Points
ArcGIS Pipeline Data Model
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
Core Classes: Control Points
ArcGIS Pipeline Data Model
-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 = 1
Subtypes::InternalPoint
-SubTypeCD : esriFieldTypeInteger = 2
Subtypes::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 Classes: Stationing
ArcGIS Pipeline Data Model
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
Core Classes: Stationing
Station 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
CP3, SS1, 200+00, Slack ChainCP3, SS1, 5.6, Mile PostCP3, SS1, 1000+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
CP5, SS2, 400+00, Slack ChainCP5, SS2, 9.1, Mile PostCP5, SS2, 3000+00, Historical
CP6, SS2, 600+00, Slack ChainCP6, SS2, 11.1, Mile PostCP6, SS2, 7500+00, Historical
Core Classes: Stationing
-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 Classes: Stationing
ArcGIS Pipeline Data Model
Route 1
Route 2
Measure 225
Measure 250
Measure 600
Measure 200
Measure 100
Measure 400
Measure 0
Core Classes
ArcGIS Pipeline Data 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.
Core Classes: Model Objects
ArcGIS Pipeline Data Model
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)
Core Classes: Definitions
ArcGIS Pipeline Data Model
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
Core Classes: ORN
ArcGIS Pipeline Data Model
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
Station SeriesMeasure 225
Measure 100
Measure 0
Pipe SegmentValve
ReducerClosureControl Point
Closure – StationSeriesEventID 235, Station 0+00
PipeSegment BeginStationSeriesEventID 235, BeginStation 0+00EndStationSeriesEventID 235, EndStation 30+00
Valve – StationSeriesEventID 235, Station 30+00
PipeSegment BeginStationSeriesEventID 235, BeginStation 30+00EndStationSeriesEventID 235, EndStation 165+00
Valve – StationSeriesEventID 235, Station 165+00
PipeSegment BeginStationSeriesEventID 235, BeginStation 165+00EndStationSeriesEventID 235, EndStation 225+00
Reducer – StationSeriesEventID 235, Station 225+00
Core Classes: ORNN
Online Referenced Not-Networked Point or Linear Feature Geometrically constrained to centerline Does not participate in Geometric Network
Leaks, Pressure Tests, Coating
Station SeriesMeasure 225
Measure 100
Measure 0
CoatingPressure TestLeakControl 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 Classes: 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
Station SeriesMeasure 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
Core Classes: Other
Not Referenced Pass-through Polygons, Transportation Networks,
Hydrology, Environmental, Operational, and Cultural features
Object Classes Activities, External Documents, GeoMetaData,
Contacts, Companies etc.
Measure 225Measure 100
Measure 0Great Western Railway
Parcels
Station Series
Operating Areas
Tour 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 Tour: Centerline
ArcGIS Pipeline Data Model
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
Model Tour: Facility
ArcGIS Pipeline Data Model
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)
Model Tour: Inspection
ArcGIS Pipeline Data Model
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
Model Tour: Operations
ArcGIS Pipeline Data Model
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)
Model Tour: Cathodic
ArcGIS Pipeline Data Model
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)
Model Tour: Encroachments
ArcGIS Pipeline Data Model
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)
Model Tour: Event Support
ArcGIS Pipeline Data Model
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
Model Tour: GeoDB
ArcGIS Pipeline Data Model
Subtypes Relationship Classes Domains