PODS Lite Conceptual Model Logical Model Design – Pipeline Hierarchy, MetaData and Logical Model Design – Assets

Logical Model Design – Pipeline Hierarchy, MetaData and Logical Model Design – Assets (III)
Linear Referencing (II) Assets Assets represent the depreciable
Pipeline Hierarchy A conceptual model is a representation of a system, made of the G/As/D/H/Au
components that comprise the
Pipeline composition of concepts which are used to help people know,
Pipeline Hierarchy pressurized product containment and
understand, or simulate a subject the model represents. A Pipeline represents a continuous pressurized segment or product
transportation aspect of the pipeline.
transportation or containment. The simplest definition of a pipeline
G/H/D/Au G Assets exist as real-world features and
defines centerline for This conceptual model is broken down into five main areas: is the pipe stretching from inline inspection pig launcher to pig
are almost always represented as
pipeline hierarchy, assets, conditions, linear referencing, and receiver. Each pipeline operator has some variation on how it
transported points or polylines on or along the
Product metadata. Was PODS Line classifies pipelines. *Pt *Pl
by Network pipeline routes.
Route The Pipeline is analogous to the Line or Lineloop in previous models.
The elements in this diagram indicate the primary elements that Valves are used to moderate or
comprise the conceptual model. Each colored rectangle has an A pipeline is defined as either: logical (does not have child network
constrain flow. A valve is represented
icon indicating the geometry shape that is used to represent it. route features) or physical (has child network route features).
as a point on the map but will also
Assets Assets The icons in the elements represent a description of the Pipeline PipelineProduct Product have a length that is described as pipe
geometry type and are described in the legend directly below. Logical pipelines will have one or more Physical pipelines to denote ol ol ol ol ol
ol pipelineName (string) primaryProduct <d> productTypeCL <d> a hierarchy. They act as a parent to one or more physical pipelines
LauncherReceiver Valve GirthWeld PipeBend Coating PipeSegment characteristics.
PipeSegment comprised of/installed on The lines connecting the ‘elements’ in the model represent
located on engineering formal or defined relationships between the ‘elements’. The pipelineOrder (integer) productSubtypeCL <d> to comprise a bigger pipeline system. Pipeline hierarchy can be barrelDiameterCL <d> dateManufactured (date) coatingTypeCL <d> fabricatorNameCL <d> applicationCompanyCL <d> dateManufactured (date)
stationing A PipeSegment represents a
point ol ‘crows feet’ represent many elements that are related to a pipelineTag (string) achieved by a self relate through the Pipeline table via the barrelSpecificationCL <d> functionalStatusCL <d> girthWeldTypeCL <d> horizontalAngle (double) applicationLocationCL <d> detailFeatureID (fk)
Valve continuous section of pipe.
representation parent or single element. hasRouteLF <y/n> parentPipelineID. This implies each child has one and only one barrelWallThicknessCL <d> functionCL <d> identifier (string) radius (double) applicationMethodCL <d> detailTableName (string) PipeSegments are a larger master
of Network Route hasLRSLF <y/n> parent. If a Physical Pipeline belongs to more than one Logical barrelOrientationCL <d> Identifier (string) inspectionTypeCL <d> techniqueCL <d> appliedForRepairLF <d> gradeCL <d>
ol
transported segment comprised of many lengths or
PipeBend The pipeline hierarchy is used to define the pipelines in a system locationCL <d> by parent Pipeline, the optional PipelineHierarchy table can be used to corrosionAllowance (double) joinTypeCL <d> vendorIdentifier (string) typeCL <d> coatingLayer (integer) joinTypeCL <d> joints of pipe that share common
and how they are organized. The hierarchy also defines sites or lowFlowLF <y/n> transports model this relationship and multiple hierarchies. Identifier (string) length (double) verticalAngle (double) dateApplied (date) longSeamCL <d> attributes (as shown to the left).
ol ol stations and where they are located in space. parentPipelineID (fk) (GUID) manufacturerCL <d> manufacturerCL <d> heatCapacity (double) manufacturerCL <d>
LauncherReceiver piggableLF <y/n>
ol Network Route NOTE: How each element in this group inherits attributes and relationships from one or more abstract maximumPigDiameter (double) materialCL <d> materialCL <d> materialCL <d> A PipeSegment can also represent the
Coating Assets are installed and in-service product transportation or operationalStatusCL <d> classes (represented by the grey boxes). Also note that each attribute describing a element has a data type maximumPigLength (double) millTestPressure <d> thickness (double) nominalDiameterCL <d> length and pipe characteristics of a
ol regulatedLF <y/n>
GirthWeld containment devices. These are maintainable features that (string, double, GUID), a key identifier (pk) or (fk) used to relate child elements to parent elements and a <d> nominalPressureRating (double) model (srting) thicknessUOMCL <d> nominalPressureRating (long) point feature such as a valve or other
remain until abandoned, removed or replaced. All assets may be smartPiggableLF <y/n> indicates that the attribute is defined by a ‘valid value list’ or ‘domain’. Again boxes are connected by portableLF operatorTypeCL <d> typeCL <d> nominalWallThicknessCL <d> point fitting (bend, meter, reducer
located by a measured position along a pipeline or by a XYZ systemTypeCL <d> groups network
relationships (with or without crow’s feet to denote parent to child relationships between elements). Each totalLength (double) operatorManufacturerCL <d> millLocation (string)
routes and etc.) as shown in the ‘Asset’ section of
coordinate position. A set of assets connected end to end form typeCL <d> defines pipeline rectangle has a icon indicating the type of geometry the element will appear as on a map and if that trapClosureTypeCL <d> outsideDiameterCL <d> millTestPressure (long)
Conditions Condition the pipeline in the ground. location
the Conceptual Model (far left).
geometry is located by LRS (online or on-the-pipeline route) or XYZ (offline or off-the-pipeline). Any attribute typeCL <d) ratingCL <d> originCL <d>
ol ol defined with a suffix CL indicates a domain attribute. Any ending with LF indicates a logical Yes/No attribute. remotelyOperatedLF <y/n> applied to ... outsideDiameterCL <d> The relationship between point and
InspectionRange OnlineCrossing located on continuous Conditions represent the ‘state’ or ‘condition’ of the pipeline.
contains
responseTime (integer) located on
and requires segmentTypeCL <d>
measure the existence line is defined as a ‘detail’. The
Conditions also represent the results of an activity such as an safetyCriticalEquipmentLF <y/n> of ... specificationCL <d> attributes of both Valve and Pipe
ol
Class Crossing inspection or analysis (like a population class study, or high specificationCL (string) located on SMYSCL <d>
Network Route consequence area analysis). Conditions represent the current
Metadata Metadata tables are used to describe
describe the physical aspects rather
typeCL <d> than ‘conditional’ or ‘operational’
‘state’ of the pipeline and record previous or historical states of 1
2 LRSNetwork G/H/D/Au/C/Pt* generic non-spatial elements and to
aspects. These are described by
ol
OperatingPressure G/T
3

ol the pipeline as the conditions change over time. capture or codify rules about the
CrossingPipeline EngineeringStationNetwork = 1 structure and content of the model.
overlain ‘Condition’ features.
ol
Metadata tables store information about activities or the ContinuousMeasureNetwork = 2
TestPressure ol
enumerated
CrossingUtility elements that are done to maintain and operate a pipeline Notes are a generic container for located on Network Route located on
Is type of (repairs, analysis, inspections). There are tables for storing comments and additional notes
ol
ConsequenceSegment ol supporting documents and notes that describe the element in describing any ‘element’ in the model.
CrossingHydrology TableMetaData ReferenceMode
ol
Notes Notes replaces routing, sheet, and field
the system. There are also tables holding the rules that govern length representation of point location
ol
PipeOperatingCondition the organization of the model, and how linear referencing notes and can be placed as a ‘online’
ol
CrossingTransportation measurement systems are managed. tableCode (string) is primary or networkID (fk) (integer) noteSummary (string) point, or can be used as a generic note
is secondary
tableName (string) refModeCL <d> noteTypeCL <d> about some ‘element’ without a spatial
ol
PipeJurisdiction Lastly there are elements designed to manage how linear category (string) refModeBasisCL <d> position by keeping the SHAPE or
referencing (LRS) is applied and utilized in the system. These subcategory (string) redModeTypeCL <d> GEOMETRY attribute NULL.
Logical Model Design – Conditions (IV)
cross references
tables are based on the ESRI ArcGIS for Pipeline Referencing coordinateRefSystem <string> refModeUnitsCL <d>
EPSGNumberCL <d> isPRM <d> TableMetaData records information
Metadata ReferenceMode TableMetaData are
(APR) location model. The LR system manages networks of
ESRIcoordinateRefSystemCL <d> parentRefMode (fk)
routes for the purpose of locating features by measure and/or describe the All elements about specific ‘elements’ (or tables) in
comprised of station. Of all the tables in the PODS Lite, these are the only geometryTypeCL <d> attributes of startMeasure (double) the model. Currently this information
LayerMetaData optional tables. geometryRepresentationCL <d> refers to a ‘code’ for each table and a Conditions Conditions represent the ‘state’ or ‘condition’ of the pipeline. Conditions
enumerated G/C/D/H/Au
1
2 LRSNetwork unitOfMeasureCL geometryTypeCL name. This eventually will be the place also represent the results of an activity such as an inspection or analysis
3
as ol
are comprised of
for gap/overlap rules. ModuleMetaData (like a population class study, or high consequence area analysis).
UnitOfMeasure Notes feet point
meter polygon
stores the name and code for modules Conditions represent the current ‘state’ of the pipeline and record previous
LayerMetaData UnitOfMeasure (or logical groupings) of tables. or historical states of the pipeline as the conditions change over time.
millemeter polyline
mils table ModuleMetaData has a ‘contains’
tableID (fk) tableID (fk)
Linear Referencing System (LRS) [Optional] definitionQuery (string) tableName
psi relationships indicating that parent
CalibrationPoint geometryRepresentationCL modules contain or organize child Pt Pl
m assigns allowGapLF <d> attribute
Centerline CenterlineSequence ContinuousMeasureNetwork allowOverlapLF <d> unitOfMeasurement <d> Spatial Type
modules. ReferenceMode describes all
Measure the ‘route networks’ or ‘measure/
dependentLayerID (fk) Well Known Binary
ordered by m
to Well Known Text stationing’ systems within the model.
1
2
3
LRSNetwork enumerated as EngineeringStationNetwork
may require the
presence of
ol ol ol ol ol ol
Crossing Class OperatingPressure InspectionRange TestPressure ConsequenceSegment PipeJurisdiction
1
2
3
Enumeration Table Point (located by XY only) Offline FeatureClass Linear Referencing System (LRS) G/H/Au/D angle determinationDate determinationAuthority dateBegin dateOfTest dateEstablished city
Location Model [Optional] belowLineLF <d> determinationMethodCL <d> determinationDate dateEnd duration typeCL <d> county
Either/Or Inheritance ol
Online Polyline (located by LRS or XY) Polygon Abstract Class Was PODS Route Was PODS Series
classTypeCL <d> ratingCL <d> determinationMethodCL <d> reasonCL <d> mediumCL <d> establishedByMethodCL <d> state
Inheritance (Dashed=Optional) Polyline (located by XY only) Table (Object) Domain clearance limitingFactors typeCL <d> maxElevation establishedAuthority country
easementDS pressure maxPressureAtMinElevation
1..M Relationship (Implied) m
Polyline (A M-Aware route) Online FeatureClass Centerline (LRS) Class
easementUS pressureCalculatedAsCL <d> minElevation
Was ol
PipeOperatingCondition
1..M Relationship (Explicit or Defined) SubType Wormhole relationship name pressureTypeCL <d> minPressureAtMaxElevation
ol
Online Point (located by LRS or XY) MAOPRating
Centerline CenterlineSequence NR NR CalibrationPoint owner pressureGroup originalTestLength
A Abstract Class (MOP) aboveGroundPipeLF <d>
reasonForTestCL <d>
centerlineID (fk) (GUID) m
ContinuousMeasureNetwork
m
EngineeringStationNetwork measure (double) aboveWaterLF <d>
testStationElevation
networkID (fk) (integer *) networkID (integer *) HDDSegmentLF <d>
testStationPressure
networkRouteID (fk) (GUID) parentNetworkID (fk) (integer) networkRouteID (fk) (GUID) is subclass of ... offshoreLF <d>
testPressure
stationingDirectionCL <d> pointTypeCL <d> provenanceCL <d>
testPressureGroup
Logical Model Design – Abstract Classes (I) shared geometry
ordered
by
seriesOrder (integer)
forwardMeasure (double)
ol
CrossingPipeline ol
CrossingUtility ol
CrossingHydrology ol
CrossingTransportation
spanLF <d>

in network backwardMeasure (double) bondedLF <d> bondedLF <d> inFloodplainLF <d> heavyHaulRoadLF <d>
enumerated
pipelineCoatingCL <d> utilityTypeCL <d> numberOfLanes (integer) Network Route located on All Conditions
Abstract Classes assigns measure to
Abstract classes are used to simplify the design and documentation of a model. An abstract
1
2 LRSNetwork pipelineCommodityCL <d> utilityVoltage (double) patrolledRoadLF <d>
3
vertex on route requires
class represents a concept that needs to be described or utilized within a logical model. pipelineDiameterCL <d> publicRoadLF <d> PipeSegment the existence OperatingPressure InspectionRange
A Global (G) EngineeringStationNetwork = 1 pipelineMaterialCL <d> of ...
ContinuousMeasureNetwork = 2 NOTES: pipeToGroundON (double)
Abstract classes are represented by the letters that follow the name of the abstract class in RedlineActivityTypeCL RedLine Crossings The crossing object acts as a superclass. The attributes described in this object are TestPressure ConsequenceSegment
uniqueID (pk) (GUID)(NN) The ContinuousMeasureNetwork pipeToGroundOFF (double)
the remainder of the logical model to indicate that each table describing an element in the immediately inherited by the objects beneath. The child objects have the word ‘Crossing’
replace the previous PODS PipeOperatingCondition Class
model has the attributes and relationships defined in and by these abstract classes. Create Route fromMeasure prefixed to the object name to denote this relationship. The construct of super-class and sub-
calibrationPointTypeCL stationingDirectionCL Routes. These features contain
Calibrate Route toMeasure class is used here to avoid duplicating super-class attributes in each sub-class object.
measure values along the route PipeJurisdiction Crossing
Begin Route Ascending (with measure) Reverse Route networkRouteID (fk)
in a continuous and un-
End Route Descending (against measure) Retire Route routeName (fk)
interrupted state. The
Equation Extend Route networkID (fk)
EngineeringStationNetwork
Point of Inflection (PI) Reassign Route effectiveDate
replace the previous PODS
Unknown Realign Route activityType <d>
Series. These feature contain MetaData and Hierarchy Domains referenceModeBasisCL referenceModeTypeCL referenceModeUnitsCL
Verified as Unknown station values along each route.
A Assets (As) A Conditions (C) A Describe (D) A History (H) A Audit (Au) But the sum of the engineering pipelineTypeCL noteTypeCL pipelineLocationCL operationalStatusCL referenceModeCL Arbitrary Interrupted and Adjustable (Re-route + Offset) 9001, esriSRUnit_Meter
Linear Referencing Systems (LRS) tables describe how CalibrationPoints are stand-alone point geometries containing measure series stationing connected end- 2D Projected Interrupted and Not Adjustable (Engineering) 9002, esriSRUnit_Foot
installedDate (date)(AN) activityOriginDate (date) description (string)(AN) fromDate (date)(NN) editDate (date)(AN) Dumpline Above/Below Ground Onshore Abandoned Continuous Measure 3D Geoid Uninterrupted and Adjustable (Continuous) 9003, esriSRUnit_SurveyFoot
networks of M-Aware polyline routes are organized and values that are used to ‘calibrate’ or ‘set’ the measure for any given to-end form the measure values
Export Adjacent Feature Offshore Active Engineering Station 3D Projected Uninterrupted and Not Adjustable (Mile Post) 9030, esriSRUnit_NauticalMile
inserviceDate (date)(AN) (AN) comments (string)(AN) toDate (date)(AN) editor (string)(AN) managed for the purpose of locating ‘elements’ on or route. Each calibration point belongs to a single ‘route’ in a single of the parent 3D Slack Chain Unknown 9033, esriSRUnit_SurveyChain
Fiber Optic Block Line Onshore/Offshore Conceptual
tagID (string)(AN) statusCL <d>(AN) createDate (date)(NN) along a pipeline using a ‘measured’ distance along the ‘network’. Store the information for equation points in CalibrationPoint. ‘ContinuousMeasureNetwork’ Flowline Building Corner Unknown Decommissioned Unknown Verified as Unknown 9034, esriSRUnit_SurveyLink
creator (string)(NN) route from the start of the route. feature. Routes are the parents Future Connection/Tie In Feature Notes Verified as Unknown Design pipelineSystemTypeCL Verified as Unknown 9035, esriSRUnit_SurveyMile
Centerline stores the network features (or Geometry) for a given route to Series. Gas Injection Field Note Idle 9036, esriSRUnit_Kilometer
Gas Lift General Comment Inactive Distribution -9999, Unknown
can be ONLY The term route in this instance is not the old PODS route network. If Polyline feature class that stores the actual route features Gathering productSubTypeCL (Liquids)
one of Gathering Interface Proposed -9998, Verified as Unknown
but rather is the definition of a ‘ESRI’ M-Aware Polyline (Geometry) of the routes. Where multiple routes from different networks PODS NextGen provides an Transmission
Jumper Marker Removed CRD-CRD, Crude Oil
Route. share common geometry, only one centerline feature is present. explicit foreign-key relationship Lateral Onshore/Offshore Unknown CRD-CRD, Crude Oil productSubTypeCL (Gas)
from ContinuousMeasure to Mainline Interface Verified as Unknown CRD-CRW, Sweet Crude Oil
All routes are managed in a connected network of lines. CenterlineSequence is a table storing the sequence of routes in a given EngineeringStationNetwork. This Mooring Property Line CRD-CRR, Sour Crude Oil NG-PG, Propane Gas
These are connected end-point to end-point to create a network. relationship exists in the APR Pipe-In-Pipe Outer Pipe Right of Way HVL-HVL, Highly Volatile Liquid NG-MG, Methane Gas
sequence of routes that form the network. Pipe-In-Pipe Inner Pipe Routing Note EPSGNumberCL ESRI_CRS_WKID HVL-OHV, Other Highly Volatile Liquid NG-SG, Synthetic Gas
software between ‘continuous’ Production Sheet Note
ContinuousMeasureNetwork are M-Aware Polyline features representing HVL-CHM, Chemical NG-HG, Hydrogen Gas
m and ‘engineering’ network but
A PipelineFeature (*) NetworkRoute (NR) Polygon (Pg) Table (T) All tables in this module inherit from global and history the ‘routes’ in the old PODS world. These can be formed together end-to-
Sales Water Level 2025, NAD27(76) / MTM zone 16 2165, Abidjan_1987_TM_5_NW PRD-AA, Anhydrous Ammonia NG-NG1, Pipeline quality or tariff quality natural gas
does not exist as a relationship in Service Unknown 2026, NAD27(76) / MTM zone 17 2043, Abidjan_1987_UTM_Zone_29N PRD-LPG, Liquified Petroleum Gas NG-NG2, Wet but non-sour natural gas
editResponseCL <d> (NN) networkID (GUID)(NN) Geometry (BLOB/String) (AN) abstract classes. Describe and Audit are optional. end point in a network but for purposes of modeling pipelines these are the model. Site Verified as Unknown 2027, NAD27(76) / UTM zone 15N 2041, Abidjan_1987_UTM_Zone_30N PRD-NGL, Natural Gas Liquids NG-NG3, Sour but non-wet natural gas
considered ‘stand’ alone features where ‘events’ do not cross from one to Sub-Sea Tie In Stub Line etc... etc... PRD-ETH, Fuel Grade Ethanol NG-NG4, Wet, sour natural gas
positionSourceCL <d> (NN) networkRouteOrder (integer)(AN) Umbilical Main
An enumeration (or list of numbers) is used to define the the other. Each physical Pipeline in the PRD-EPL, Abandoned Liquid Pipeline NG-OTG, Other Gas
locError (string)(AN) networkRouteName (string)(AN) ABSTRACT CLASS TYPES Umblilical Infield PRD-RGS, Refined non-ethanol blended gasoline NG-EPG, Abandoned or Empty Gas Pipeline
pipeLineID (FK) (GUID)(NN) primary key for a given network these are stored in the model has one productTypeCL
maintainLRSLF <y/n> (NN) Water Injection
Domain listings show standard set of PRD-RFD, Refined fuel oil, diesel
networkID (fk) (integer) (AN) pipelineName (FK) (string)(AN) LRSNetwork. EngineeringStationNetwork represent a different network where each ContinuousMeasureNetwork Well Tie PRD-RKJ, Refined kerosene, jet fuel
The Global abstract class is concerned with a values. Values can be added to each CRD, Crude Oil
pipelineID (fk) (GUID) (AN) Geometry (BLOB or String) (NN) route comprises a section of the ‘continuous’ measure network. route per pipeline. Each physical Unknown PRD-OTR, Other refined and/or non-HVL petroleum products
model wide global identifier field. Verified as Unknown domain to suit business purposes. HVL, Highly Volatile Liquid
pipelineName (fk) (string)(AN) IMPORTANT Pipeline many have one or more PRD, Non-Volatile Liquid Product PRD-ETB, Ethanol blended gasoline
Redline is yet to be defined .... EngineeringStationNetwork NG, Natural Gas PRD-BDB, Biodiesel blend
visualOffset (double)(AN) The Assets abstract class is concerned with PRD-OBI, other biofuels
describing physical installed assets used to The LRS tables defined above are based on the ESRI ArcGIS routes. Each ContinuousMeasure
CO2, Carbon Dioxide
transport product or are part of the physical for Pipeline Referencing (APR) Location Model tables. route should be comprised of
pipeline operation. Assets can be contained Implementing the LRS Location Model tables within PODS one or more EngineeringStation
located on Network Route routes connected to each other
within Sites. The Conditions abstract classes is LIte is optional.
used to describe the historic and current ‘state’ in sequence, end point to end Asset Domains Condition Domains
or ‘condition’ of the pipeline. Conditions are Implementing LRS within PODS LIte does not require point. All routes in either table
discovered as a result of Activities. adoption or use of the ESRI APR software tools. However, may have negative measure valveFunctionCL carrierPipeInnerOuterCL pipeSegmentTypeCL onlineLocationFeatureID classRatingCL conseqSegDetermineMethodCL
PODS Lite has been designed to work seamlessly with values.
ol ol
Point (Pt) Polyline (Pl) Describe is used to describe elements in the APR. valveFunctionalStatusCL pipeGradeCL pipeSMYSCL
Derived Network Measure Fields crossingClassTypeCL pressureDetermineMethodCL pipeOperConditionSourceCL
geometry (BLOB or String) (AN) geometry (BLOB or String) (AN) pipeline. History is used to track when
measure (double)(AN) fromMeasure (double)(AN) ContinuousMeasureNetwork elements were ‘current’ or ‘active’ or when they valveManufacturerCL pipeJoinTypeCL pipeSpecificationCL
were ‘historic’ or ‘idle’. crossingPipeCoatingCL pressureCalculatedAsCL
networkRouteID (fk) (long)(AN) fromNetworkRouteName (fk)(str)(AN) measure values can be derived
Audit is used to track what person created and The poster is designed to be read from upper left, downwards valveMaterialCL pipeLongSeamWeldTypeCL pipeWallThicknessCL
networkRouteName (fk)(string)(AN) fromNetworkRouteID (fk)(long)(AN) from the cumulative total of the
validityTolerance (double)(AN) toMeasure (double)(AN) stationing of the last modified a element in the database. and the from upper right and downwards. The sections are crossingPipeProductCL pressureTypeCL
toNetworkRouteName (fk)(str)(AN) EngineeringStationNetwork enumerated by numbers in the title blocks (I-II-III) valveOperatorManufacturerCL pipeMaterialCL offshoreOnshoreCL
derivedMeasure toNetworkRouteID (fk)(long)(AN) route features. These fields are PipelineFeature is used to represent how a
geometric feature/shape is located on or along crossingNomDiameterCL testPressureMediumCL
derivedNetworkRouteName validityTolerance (double)(AN) not considered part of the PODS valveOperatorTypeCL pipeNominalDiameterCL
derivedNetworkRouteID Lite Core but are shown here as the pipeline. All elements in the model that
derivedfromMeasure they could be added during the have a location in space (with the exception of crossingPipeMaterialCL testPressureReasonCL
derivedFromNetworkRouteName area features – polygons) must implement (or valveRatingCL pipeOutsideDiameterCL
creation of the APR networks
derivedFromNetworkRouteID using the ESRI ArcGIS for Pipeline possess the attributes from) the PipelineFeature
abstract class. Each PipelineFeature can valveTypeCL pipeOriginCL crossingUtilityTypeCL inspectionReasonCL
derivedToMeasure Referencing network creation
derivedToNetworkRouteName process. optionally be located on or along a Network
derivedToNetworkRouteID Route. Point, Polyline, A PipelineFeature can be Design Notes barrelSpecificationCL coatingTypeCL coatingLocationCL crossingWaterFloodPlainCL inspectionTypeCL
EITHER an Asset or a Condition but can still
editResponseCL statusCL positionSourceCL inherit from any of the of the OTHER abstract This poster comprises both a conceptual and logical model design notes. The poster is designed to be read from upper left, downwards and the from upper right and downwards. The barrelOrientationCL coatingMaterialCL coatingUOMCL classDetermineMethodCL consequenceSegmentTypeCL
classes sections are enumerated by numbers in the title blocks (I-II-III). For the designer it is difficult to perform and document a conceptual model and logical design without reverting back to
Relative – Online – Fixed LRS Current Coordinate Located
the terms ‘tables’ and ‘attributes’ and ‘relationships’. In some cases, the design is best explained in these terms.
Absolute – Online – Update LRS Historic LRS Located pigTrapManufacturerCL radiographicResultCL coatingApplyLocationCL
NetworkRoute, and Polygon represent physical
Absolute – Online – Fixed LRS Unknown LRS Located with Offset
spatial features in the model. A NetworkRoute The principles for design were to utilize what worked in previous PODS models including the relational and spatial model. The design uses existing patterns if they still make sense or
Absolute – Offline – Update LRS for Point Verified as Unknown pigTrapReducerTypeCL bendFabricatorNameCL coatingApplicationCoCL
is used to locate elements along a route using there was not a better way. Every attempt was made to remove any element that was not necessary, to keep things simple, and to use common ‘pipeline’ terms rather than data
Absolute – Offline – No LRS
the linear referencing system (LRS) tables. modeler terminology. Every attempt was made to keep the abstract classes as straight forward as possible.
pigTrapWallThicknessCL bendTechniqueCL coatingApplyMethodCL
Move the event on the line, do not update the measure
Do not move the event on the line, update the measure (G) – Braces indicate the abstract class can be At this stage of the design no decision about feature, table, attribute ‘SourceCL’ information has been finalized. Part of ‘SourceCL’ construct is covered in the PipelineFeature abstract
Do not move the event on the line, do not update the measure inherited from by elements in the model. (*) – class. The final decision has not been made regarding this. Domains and Code-Lookup tables are considered to be synonymous with each other containing, at a minimum, a code and pigTrapClosureTypeCL bendTypeCL
Do not move the event in space, update the measure within validityTolerance (point only) Indicates that no class can inherit directly from description value.
Do not move the event in space, no LRS this abstract class. pigTrapTypeCL
Copyright © PODS Organization 2016-2017 – All rights reserved