Utility and Pipeline data Model - iSpatial Tec

Utility and Pipeline Data Model 2019 Edition pg. 1

Esri, 2019

Copyright © 2019 Esri

All rights reserved.

Printed in the United States of America.

The information contained in this document is the intellectual property of Esri. This work is protected under United

States copyright law and other international copyright treaties and conventions, and is licensed the recipient to use

under the terms and conditions set forth in the Creative Commons Attribution 4.0 International license. To view a copy of

this license, visit http://creativecommons.org/licenses/by/4.0/legalcode.

US Government Restricted/Limited Rights

Any software, documentation, and/or data delivered hereunder is subject to the terms of the License Agreement. The

commercial license rights in the License Agreement strictly govern Licensee’s use, reproduction, or disclosure of the

software, data, and documentation. In no event shall the US Government acquire greater than RESTRICTED/LIMITED

RIGHTS. At a minimum, use, duplication, or disclosure by the US Government is subject to restrictions as set forth in

FAR §52.227-14 Alternates I, II, and III (DEC 2007); FAR §52.227-19(b) (DEC 2007) and/or FAR §12.211/12.212

(Commercial Technical Data/Computer Software); and DFARS §252.227-7015 (DEC 2011) (Technical Data –

Commercial Items) and/or DFARS §227.7202 (Commercial Computer Software and Commercial Computer Software

Documentation), as applicable. Contractor/Manufacturer is Esri, 380 New York Street, Redlands, CA 92373-8100, USA.

Esri Trademarks

@esri.com, 3D Analyst, ACORN, Address Coder, ADF, AML, ArcAtlas, ArcCAD, ArcCatalog, ArcCOGO, ArcData, ArcDoc,

ArcEdit, ArcEditor, ArcEurope, ArcExplorer, ArcExpress, ArcGIS, arcgis.com, ArcGlobe, ArcGrid, ArcIMS, ARC/INFO, ArcInfo,

ArcInfo Librarian, ArcLessons, ArcLocation, ArcLogistics, ArcMap, ArcNetwork, ArcNews, ArcObjects, ArcOpen, ArcPad,

ArcPlot, ArcPress, ArcPy, ArcQuest, ArcReader, ArcScan, ArcScene, ArcSchool, ArcScripts, ArcSDE, ArcSdl, ArcSketch,

ArcStorm, ArcSurvey, ArcTIN, ArcToolbox, ArcTools, ArcUSA, ArcUser, ArcView, ArcVoyager, ArcWatch, ArcWeb, ArcWorld,

ArcXML, Atlas GIS, AtlasWare, Avenue, BAO, Business Analyst, Business Analyst Online, BusinessMAP, CityEngine,

Community, Community Analyst, CommunityInfo, Community Maps, Database Integrator, DBI Kit, EDN, Esri, esri.com,

Esri—Team GIS, Esri—The GIS Company, Esri—The GIS People, Esri—The GIS Software Leader, FormEdit, GeoCollector,

GeoEnrichment, GeoEvent, Geographic Design System, Geography Matters, Geography Network, geographynetwork.com,

Geoloqi, GeoPlanner, Geoportal, Geotrigger, GIS by Esri, gis.com, GISData Server, GIS Day, gisday.com, GIS for Everyone,

Insights, JTX, MapIt, Maplex, MapObjects, MapStudio, ModelBuilder, MOLE, MPS—Atlas, PLTS, Rent-a-Tech, SDE, SML,

Sourcebook·America, SpatiaLABS, Spatial Database Engine, Story Map Countdown, Story Map Journal, Story Map Playlist,

Story Map Shortlist, Story Map Spyglass, Story Map Swipe, Story Map Tabbed, Story Map Tour, StreetMap, Tapestry, the

ARC/INFO logo, the ArcGIS Explorer logo, the ArcGIS logo, the ArcPad logo, the Esri globe logo, the Esri Press logo, The

Geographic Advantage, The Geographic Approach, the GIS Day logo, the MapIt logo, The World’s Leading Desktop GIS,

Water Writes, and Your Personal Geographic Information System are trademarks, service marks, or registered marks of

Esri in the United States, the European Community, or certain other jurisdictions. CityEngine is a registered trademark of

Procedural AG and is distributed under license by Esri.

Other companies and products or services mentioned herein may be trademarks, service marks, or registered marks of

their respective mark owners.

http://creativecommons.org/licenses/by/4.0/legalcode


Table of Contents Esri geodatabase data model templates ...................................................................................................... 7

Goal of the Esri UPDM .................................................................................................................................. 7

The UPDM 2019 Edition Geodatabase ......................................................................................................... 8

Assemblies .................................................................................................................................................. 10

Feature Class Schema ......................................................................................................................... 11

Compressor Station ............................................................................................................................. 14

Meter Setting ...................................................................................................................................... 22

Regulator Station ................................................................................................................................ 29

Rural Tap ............................................................................................................................................. 38

Town Border Station ........................................................................................................................... 47

Wellhead ............................................................................................................................................. 56

Pigging Structure ................................................................................................................................. 64

Fitting Assembly .................................................................................................................................. 72

Pump Station ....................................................................................................................................... 78

Lines ............................................................................................................................................................ 85

Feature Class Schema ......................................................................................................................... 86

Pipes .................................................................................................................................................... 90

Service Line ....................................................................................................................................... 107

Station Pipe ....................................................................................................................................... 120

Bonding Line ...................................................................................................................................... 129

Test Lead Wire .................................................................................................................................. 140

Rectifier Cable ................................................................................................................................... 149

Devices ...................................................................................................................................................... 159

Feature Class Schema ....................................................................................................................... 160

Excess Flow Valve .............................................................................................................................. 164

Meter ................................................................................................................................................ 175

Controllable Valve ............................................................................................................................. 187

Flow Valve ......................................................................................................................................... 200

Relief Valve........................................................................................................................................ 212

Scrubber ............................................................................................................................................ 224

Strainer .............................................................................................................................................. 236


Pressure Monitoring Device .............................................................................................................. 248

Lamp .................................................................................................................................................. 260

Compressor ....................................................................................................................................... 272

Wellhead Source Flange.................................................................................................................... 284

Controllable Tee ................................................................................................................................ 292

Short Stop ......................................................................................................................................... 304

Anode ................................................................................................................................................ 316

Rectifier ............................................................................................................................................. 326

Test Point .......................................................................................................................................... 336

Pump ................................................................................................................................................. 346

Regulator ........................................................................................................................................... 355

Junctions ................................................................................................................................................... 367


Coupling ............................................................................................................................................ 371

Elbow ................................................................................................................................................. 381

End Cap ............................................................................................................................................. 391

Expansion Joint ................................................................................................................................. 401

Flange ................................................................................................................................................ 411

Reducer ............................................................................................................................................. 421

Tee ..................................................................................................................................................... 432

Transition .......................................................................................................................................... 442

Weld .................................................................................................................................................. 452

Screw ................................................................................................................................................. 461

Electro Stop ....................................................................................................................................... 471

Plastic Fusion ..................................................................................................................................... 481

Saddle ................................................................................................................................................ 490

Tank ................................................................................................................................................... 500

Line Heater ........................................................................................................................................ 510

Cooling System .................................................................................................................................. 520

Odorizer ............................................................................................................................................ 528

Coupon .............................................................................................................................................. 538

Dehydration Equipment .................................................................................................................... 546


Drip .................................................................................................................................................... 556

Connection Point............................................................................................................................... 566

Wire Junction .................................................................................................................................... 570

Insulation Junction ............................................................................................................................ 579

Structure Boundary ................................................................................................................................... 588


Pipeline Station Structure ................................................................................................................. 591

Pipeline Vault Boundary .................................................................................................................... 597

Pipeline Processing Facility ............................................................................................................... 603

Structure Junction ..................................................................................................................................... 607


Pipeline Muffler ................................................................................................................................ 610

Pipeline Anchor ................................................................................................................................. 615

Pipeline Pipe Support ........................................................................................................................ 620

Pipeline Pipe Hanger ......................................................................................................................... 625

Pipeline End Connection ................................................................................................................... 630

Pipeline Vault .................................................................................................................................... 635

Pipeline Valve Box ............................................................................................................................. 639

Structure Line ............................................................................................................................................ 643


Pipeline Pipe Casing .......................................................................................................................... 646

Inspections ................................................................................................................................................ 656

Casing Inspection .............................................................................................................................. 657

CP Bond Inspection ........................................................................................................................... 660

CP Rectifier Inspection ...................................................................................................................... 663

CP Test Point Reading ....................................................................................................................... 666

Crossing Inspection ........................................................................................................................... 669

Electric Survey ................................................................................................................................... 671

Excavation Damage ........................................................................................................................... 673

Exposed Pipe Inspection ................................................................................................................... 679

Gas Leak Inspection .......................................................................................................................... 684

Isolated Pipe Inspection .................................................................................................................... 687


Inspection Note ................................................................................................................................. 689

Inspection Range ............................................................................................................................... 693

Leak Survey Area ............................................................................................................................... 698

Line Valve Inspection ........................................................................................................................ 701

Regulator Inspection ......................................................................................................................... 703

Relief Valve Inspection ...................................................................................................................... 707

Station Visual Inspection ................................................................................................................... 710

Strainer Inspection ............................................................................................................................ 713

Valve Inspection ................................................................................................................................ 715

ArcGIS Pipeline Referencing ...................................................................................................................... 718

Calibration Point ............................................................................................................................... 719

Centerline .......................................................................................................................................... 721

Centerline Sequence ......................................................................................................................... 723

Continuous Network ......................................................................................................................... 725

Engineering Network ........................................................................................................................ 727

Redline .............................................................................................................................................. 729

Maintenance ............................................................................................................................................. 731

Coupon .............................................................................................................................................. 732

Gas Leaks ........................................................................................................................................... 734

Identified Issue .................................................................................................................................. 740

Leak Repair ........................................................................................................................................ 744

Squeeze Off ....................................................................................................................................... 749

Environment ............................................................................................................................................. 753

Drinking Water .................................................................................................................................. 754

Ecological Area .................................................................................................................................. 756

Elevation ........................................................................................................................................... 758

High Populated Area ......................................................................................................................... 761

Navigable Waterway ......................................................................................................................... 763

Other Populated Area ....................................................................................................................... 765

Outside Area ..................................................................................................................................... 767

Structure Footprint ........................................................................................................................... 770

Structure Point .................................................................................................................................. 773


Inline Inspection ........................................................................................................................................ 778

ILI Ground Ref Markers ..................................................................................................................... 779

ILI Inspection Range .......................................................................................................................... 783

ILI Survey Group ................................................................................................................................ 788

ILI Survey Readings ........................................................................................................................... 793

Inline Inspection ................................................................................................................................ 798

Integrity ..................................................................................................................................................... 802

Anomaly ............................................................................................................................................ 803

Anomaly Group ................................................................................................................................. 808

Centerline Accuracy .......................................................................................................................... 812

Consequence Segment ..................................................................................................................... 816

Could Affect Segment ....................................................................................................................... 821

DA Survey Readings .......................................................................................................................... 825

Document Point ................................................................................................................................ 829

DOT Class .......................................................................................................................................... 832

High Consequence Area .................................................................................................................... 836

MAOP Calculated Range ................................................................................................................... 838

Operating Pressure Range ................................................................................................................ 843

Pipe Crossing ..................................................................................................................................... 847

Pipe Exposure .................................................................................................................................... 852

Pipeline Marker ................................................................................................................................. 856

Test Pressure Range .......................................................................................................................... 861

Mapping .................................................................................................................................................... 866

Alignment Sheet ................................................................................................................................ 867

Capital Project ................................................................................................................................... 869

Pipe Job Separator ............................................................................................................................ 871


Esri geodatabase data model templates The availability of a practical and up-to-date data model template, tailored to the unique needs of an

industry, is one of the keys to GIS project success at companies, whether their use of Esri software is

new or long-standing. For this reason, Esri collaborates with industry and academic leaders to

continually evolve a range of geodatabase data model templates. The intent of Esri data model

templates is to provide users with a best practice, industry-specific starting point. Most users start with

these data model templates; then they refine and extend them to meet their specific needs and

requirements. Esri data model templates just work with the ArcGIS platform and reflect Esri’s view of

best data model practice.

The Esri Utility and Pipeline Data Model (UPDM) is a geodatabase data model template for operators of

pipe networks in the gas and hazardous liquids industries. UPDM is a moderately normalized data model

that explicitly represents each physical component of a gas pipe network from the wellhead to the

customer meter, or a hazardous liquids pipe network from the wellhead to the terminal or delivery

point, in a single database table object.

Esri thanks all those who contributed their time and talents to the improvement of the Esri Utility and

Pipeline Data Model for the good of the community and of all Esri users in the pipeline and gas

industries.

Goal of the Esri UPDM The goal of the Esri UPDM is to make it easier, quicker, and more cost-effective for pipelines and gas

utilities to implement the ArcGIS platform. The Esri UPDM accomplishes this by freely providing a data

model that takes full advantage of the capabilities of the geodatabase. The data model is created and

tested with ArcGIS products to ensure that it works. This significantly reduces the complexity, time, and

cost to implement a spatially enabled pipeline or gas data repository.

Keeping up with the advancements of the geodatabase is an ongoing activity. Esri software development

staff continue to enhance and evolve the capabilities of the geodatabase. In addition to the data model

representing a best practice on how to leverage the geodatabase, the data model also represents a

repository of industry knowledge. Much of the structure and content of this data model is based on

feedback from Esri’s users as well as lessons learned from the large number of implementations of

ArcGIS in the pipeline and gas industries.

Because the Esri UPDM is built specifically for the ArcGIS family of products, it can be implemented as-is,

without modification to ArcGIS products.


The UPDM 2019 Edition Geodatabase The feature classes and tables that comprise the UPDM 2019 Edition Geodatabase are organized into

the following three groups:

• Stand-alone feature classes and tables

• Pipe System feature dataset

The stand-alone feature classes and tables grouping is composed of 21 feature classes and 15 tables.

UPDM 2019 Geodatabase

PipeSystem Feature Dataset

Stand-alone Feature Classes and Tables

P_AlignmentSheet

P_CapitalProject

P_CasingInspection

P_Centerline_Sequence

P_Coupon

P_CPBondInspection

P_CPRectifierInspection

P_CPTestPointReading

P_CrossingInspection

P_DrinkingWater

P_EcologicalArea

P_ElectricSurvey

P_ExcavationDamage

P_ExposedPipeInspect

P_GasLeak

P_GasLeakInspect

P_HighPopulatedArea

P_IdentifiedIssue

P_IsolatedPipeInspection

P_LeakRepairs

P_LeakSurveyArea

P_LineValveInspection

P_NavigableWaterway

P_OtherPopulatedArea

P_OutsideArea

P_PipeCrossing

P_PipeJobSeparator

P_PipelineMarker

P_RegulatorInspect

P_ReliefValveInspection

P_SqueezeOff

P_StationVisualInspection

P_StrainerInspect

P_StructureFootPrint

P_StructurePoint

P_Valve Inspection


The Pipe System feature dataset contains the pipe system, cathodic protection system assets, and

feature classes associated with managing the information about the integrity of the pipe system. These

are stored in 35 feature classes.

ServiceArea

StructureBoundary

StructureJunction

StructureLine

PipelineAssembly

PipelineDevice

PipelineJunction

PipelineLine

PipelineSubnetLine

P_Anomaly

P_AnomalyGroup

P_CalibrationPoint

P_Centerline

P_CenterlineAccuracy

P_ConsequenceSegment

P_ContinuousNetwork

P_CouldAffectSegment

P_DASurveyReadings

P_DocumentPoint

P_DOTClass

P_Elevation

P_EngineeringNetwork

P_HighConsequenceArea

P_ILIGroundRefMarkers

P_ILIInspectionRange

P_ILISurveyGroup

P_ILISurveyReadings

P_InlineInspection

P_InspectionNote

P_InspectionRange

P_MAOPCalcRange

P_OperatingPressRange

P_PipeExposure

P_Redline

P_TestPressureRange


Assemblies Definition: The Assembly feature class models the assemblies and stations of a pipe system. Upon initial

creation, Assembly is a simple point feature representation of the station with a schema to describe the

contents of the station. This follows the industry legacy practice of representing these multiple asset

facilities with a simple cartographic display. The emerging industry practice is to use the ArcGIS platform

to track all assets for the life of the asset. This industry best practice requires a detailed inventory of the

assets within the assembly facility.

To ensure the ease of implementation of this emerging industry best practice, all assemblies are

preconfigured with the ability to support containers. Using containers allows for the complete modeling

of the internals of a facility. For example, a Regulator Station assembly contains one or more Regulators

plus associated components such as valves, fittings, and station piping. On the map, this regulator

station will appear as one feature, but the internal assets can be examined in the container view or

network diagram.

Derived Feature Layers:

The following are the general types of associations for assemblies:

• An assembly can contain the following:

o Devices—For example, a compressor station contains one or more compressors.

o Junctions—For example, a compressor station contains one or more cooling

systems.

o Lines—For example, a compressor station contains one or more coated steel station

pipe segments.

• An assembly can be contained by the following:

o Structure boundary—For example, a regulator station can be contained by a

structure boundary vault

Assembly

CompressorStation

FittingAssembly

MeterSetting

PigStructure

PumpStation

RegulatorStation

RuralTap

Town BorderStation

Wellhead


Feature Class Schema

This is the schema for the Assembly feature class.

Attribute Name Data Type Description

assetgroup Long Integer Required for Utility Network

assettype Short Integer Required for Utility Network

associationstatus Short Integer Required for Utility Network

creationdate Date Required for Utility Network

creator Text(255) Required for Utility Network

lastupdate Date Required for Utility Network

updatedby Text(255) Required for Utility Network

Globalid Global ID Required for Geodatabase

Regulatorytype Short Integer

Vault Short Integer

Installationdate Date

Inservicedate Date

Assetid Text(64)

Name Text(20)

Ownedby Short Integer

Maintby Short Integer

Locationdescription Text(255)

Lifecyclestatus Short Integer Network Attribute

Pipelineoperatornumber Short Integer

Supplier Short Integer

Pressurerating Double(16,5)

Mopin Double(16,5)

Mopout Double(16,5)

Sopin Double(16,5)

Sopout Double(16,5)

Rotation Short Integer

Prottype Short Integer

Systemsubnetworkname Text(2000) Automatically added to Utility Network

Pressuresubnetworkname Text(2000) Automatically added to Utility Network

Isolationsubnetworkname Text(2000) Automatically added to Utility Network

Cpsubnetworkname Text(2000) Automatically added to Utility Network

Pipelineoperator Text(50)


pressureunits Short Integer

bypassindicator Short Integer

designcapacity Double(16,5)

designcapacityunits Short Integer

diameter Double(16,5)

diameterunits Short Integer

pipegrade Text(2)

wallthickness Double(10,6)

manufacturer Text(5)

pipematerial Text(30)

structurelength Double(16,5)

lengthunits Short Integer

materialclass Text(20)

connectiontype Text(30)

outletvalvetype Text(30)

pressureratingunits Text(30)

odorizerindicator Short Integer

shutoffvalvediameter Double(10,6)

shutoffvalvetype Text(25)

tapdiameter Double(10,6)

taptype Text(20)

totalpower Double(10,6)

numberofengines Short Integer

numberofturbines Short Integer

numberofmotors Short Integer

numberofunits Short Integer

comments Text(255)

spatialaccuracy SHORT

gpsx Double(16,8)

gpsy Double(16,8)

gpsz Double(16,8)

legacyid Text(38)

workorderid Text(38)

projectnumber Text(38)

assetunitcode Text(38)


servicesummaryid GUID

eventid Text(38)

fromdate Date

todate Date

locationerror Text(100)

engrouteid Text(38)

engroutename Text(100)

engm Double(16,5)

continrouteid Text(38)

continroutename Text(100)

continm Double(16,5)

refmethod Short Integer

reflocation Text(50)

refoffset Text(50)


Compressor Station

The subtype feature layer Compressor Station describes the facility in the natural gas

transmission pipeline portion of the pipe system responsible for increasing pressure in the

downstream pipeline. A compressor station is composed of one or more compressors plus other

supporting components such as cooling systems, valves, fittings, and station piping.

GeometryType: Point with z- and m-values enabled

Relationships:

-UPDMAssembly__ATTACHREL

Asset Groups/Asset Types:

Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a compressor station

whose type is not known.

1 161 Compressor

Station

A compressor station is a pressure

elevation facility composed of one or

more compressor systems.

Container: Yes

Attachments: Yes

Editor Tracking:

Editor Tracking Value Column Name

Creator Field creator

Create Date Field creationdate

Update Editor Field updatedby

Update Edit Date Field lastupdate


Attributes:

objectid (Long Integer)—The geodatabase generated and maintained unique identifier value.

assetgroup (Long Integer)—The geodatabase subtype field. The subtype field models general

classes of features.

assettype (Short Integer)—Discriminator field with a subtype-specific coded domain.

associationstatus (Short Integer) —An indicator of the type of utility network association to

which the assembly feature participates.

Coded Value Domain: Pipeline_AssociationStatus.

creationdate (Date)—The date and time the compressor station record was originally created in

the geodatabase. This value is automatically populated by the Editor Tracking.

creator (Text[255])—The name of the system user who originally created the compressor station

record in the geodatabase. This value is automatically populated by the Editor Tracking.

lastupdate (Date)—The date and time the compressor station record was last modified in the

geodatabase. This value is automatically populated by the Editor Tracking.

updatedby (Text[255])—The name of the system user responsible for the last modification to

the compressor station record in the geodatabase. This value is automatically populated by the

Editor Tracking.

globalid (GlobalID)—The systemwide unique identifier. This is the primary key value for

relationships to child tables.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the compressor

station.

Coded Value Domain: Pipeline_LifeCycle_Status_Combined

installdate (Date)—The date the construction of the compressor station was completed.

inservicedate (Date)—The date the compressor station was put into production.

name (Text[50])—The textual name used within the organization to refer to the compressor

station.


legacyid (Text[38])—A unique identifier used to relate this record to its predecessor record from

a previous mapping or asset system. This provides continuity between the old system and the

current Utility and Pipeline Data model.

mopin (Double[16,5])—The maximum operating pressure allowed to enter the compressor

station.

mopout (Double[16,5])—The maximum operating pressure allowed to exit the compressor station. sopin (Double[16,5])—The standard operating pressure allowed to enter the compressor

station.

sopout (Double[16,5])—The standard operating pressure allowed to exit the compressor station.

totalpower (Double[10,6])—The summation of the power of all units in the compressor station.

numberofengines (Short Integer)—The number of engines in the compressor station.

numberofturbines (Short Integer)—The number of turbines in the compressor station.

numberofmotors (Short Integer)—The number of motors in the compressor station.

regulatorytype (Short Integer)—The value indicating whether the compressor station is part of

the Transmission, Offshore Transmission, Gathering, or Offshore Gathering system.

Coded Value Domain: Pipeline_Regulatory_Type

locationdescription (Text[255])—The textual description of the location of the compressor

station.

rotation (Short Integer)—The numerical value indicating the number of degrees the compressor

station should be rotated in a map display. This is typically done to have the symbol match the

orientation of the associated pipe segments.

Range Domain: Symbol_Rotation

eventid (Text[38])—The unique ID for each event record. This attribute is only used by

organizations wanting to maintain the Compressor Station features as event records with the

ArcGIS Pipeline Referencing tools. The value is automatically generated and populated by the

ArcGIS Pipeline Referencing tools.

fromdate (Date)—The date the event became active on the route. This attribute is only used by





todate (Date)—The date the event was retired from the route. This attribute is only used by




locationerror (Text[100])—The resultant message from the process of defining the event’s

location on a route. This attribute is only used by organizations wanting to maintain the

Compressor Station features as event records with the ArcGIS Pipeline Referencing tools. The

value is automatically generated and populated by the ArcGIS Pipeline Referencing tools.

engrouteid (Text[38])—The unique ID of the engineering network route where the event is

located. This attribute is only used by organizations wanting to maintain the Compressor Station

features as event records with the ArcGIS Pipeline Referencing tools. The value is automatically

generated and populated by the ArcGIS Pipeline Referencing tools.

engroutename (Text[100])—The name of the engineering network route where the event is

located. This attribute is only used by organizations wanting to maintain the Compressor Station



engm (Double[16,5])—The measure location along the engineering network route where the

anomaly is located. This attribute is only used by organizations wanting to maintain the

Compressor Station features as event records with the ArcGIS Pipeline Referencing tools. The


continrouteid (Text[38])—The continuous network route ID that is automatically created and

maintained by the ArcGIS Pipeline Referencing tools. This attribute is only used by organizations

wanting to maintain the Compressor Station features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100])—The continuous network name that is automatically created and


wanting to maintain the Compressor Station features as event records with the ArcGIS Pipeline

Referencing tools.

continm (Double[16,5])—The continuous network measure along the continrouteid route. This

value is automatically created and maintained by the ArcGIS Pipeline Referencing tools.


refmethod (Short Integer)—The method of referencing the offset feature. This can be

Coordinates, Stationing, Length, LRS Network, Event Intersection, or other point feature class.

This attribute is only used by organizations wanting to maintain the Compressor Station features

as event records with the ArcGIS Pipeline Referencing tools. The value is populated by the


reflocation (Text[50])—The location of the offsetting feature. This can be Coordinates,

Feature/EventID, and/or IntersectionID. This attribute is only used by organizations wanting to

maintain the Compressor Station features as event records with the ArcGIS Pipeline Referencing

tools. The value is populated by the ArcGIS Pipeline Referencing tools.

refoffset (Text[50])—The offset measure. This attribute is only used by organizations wanting to

maintain the Compressor Station features as event records with the ArcGIS Pipeline Referencing


spatialaccuracy (Short Integer)—This short integer value provides an assessment of the spatial

accuracy of the coordinates of the feature’s geometry when the feature is included in the

geodatabase.

Coded Domain: Spatial_Accuracy

gpsx (Double[16,8])—The longitudinal coordinate of the feature when it was originally included

in the geodatabase. If using the attribute rules capability, this value can be automatically

populated.

gpsy (Double[16,8])—The latitudinal coordinate of the feature when it was originally included in

the geodatabase. If using the attribute rules capability, this value can be automatically

populated.

gpsz (Double[16,8])—The elevation coordinate of the feature when it was originally included in


populated.

systemsubnetworkname (Text[2000])—The name of the system tier subnetwork where the

compressor station is located.

pressuresubnetworkname (Text[2000])—The name of the pressure tier subnetwork where the

compressor station is located.

isolationsubnetworkname (Text[2000])—The name of the isolation tier subnetwork where the compressor station is located.


cpsubnetworkname (Text[2000])—The name of the cathodic protection tier subnetwork where the compressor station is located.


Compressor Station Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016:

P_CompressorStation

assetgroup Asset Group N/A

assettype Asset Type N/A

associationstatus Association Status N/A

creator Creator CREATIONUSER

creationdate Creation Date creationdate

updatedby Last User LASTUSER

lastupdate Last Update DATEMODIFIED

globalid GlobalID GlobalID

lifecyclestatus Life Cycle Status STATUS

installdate Install Date INSTALLATIONDATE

inservicedate In Service Date N/A

rotation Symbol Rotation SYMBOLROTATION

name Station Name STATIONNAME

legacyid Legacy ID LEGACYID

mopin MOP IN N/A

mopout MOP OUT N/A

sopin SOP IN N/A

sopout SOP OUT N/A

totalpower Total Power TOTALHORSEPOWER

numberofengines Number of Engines NUMBEROFENGINES

numberofturbines Number of Turbines NUMBEROFTURBINES

numberofmotors Number of Motors NUMBEROFMOTORS


locationdescription Location Description LOCATIONDESCRIPTION

regulatorytype Regulatory Type SYSTEMTYPE

eventid EventID EVENTID

fromdate From Date FROMDATE

todate To Date TODATE

locationerror Location Error LOCATIONERROR

engrouteid Engineering RouteID ENGROUTEID

engroutename Engineering Route Name ENGROUTENAME

engm Engineering Measure ENGM

continrouteid Continuous Measure CONTINROUTEID

continroutename Continuous Route Name CONTINROUTENAME

continm Continuous Measure CONTINM

refmethod Reference Method REFMETHOD

reflocation Reference Location REFLOCATION

refoffset Reference Offset REFOFFSET

spatialaccuracy Spatial Accuracy Spatial Accuracy

gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A


Meter Setting

The subtype feature layer Meter Setting describes the facility in the pipe system that contains

meters, regulators, and risers to monitor and record the volume and flow.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a meter setting


2 41 Meter Setting A generic meter setting.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:




assettype (Short Integer)—Discriminator field with a subtype-specific coded domain.




creationdate (Date)—The date and time the meter setting record was originally created in the


creator (Text[255])—The name of the system user who originally created the meter setting


lastupdate (Date)—The date and time the meter setting record was last modified in the



the meter setting record in the geodatabase. This value is automatically populated by the Editor

Tracking.



regulatorytype (Short Integer)—The value indicating whether the meter setting is part of the

Transmission, Offshore Transmission, Gathering, or Offshore Gathering system.


installdate (Date)—The date the construction of the meter setting was completed.

inservicedate (Date)—The date the meter setting was put into production.

assetid (Text[64])—A layer-specific textual unique identifier.

ownedby (Short Integer)—The name of the organization with ownership of the meter setting. In

most instances, this will be the name of your organization.

Coded Value Domain: Asset_Owner


maintby (Short Integer)—The name of the organization responsible for the operation and

maintenance of the meter setting. In most instances, this will be the name of your organization.

Coded Value Domain: Asset_Manager

locationdescription (Text[255])—The textual description of the location of the meter setting.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the meter setting.


bypassindicator (Short Integer)—The yes/no Boolean value indicating whether the meter setting

includes a bypass.

Coded value domain: Yes_No

rotation (Short Integer)–The numerical value indicating the number of degrees the meter setting

should be rotated in a map display. This is typically done to have the symbol match the




organizations wanting to maintain the Meter Setting features as event records with the ArcGIS

Pipeline Referencing tools. The value is automatically generated and populated by the ArcGIS

Pipeline Referencing tools.









locationerror(Text[100])—The resultant message from the process of defining the event’s

location on a route. This attribute is only used by organizations wanting to maintain the Meter

Setting features as event records with the ArcGIS Pipeline Referencing tools. The value is

automatically generated and populated by the ArcGIS Pipeline Referencing tools.


located. This attribute is only used by organizations wanting to maintain the Meter Setting





located. This attribute is only used by organizations wanting to maintain the Meter Setting




anomaly is located. This attribute is only used by organizations wanting to maintain the Meter

Setting features as event records with the ArcGIS Pipeline Referencing tools. The value is




wanting to maintain the Meter Setting features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the Meter Setting features as event records with the ArcGIS Pipeline

Referencing tools.





This attribute is only used by organizations wanting to maintain the Meter Setting features as

event records with the ArcGIS Pipeline Referencing tools. The value is populated by the ArcGIS




maintain the Meter Setting features as event records with the ArcGIS Pipeline Referencing tools.

The value is populated by the ArcGIS Pipeline Referencing tools.

refoffset(Text[50])—The offset measure. This attribute is only used by organizations wanting to

maintain the Meter Setting features as event records with the ArcGIS Pipeline Referencing tools.





geodatabase.


gpsx(Double[16,8])—The longitudinal coordinate of the feature when it was originally included


populated.



populated.



populated.

workorderid (Text[38])—The work order management system value used to identify the task

number under which the work order was issued to construct the meter setting.

projectnumber (Text[38])—The work order management system value used to identify the

project number under which the work order was issued to construct the meter setting.





meter setting is located.


meter setting is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the meter setting is located. cpsubnetworkname (Text[2000])—The name of the cathodic protection tier subnetwork where the meter setting is located.


Meter Setting Migration Table UPDM 2016 to UPDM 2019:


P_MeterSetting




creationdate Creation date CREATIONUSER

creator Creator DATECREATED

lastupdate Last update LASTUSER

updatedby Updated by DATEMODIFIED

globalid Global ID GlobalID




assetid Facility ID FACILITYID

name Premise PREMISE

ownedby Owner OWNER

maintby Maintained By N/A



rotation Rotation SYMBOLROTATION

bypassindicator Bypass Indicator BYPASSINDICATOR

legacyid LegacyID LEGACYID

projectnumber Project Number PROJECTNUMBER

workorderid Work Order ID WORKORDERID


servicesummaryid Service SummaryID SERVICESUMMARY_Glo

balID

spatialaccuracy Spatial Accuracy SPATIALACCURACY

gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z GPSZ

n/a GASTRACEWEIGHT

eventid Event ID EVENTID




engrouteid Engineering Route ID ENGROUTEID



continrouteid Continuous Route ID CONTINROUTEID







Regulator Station

The subtype feature layer Regulator Station describes the facility within a pipeline that contains

the regulators, valves, and piping to change the pressure of the fluid or gas in the pipe system.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a regulator station


3 81 Regulator

Station

A generic regulator station.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:




assettype (Short Integer)—A discriminator field with a subtype-specific coded domain.




creationdate (Date)—The date and time the regulator station record was originally created in


creator (Text[255])—The name of the system user who originally created the regulator station


lastupdate (Date)—The date and time the regulator station record was last modified in the



the regulator station record in the geodatabase. This value is automatically populated by the

Editor Tracking.



regulatorytype (Short Integer)—The value indicating whether the meter setting is part of the

Transmission, Offshore Transmission, Gathering, or Offshore Gathering system.


vault (Short Integer)—The yes/no Boolean value indicating whether the regulator station is contained in a vault. Coded Value Domain: Yes_No

installdate (Date)—The date the construction of the regulator station was completed.

inservicedate (Date)—The date the regulator station was put into production.



name (Text[20])—The textual name used within the organization to refer to the regulator

station.

ownedby (Short Integer)—The name of the organization with ownership of the regulator station.

In most instances, this will be the name of your organization.



maintenance of the regulator station. In most instances, this will be the name of your

organization. Coded Value Domain: Asset_Manager

locationdescription (Text [255])—The textual description of the location of the regulator station. lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the regulator

station.


mopin (Double[16,5])—The maximum operating pressure allowed to enter the regulator station.

mopout (Double[16,5])—The maximum operating pressure allowed to exit the regulator station. sopin (Double[16,5])—The standard operating pressure allowed to enter the regulator station.

sopout (Double[16,5])—The standard operating pressure allowed to exit the regulator station.

rotation (Short Integer)—This value defines the angular degrees that the point symbol should be rotated. The purpose is to have the regulator station’s display symbology automatically rotated to the angle defined in this attribute. Range Domain: Symbol_Position

prottype (Short Integer)—The type of over pressure protection used in the regulator station. Coded Value Domain: Pipeline Over Pressure Protection Type

pressureunits (Short Integer)—The unit of measure for pressure for mopin, mopout, sopin, and sopout. Coded Value Domain: Units_For_Pressure

bypassindicator (Short Integer)—The yes/no Boolean value indicating whether the regulator station includes bypass piping. Coded Value Domain: Yes_No

designcapacity (Double[16,5])—The maximum flow rate through the regulator station. designcapacityunits (Short Integer)—The unit of measure for volume flow for designcapacity.


pipediameter (Double[16,5])—The nominal edge-to-edge measured length of a straight line

through the center of the outlet pipe.

Coded Value Domain: Pipeline_StationPipeDiameter

diameterunits (Short Integer)—The unit of measure for pipediameter. Coded Value Domain: Pipeline_Units_for_Diameter comments (Text[255])—The nonstructured information about the regulator station. legacyid (Text[38])—A unique identifier used to relate this table’s record to its predecessor record from a previous mapping system. This provides continuity between the old system and the current Utility and Pipeline Data Model. spatialaccuracy (Short Integer)—This short integer value provides an assessment of the spatial


geodatabase.




populated.



populated.



populated.

workorderid (Text[38])—The work order management system value used to identify the task number under which the work order was issued to construct the regulator station. projectnumber (Text[38])—The work order management system value used to identify the project number under which the work order was issued to construct the regulator station. eventid (Text[38])—The unique ID for each event record. This attribute is only used by

organizations wanting to maintain the Regulator Station features as event records with the














Regulator Station features as event records with the ArcGIS Pipeline Referencing tools. The



located. This attribute is only used by organizations wanting to maintain the Regulator Station




located. This attribute is only used by organizations wanting to maintain the Regulator Station




anomaly is located. This attribute is only used by organizations wanting to maintain the

Regulator Station features as event records with the ArcGIS Pipeline Referencing tools. The




wanting to maintain the Regulator Station features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the Regulator Station features as event records with the ArcGIS Pipeline

Referencing tools.






This attribute is only used by organizations wanting to maintain the Regulator Station features





maintain the Regulator Station features as event records with the ArcGIS Pipeline Referencing



maintain the Regulator Station features as event records with the ArcGIS Pipeline Referencing


assetunitcode (Text[38])—The foreign key value used to link this record to the asset’s corresponding record in the asset management system.


regulator station is located.


regulator station is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the regulator station is located.


Regulator Station Migration Table UPDM 2016 to UPDM 2019:


P_RegulatorStation

assetgroup Asset group N/A

assettype Asset type N/A



creationdate Date Created DATECREATED


updatedby Updated By LASTUSER


regulatorytype Regulatory Type N/A

vault Vault VAULT





ownedby Owner OWNER





mopin MOP In MOPIN

mopout MOP Out MOPOUT

sopin SOP In SOPIN


sopout SOP Out SOPOUT


prottype Over Pressure

Protection Type

OVERPRESSUREPROTECTIO

NTYPE

pressureunits Pressure Units N/A


n/a Insulated Indicator INSULATEDINDICATOR

n/a Present Status PRESENTSTATUS

designcapacity Design Capacity DESIGNCAPACITY

designcapacityunits Design Capacity Units N/A

pipediameter Pipe Diameter PIPEDIAMETER

diameterunits Diameter Units N/A

n/a Regulatory Type SYSTEMTYPE

comments Comments COMMENTS



assetunitcode Asset Unit Code ASSETUNITCODE


gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A

n/a GASTRACEWEIGHT






engroutename Engineering Route

Name

ENGROUTENAME



continrouteid Continuous RouteID CONTINROUTEID

continroutename Continuous Route

Name

CONTINROUTENAME






Rural Tap

The derived point feature layer RuralTap describes the facility on a transmission pipeline used to

serve gas to rural residential and industrial customers. This facility is also commonly referred to

as a farm tap.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a rural tap whose type

is not known.

4 121 Rural Tap A generic rural tap.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:








creationdate (Date)—The date and time the rural tap record was originally created in the


creator (Text[255])—The name of the system user who originally created the rural tap record in


lastupdate (Date)—The date and time the rural tap record was last modified in the geodatabase.

This value is automatically populated by the Editor Tracking.


the rural tap record in the geodatabase. This value is automatically populated by the Editor

Tracking.



regulatorytype (Short Integer)—The value indicating whether regulations require the rural tap to

be considered a participant in the Distribution, Transmission, or Gathering portion of the pipe

system. The default value is Transmission.


vault (Short Integer)—The yes/no Boolean value indicating whether the rural tap is contained in a vault. Coded Value Domain: Yes_No

installdate (Date)—The date the construction of the rural tap was completed.

inservicedate (Date)—The date the rural tap was put into production.



name (Text[20])—The textual name used within the organization to refer to the rural tap.

ownedby (Short Integer)—The name of the organization with ownership of the rural tap. In most

instances, this will be the name of your organization.



maintenance of the rural tap. In most instances, this will be the name of your organization.


locationdescription (Text[255])—The textual description of the location of the rural tap.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the rural tap.


rotation (Short Integer)—This value defines the angular degrees that the point symbol should be

rotated. The purpose is to have the fitting display symbology automatically rotated to the angle

defined by this attribute.

Coded Value Domain: Symbol_Position

pipelineoperator (Text[50])—The name of the organization responsible for the operation and

maintenance of the pipeline connecting the rural tap.

supplier (Text[50])—The name of the organization responsible for supplying the commodity to

the organization.

mopin (Double[16,5])—The maximum operating pressure allowed to enter the rural tap.

mopout (Double[16,5])—The maximum operating pressure allowed to exit the rural tap. sopin (Double[16,5])—The standard operating pressure allowed to enter the rural tap.

sopout (Double[16,5])—The standard operating pressure allowed to exit the rural tap.

bypassindicator (Short Integer)—The yes/no Boolean value indicating whether the rural tap

includes bypass piping.

Coded Value Domain: Yes_No

odorizerindicator (Short Integer)—The yes/no Boolean value indicating whether the rural tap

odorizes the natural gas.



shutoffvalvediameter (Double[10,6])—The edge-to-edge nominal measurement length of a

straight line through the center of the rural tap shutoff valve orifice.

Coded Value Domain: Pipeline_ValveDiameter

shutoffvalvetype (Text[25])—The type of valve used in the rural tap for shutoff.

Coded Value Domain: Pipeline_ASTMFValve

tapdiameter(Double[10,6])—The edge-to-edge nominal measurement length of a straight line

through the center of the rural tap inflow tap orifice.

Coded Value Domain: Pipeline_ValveDiameter

taptype (Text[20])—The type of tap used in the rural tap.

diameterunits (Short Integer)—The unit of measure for TAPDIAMETER.

Coded Value Domain: Units_for_Diameter

comments (Text[255])—The nonstructured information about the rural tap.


number under which the work order was issued to construct the rural tap.


project number under which the work order was issued to construct the rural tap.

assetunitcode (Text[38])—The foreign key value used to link this record to the asset’s

corresponding record in an asset management system.

legacyid (Text[38])—A unique identifier used to relate this table’s record to its predecessor record from a previous mapping system. This provides continuity between the old system and the current Utility and Pipeline Data Model. spatialaccuracy (Short Integer)—This short integer value provides an assessment of the spatial


geodatabase.

Coded Domain: Spatial_Accuracy.



populated.




populated.



populated.


organizations wanting to maintain the Rural Tap features as event records with the ArcGIS




located. This attribute is only used by organizations wanting to maintain the Rural Tap features

as event records with the ArcGIS Pipeline Referencing tools. The value is automatically










engroutename (Text[100])—The engineering network name that is automatically created and


wanting to maintain the Rural Tap features as event records with the ArcGIS Pipeline

Referencing tools.


location on a route. This attribute is only used by organizations wanting to maintain the Rural

Tap features as event records with the ArcGIS Pipeline Referencing tools. The value is


engm (Double)—The measure location along the engineering network route where the anomaly

is located. This attribute is only used by organizations wanting to maintain the Rural Tap







Referencing tools.




Referencing tools.

continm (Double)—The continuous network measure along the continrouteid route. This value

is automatically created and maintained by the ArcGIS Pipeline Referencing tools.



This attribute is only used by organizations wanting to maintain the Rural Tap features as event

records with the ArcGIS Pipeline Referencing tools. The value is populated by the ArcGIS Pipeline

Referencing tools.



maintain the Rural Tap features as event records with the ArcGIS Pipeline Referencing tools. The

value is populated by the ArcGIS Pipeline Referencing tools.


maintain the Rural Tap features as event records with the ArcGIS Pipeline Referencing tools. The


systemsubnetworkname (Text[2000])—The name of the system tier subnetwork where the rural

tap is located.


rural tap is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the rural tap is located.


Rural Tap Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_RuralTap










vault Vault N/A



assetid Facility ID N/A

ownedby Owner OWNER


locationdescription Location Description N/A


name Station Name N/A


pipelineoperator Pipeline Operator PIPELINEOPERATOR

supplier Supplier N/A

mopin MOP IN N/A


mopout MOP OUT N/A

sopin SOP IN N/A

sopout SOP OUT N/A

bypassindicator Bypass Indicator N/A

odorizerindicator Odorizer Indicator ODORIZERINDICATOR

shutoffvalvediameter Shutoff Valve

Diameter

SHUTOFFVALVEDIAMETER

shutoffvalvetype Shutoff Valve Type SHUTOFFVALVETYPE

tapdiameter Tap Diameter TAPDIAMETER

taptype Tap Type TAPTYPE


comments Comments N/A





N/A GASTRACEWEIGHT

spatialaccuracy Spatial Accuracy N/A

gpsx GPS X N/A

gpsy GPS Y N/A

gpsz GPS Z N/A







Name

ENGROUTENAME





Name

CONTINROUTENAME






Town Border Station

The point derived feature layer Town Border Station describes the regulator station facility

within a pipeline that is also the point of transfer between the transmission system and the

distribution system. In distribution-only pipe systems, the town border station represents the

source of gas.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a town border

station whose type is not known.

5 161 Town Border

Station

A generic town border station.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:








creationdate (Date)—The date and time the town border station record was originally created in


creator (Text[255])—The name of the system user who originally created the town border

station record in the geodatabase. This value is automatically populated by the Editor Tracking.

lastupdate (Date)—The date and time the town border station record was last modified in the



the town border station record in the geodatabase. This value is automatically populated by the

Editor Tracking.

regulatorytype (Short Integer)—The value indicating whether regulations require the town

border station to be considered a participant in the Distribution, Transmission, or Gathering

portion of the pipe system. The default value is Transmission.


vault (Short Integer)—The yes/no Boolean value indicating whether the town border station is contained in a vault. Coded Value Domain: Yes_No



installdate (Date)—The date the construction of the town border station was completed.

inservicedate (Date)—The date the town border station was put into production. assetid (Text[64])—A layer-specific textual unique identifier.


name (Text[20])—The textual name used within the organization to refer to the town border

station.

ownedby (Short Integer)—The name of the organization with ownership of the town border

station. In most instances, this will be the name of your organization.



maintenance of the town border station. In most instances, this will be the name of your


locationdescription (Text[255])—The textual description of the location of the town border station. lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the town border

station.


comments (Text[255])—The nonstructured information about the town border station.

pipelineoperator (Text[50])—The name of the organization responsible for the operation and

maintenance of the pipeline connecting the town border station.

pipelineoperatorNUMBER (Text[20])—The U.S. DOT-issued unique identifier.

supplier (Text[50])—The name of the organization responsible for supplying the commodity to

the organization.

mopin (Double[16,5])—The maximum operating pressure allowed to enter the town border

station.

mopout (Double[16,5])—The maximum operating pressure allowed to exit the town border station. sopin (Double[16,5])—The standard operating pressure allowed to enter the town border

station.

sopout (Double[16,5])—The standard operating pressure allowed to exit the town border

station.


rotation (Short Integer)—This value defines the angular degrees that the point symbol should be rotated. The purpose is to have the town border station’s display symbology automatically rotated to the angle defined in this attribute. Range Domain: Symbol_Position

pressureunits (Short Integer)—The unit of measure for pressure for mopin, mopout, sopin, and sopout. Coded Value Domain: Units_For_Pressure prottype (Short Integer)—The type of over pressure protection used in the town border station. Coded Value Domain: Pipeline Over Protection Type bypassindicator (Short Integer)—The yes/no Boolean value indicating whether the town border station includes bypass piping. Coded Value Domain: Yes_No designcapacity (Double[16,5])—The maximum flow rate through the town border station. designcapacityunits (Short Integer)—The unit of measure of volume flow for designcapacity. pipediameter (Double[16,5])—The edge-to-edge nominal measured length of a straight line

through the center of the outlet pipe.

Coded Value Domain: Pipeline_Station_Pipe_Diameter

diameterunits (Short Integer)—The unit of measure for pipediameter. Coded Value Domain: Units_for_Diameter

legacyid (Text[38])—A unique identifier used to relate this table’s record to its predecessor record from a previous mapping system. This provides continuity between the old system and the current Utility and Pipeline Data Model. spatialaccuracy (Short Integer)—This short integer value provides an assessment of the spatial


geodatabase.




populated.



populated.




populated.

workorderid (Text[38])—The work order management system value used to identify the task number under which the work order was issued to construct the town border station. projectnumber (Text[38])—The work order management system value used to identify the project number under which the work order was issued to construct the town border station. assetunitcode (Text[38])—The foreign key value used to link this record to the asset’s corresponding record in the asset management system. eventid (Text[38])—The unique ID for each event record. This attribute is only used by

organizations wanting to maintain the Town Border Station features as event records with the












location on a route. This attribute is only used by organizations wanting to maintain the Town

Border Station features as event records with the ArcGIS Pipeline Referencing tools. The value is



located. This attribute is only used by organizations wanting to maintain the Town Border

Station features as event records with the ArcGIS Pipeline Referencing tools. The value is


engroutename (Text[100]) —The name of the engineering network route where the event is

located. This attribute is only used by organizations wanting to maintain the Town Border





anomaly is located. This attribute is only used by organizations wanting to maintain the Town

Border Station features as event records with the ArcGIS Pipeline Referencing tools. The value is




wanting to maintain the Town Border Station features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the Town Border Station features as event records with the ArcGIS Pipeline

Referencing tools.





This attribute is only used by organizations wanting to maintain the Town Border Station

features as event records with the ArcGIS Pipeline Referencing tools. The value is populated by

the ArcGIS Pipeline Referencing tools.



maintain the Town Border Station features as event records with the ArcGIS Pipeline

Referencing tools. The value is populated by the ArcGIS Pipeline Referencing tools.


maintain the Town Border Station features as event records with the ArcGIS Pipeline


systemsubnetworkname (Text[2000])—The name of the system tier subnetwork where the town

border station is located.


town border station is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the town border station is located.


Town Border Station Migration Table UPDM 2016 to UPDM 2019:


PTownBorderStation






lastupdate Last Updated DATEMODIFIED




vault Vault VAULT

globalid Global ID Global ID



inservicedate In Service Date INSERVICEDATE




ownedby Owner OWNER




mopin MOP In MOPIN


mopout MOP Out MOPOUT

sopin SOP In SOPIN

sopout SOP Out SOPOUT

pipelineoperator Pipeline Operator N/A

pipelineoperatornumber Pipeline Operator

Number

PIPELINEOPERATORNUMBE

R

supplier Supplier SUPPLIER

prottype Over Protection Type OVERPRESSUREPROTECTION

TYPE



designcapacity Design Capacity DESIGNCAPACITY

designcapacityunits Design Capacity Units N/A

N/A Insulated Indicator INSULATEDINDICATOR

pipediameter Pipe Diameter PIPEDIAMETER







N/A GASTRACEWEIGHT

N/A Present Status PRESENTSTATUS


gpsx GPS X N/A


gpsy GPS Y N/A

gpsz GPS Z N/A



todate TODATE TODATE



Name

ENGROUTENAME




Name

CONTINROUTENAME






Wellhead

The point derived feature layer Wellhead connects a well to the pipe system. These components

are used in the utility network as a source of the gas or liquid being transported through the

pipe system.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a wellhead whose

type is not known.

6 201 Mudline A wellhead designed for deeper

water that includes a series of

hangers called mudline suspension

equipment. 6 202 Subsea A wellhead located on the ocean

floor.

6 203 Surface A wellhead located on land.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:








creator (Text[50])—The name of the system user who originally created the object record in the


creationdate (Date)—The date and time the object record was originally created in the


lastupdate (Date)—The date and time the object record was last modified in the geodatabase.


updatedby (Text[50])—The name of the system user responsible for the last modification to the

object record in the geodatabase. This value is automatically populated by the Editor Tracking.



regulatorytype (Short Integer)—The value indicating whether regulations require the wellhead

to be considered a participant in the Transmission or Gathering portion of the pipe system. The

default value is Gathering.


installdate (Date)—The date the installation of the wellhead was completed.

inservicedate (Date)—The date the wellhead was put into production.

name (Text[20])—The textual name used within the organization to identify the well.


ownedby (Short Integer)—The name of the organization with ownership of the wellhead. In





maintenance of the wellhead. In most instances, this will be the name of your organization.


mopin (Double[16,5])—The maximum operating pressure allowed to enter the wellhead.

mopout (Double[16,5])—The maximum operating pressure allowed to exit the wellhead. sopin (Double[16,5])—The standard operating pressure allowed to enter the wellhead.

sopout (Double[16,5])—The standard operating pressure allowed to exit the wellhead.

PRESSURERATING (Double[16,4])—The manufacturer’s pressure rating for the wellhead.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the wellhead.


materialclass (Text[20])—The American Petroleum Institute classification of the material used to

construct the wellhead.

Coded Value Domain: Pipeline_Wellhead_Material_Class

nominaldiameter (Double[16,5])—The nominal edge-to-edge measured length of a straight line

through the center of the wellhead orifice.

Coded Value Domain: Pipeline_Wellhead_Diameter

diameterunits (Short Integer)—The unit of measure used to define the nominal diameter and

wall thickness of the wellhead orifice.

Coded Value Domain: Units_For_Diameter

wallthickness (Double[10,6])—The manufacturer’s defined width of the pipe wall.

Range Domain: Pipeline_Pipe_WallThickness_Steel

connectiontype (Text[30])—The type of connection between the wellhead and the pipe system.

Coded Value Domain: Pipeline_Wellhead_Connection_Type

outletvalvetype (Text[30])—The type of outlet valve used in the wellhead construction.

pressureratingunits (Short Integer)—The unit of measure used to define the pressure rating.

Coded Value Domain: Pipeline_Units_For_Pressure




geodatabase.




populated.



populated.



populated.

workorderid (Text[38])—The work order management system value used to identify the task number under which the work order was issued to construct the wellhead. projectnumber (Text[38])—The work order management system value used to identify the project number under which the work order was issued to construct the wellhead. assetunitcode (Text[38])—The foreign key value used to link this record to the asset’s corresponding record in the asset management system.

fromdate (Date)—The date the wellhead became active on the route. This attribute is only used

by organizations wanting to maintain the Wellhead features as event records with the ArcGIS

Pipeline Referencing tools. This value is automatically generated and populated by the ArcGIS


todate (Date)—The date the wellhead was retired from the route. This attribute is only used by

organizations wanting to maintain the Wellhead features as event records with the ArcGIS



engrouteid (Text[38])—The unique ID of the engineering network route where the wellhead is

located. This value is automatically generated and populated by the ArcGIS Pipeline Referencing

tools.




wanting to maintain the Wellhead features as event records with the ArcGIS Pipeline

Referencing tools.

locationerror(Text[100])—The resultant message from the process of defining the wellhead’s

location on a route. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.

engm (Double)—The measure location along the engineering network route where the wellhead

is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.




Referencing tools.




Referencing tools.





This attribute is only used by organizations wanting to maintain the Wellhead features as event


Referencing tools.



maintain the Wellhead features as event records with the ArcGIS Pipeline Referencing tools. The



maintain the Wellhead features as event records with the ArcGIS Pipeline Referencing tools. The



wellhead is located.



wellhead is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the wellhead is located.


Wellhead Migration Table UPDM 2016 to UPDM 2019:


PTownBorderStation


assettype Asset type WELLHEADTYPE


creationdate Creation Date DATECREATED




regulatorytype Regulatory Type N/A




name Well Name WELLNAME

ownedby Owner N/A



materialclass Material Class MATERIALCLASS

diameter Diameter NOMINALDIAMETER

diameterunits Diameter Units DIAMETERUNITS

wallthickness Wall Thickness WALLTHICKNESS

connectiontype Connection Type CONNECTIONTYPE

outletvalvetype Outlet Valve Type OUTLETVALVETYPE

mopin MOP IN N/A


mopout MOP OUT N/A

sopin SOP IN N/A

sopout SOPOUT N/A

pressurerating Pressure Rating PRESSURERATING

pressureratingunits Pressure Rating Units PRESSURERATINGUNITS

manufacturer Manufacturer MANUFACTURER


gpsx GPS X N/A

gpsy GPS Y N/A

gpsz GPSZ N/A







Name

ENGROUTENAME




Name

CONTINROUTENAME






Pigging Structure

The point derived feature layer PiggingStructure describes the facilities that allow for the

insertion or extraction of a pig sensor unit from the gas or fluid system. PiggingStructure

represents both the launcher and receiver aspects of the pig structure.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a pigging

structure whose type is not

known. 7 241 Launcher A launcher is the pigging

structure where the pigging

device is inserted. into the

pipe system.

7 242 Receiver A receiver is the pigging

structure where the pigging

device is extracted. from the

pipe system.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:








creator (Text[50])—The name of the system user who originally created the pig structure record

in the geodatabase. This value is automatically populated by the Editor Tracking.

creationdate (Date)—The date and time the pig structure record was originally created in the


lastupdate (Date)—The date and time the pig structure record was last modified in the



pig structure record in the geodatabase. This value is automatically populated by the Editor

Tracking.

regulatorytype (Short Integer)—The value indicating whether regulations require the pigging

structure to be considered a participant in the Transmission or Gathering portion of the pipe

system. The default value is Gathering.


installdate (Date)—The date the installation of the pigging structure was completed.

inservicedate (Date)—The date the pigging structure was put into production.


name (Text[20])—The textual name used within the organization to identify the pigging

structure.

ownedby (Short Integer)—The name of the organization with ownership of the wellhead. In





maintenance of the wellhead. In most instances, this will be the name of your organization.


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the pigging

structure.


pipediameter (Short Integer)—The cord length through the centroid of the pig structure barrel.

pipegrade (Text[15])—The classification of the characteristics of the material used for the pig

structure barrel.

Coded Value Domain: Pipeline _ASTM_Transmission_Pipe_Material

pipewallthickness (Double)—The manufacturer’s defined width of the barrel pipe wall.

Coded Value Domain: Pipeline _Pipe_Wall_thickness

manufacturer (Text[50])—The name of the company responsible for the creation of the pig

structure.

PIPEMATERIAL (Text[20])—The generic classification of the type of material used for the pig

structure.

STRUCTURElength (Double)—The measured length of the pig structure.

lengthunits (Short Integer)—The unit of measure for the structure length of the pigging

structure.

Coded Value Domain: Units_For_Length

comments (Text[255])—Additional comments about the pig structure.



geodatabase.




populated.




populated.



populated.

eventid (Text[38])—The unique ID for each pigging structure record. This attribute is only used

by organizations wanting to maintain the Pigging Structure features as event records with the

ArcGIS Pipeline Referencing tools. This value is automatically generated and populated by the


fromdate (Date)—The date the pigging structure became active on the route. This attribute is

only used by organizations wanting to maintain the Pigging Structure features as event records

with the ArcGIS Pipeline Referencing tools. This value is automatically generated and populated

by the ArcGIS Pipeline Referencing tools.

todate (Date)—The date the pigging structure was retired from the route. This attribute is only

used by organizations wanting to maintain the Pigging Structure features as event records with

the ArcGIS Pipeline Referencing tools. The value is automatically generated and populated by


engrouteid (Text[38])—The unique ID of the engineering network route where the beginning of

the point event is located. This attribute is only used by organizations wanting to maintain the

Pigging Structure features as event records with the ArcGIS Pipeline Referencing tools. The value

is automatically generated and populated by the ArcGIS Pipeline Referencing tools.



wanting to maintain the Pigging Structure features as event records with the ArcGIS Pipeline

Referencing tools.

engm (Double)—The measure location along the engineering network ROUTEID specified route

where the beginning of the point event is located. This attribute is only used by organizations


Referencing tools. The value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.

engrouteid (Text[38])—The unique ID of the engineering network route where the completion of

the point event is located. This attribute is only used by organizations wanting to maintain the

Pigging Structure features as event records with the ArcGIS Pipeline Referencing tools. The value


is automatically generated and populated by the ArcGIS Pipeline Referencing tools. engrouteid is

not required if modeling in ArcGIS Pipeline Referencing (APR) as continuous networks.

engm (Double)—The measure location along the engrouteid or ENGTOROUTEID specified route

where the completion of the point event is located. This attribute is only used by organizations



Referencing tools.




Referencing tools.




Referencing tools.

continm (Double[16,5])—The continuous network measure along the derived route ID. This

value is automatically created and maintained by the ArcGIS Pipeline Referencing tools. This

attribute is only used by organizations wanting to maintain the Pigging Structure features as

event records with the ArcGIS Pipeline Referencing tools.



This attribute is only used by organizations wanting to maintain the Pigging Structure features as





maintain the Pigging Structure features as event records with the ArcGIS Pipeline Referencing



maintain the Pigging Structure features as event records with the ArcGIS Pipeline Referencing







location on a route. This attribute is only used by organizations wanting to maintain the Pigging

Structure features as event records with the ArcGIS Pipeline Referencing tools. The value is



pigging structure is located.



isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the



Pigging Structure Migration Table UPDM 2016 to UPDM 2019:


P_PigStructure













name Name N/A

ownedby Owner N/A



pipediameter Barrel Diameter BARRELDIAMETER


pipegrade Barrel Grade BARRELGRADE

pipewallthickness Barrel Wall Thickness BARRELWALLTHICKNESS


pipematerial Material MATERIAL


structurelength Structure Length STRUCTURElength

lengthunits Length Units N/A

comments Comments REMARKS



gpsx GPS X N/A

gpsy GPS Y N/A

gpsz GPSZ N/A















Fitting Assembly

The point derived feature layer FittingAssembly describes the facility within a pipeline that

contains many fittings and devices within a small geographic area.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a fitting

assembly whose type is not

known. 8 281 Service Tap The location where a service

pipe meets the main line.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:








CREATIONUSER (Text[50])—The name of the system user who originally created the object


DATECREATED (Date)—The date and time the object record was originally created in the


DATEMODIFIED (Date)—The date and time the object record was last modified in the


LASTUSER (Text[50])—The name of the system user responsible for the last modification to the


globalid (Global ID)—The systemwide unique identifier.

regulatorytype (Short Integer)—The value indicating whether the EFV is considered a participant

in the Distribution, Transmission, or Gathering portion of the pipe system. The default value is

Transmission.


installdate (Date)—The date the installation of the fitting assembly was completed.

inservicedate (Date)—The date the fitting assembly was put into production.


name (Text[20])—The textual name used within the organization to identify the facility.

locationdescription (Text[255])—The textual description of the location of the fitting assembly.


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the fitting

assembly.




geodatabase.




populated.



populated.



populated.


organizations wanting to maintain the Fitting Assembly features as event records with the












located. This attribute is only used by organizations wanting to maintain the Fitting Assembly






wanting to maintain the Fitting Assembly features as event records with the ArcGIS Pipeline

Referencing tools.


location on a route. This attribute is only used by organizations wanting to maintain the Fitting

Assembly features as event records with the ArcGIS Pipeline Referencing tools. The value is



is located. This attribute is only used by organizations wanting to maintain the Fitting Assembly






Referencing tools.




Referencing tools.





This attribute is only used by organizations wanting to maintain the Fitting Assembly features as





maintain the Fitting Assembly features as event records with the ArcGIS Pipeline Referencing



maintain the Fitting Assembly features as event records with the ArcGIS Pipeline Referencing




fitting assembly is located.



isolationsubnetworkname(Text[2000])—the name of the isolation tier subnetwork where the



Fitting Assembly Migration Table UPDM 2016 to UPDM 2019:

The UPDM 2016 model did not define Fitting Assembly as a separate feature class. This is a new feature layer for UPDM 2019.


Pump Station

The point derived feature layer Pump Station describes the facility within a pipeline that

pressurizes the fluid in the pipe system. Pump stations are typically used in long distance

transmission pipelines where additional pressurization is required to allow the fluid to continue

its transport through the pipeline.


Relationships:

-P_UPDMAssembly__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

0 0 Unknown An unknown is a pump station


9 12 Pump A generic pump station system.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:








creator (Text[50])—The name of the system user who originally created the object record in the


creationdate (Date)—The date and time the object record was originally created in the


lastupdate (Date)—The date and time the object record was last modified in the geodatabase.




globalid (Global ID)—The systemwide unique identifier.

regulatorytype (Short Integer)—The value indicating whether the EFV is considered a participant

in the Distribution, Transmission, or Gathering portion of the pipe system. The default value is

Transmission.


installdate (Date)—The date the installation of the pump station was completed.

inservicedate (Date)—The date the pump station was put into production.

name (Text[20])—The textual name used within the organization to identify the facility.


locationdescription (Text[255])—The textual description of the location of the pump station.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the pump station.



mopin (Double[16,5])—The maximum operating pressure allowed to enter the pump station.

mopout (Double[16,5])—The maximum operating pressure allowed to exit the pump station. sopin (Double[16,5])—The standard operating pressure allowed to enter the pump station.

sopout (Double[16,5])—The standard operating pressure allowed to exit the pump station.

totalpower (Double)—The power rating of the pump station. This is measured in horsepower,

which generally converts to watts as 1 hp = 746 watts.

numberofunits (Short Integer)—The number of pumps in the pump station facility.



geodatabase.




populated.



populated.



populated.


organizations wanting to maintain the Pump Station features as event records with the ArcGIS













located. This attribute is only used by organizations wanting to maintain the Pump Station





wanting to maintain the Pump Station features as event records with the ArcGIS Pipeline

Referencing tools.


location on a route. This attribute is only used by organizations wanting to maintain the Pump




is located. This attribute is only used by organizations wanting to maintain the Pump Station






Referencing tools.




Referencing tools.





This attribute is only used by organizations wanting to maintain the Pump Station features as






maintain the Pump Station features as event records with the ArcGIS Pipeline Referencing tools.



maintain the Pump Station features as event records with the ArcGIS Pipeline Referencing tools.



pump station is located.



isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the



Pump Station Migration Table UPDM 2016 to UPDM 2019:


P_PumpStation













globalid GlobalID globalid


totalpower Total Power HORSEPOWER

numberofunits Number of Units NUMBEROFUNITS

mopin MOP IN N/A

mopout MOP OUT N/A

sopin SOP IN N/A

sopout SOP OUT N/A

comments Comments N/A



gpsx GPS X N/A

gpsy GPS Y N/A

gpsz GPSZ N/A






Name

ENGROUTENAME










Lines Definition: The Line feature class models all pipe through which the commodity flows and all cathodic

protection wires through which the electricity flows. Each line segment should correspond to the length

of pipe or wire for which the pipe characteristics are consistent. Pipe segments should be split at each

isolating device, pressure changing device, and system delineation device.



• A line can connect to the following:

o Device—For example, a coated steel station pipe can connect to a regulator.

o Junction—For example, a Plastic PE pipe segment can connect to a plastic fusion.

• A line can be contained by the following:

o Assembly—For example, a bare steel riser can be contained in a meter setting.

o Structure edge—For example, a pipe casing can contain a gas line pipe segment.

o Structure boundary—For example, a processing facility can contain a coated steel

station pipe.

Line

PipeService

LineStation

PipeRectifier

CableBonding

LineTest Lead

Wire



This is the schema for the Line feature class.




associationtstatus Short Integer Required for Utility Network

isconnected Short Integer Required for Utility Network

fromdeviceterminal Short Integer Required for Utility Network

todeviceterminal Short Integer Required for Utility Network





globalid Global ID Required for Geodatabase

regulatorytype Short Integer

pinchable Short Integer Utility Network Attribute

piggable Short Integer

warningtape Short Integer

tracerwire Short Integer

seamtype Short Integer

longseamtype Short Integer

girthweldtype Short Integer

longitudinalseamorientation Double

pipesurfacearea Double(16,5) Utility Network Attribute

installdate Date

inservicedate Date

installationmethod Short Integer

assetid Text(64)

ownedby Short Integer

maintby Short Integer

lifecyclestatus Short Integer Utility Network Attribute

nominaldiameter Double(16,5)

operatingpressure Double(16,5)

maopdesign Double(16,5) Utility Network Attribute

maoptest Double(16,5) Utility Network Attribute


maoprecord Double(16,5) Utility Network Attribute

measuredlength Double(16,2)

lengthsource Short Integer


wallthickness2 Double(16,5)

outsidediameter Double(16,5)

barcode Text(16)


manufacturerlotno Long Integer

manufacturedate Date

manufacturecomponent Text(2)

material Text(2)

pipevolume Double(16,5) Utility Network Attribute

gauge Short Integer

depth Double(10,5)

criticalindicator Short Integer

notes Text(2000)

commodity Short Integer

actualinternaldiameter Double(16,5)

originalcoverdepth Double(16,5)

primarycoatingtype Text(30)

primarycoatingappdate Date

secondarycoatingtype Text(30)

secondarycoatingdate Date

tertiarycoatingtype Text(30)

tertiarycoatingdate Date

designclass Short Integer

pipetesttype Text(30)

spatialaccuracy Short Integer

covertype Text(20)

depthunits Short Integer




maopunits Short Integer


pipesurfaceareaunits Short Integer

pipevolumeunits Short Integer

smys Double(16,5)

percentsmys Double(16,5)

retireddate Date

stubbed Short Integer

pipetestdate Date

pipetestduration Double(16,5)

pipetestpressure Double(16,5)

designpressureentered Double(16,5)

designpressurestandard Double(16,5)

designpressureunits Short Integer

designfactor Double(16,5)

wirematerial Text(20)




legacyid Text(38)


eventid Text(38) ArcGIS Pipeline Referencing Attribute

fromdate Date ArcGIS Pipeline Referencing Attribute

todate Date ArcGIS Pipeline Referencing Attribute

engrouteid Text(38) ArcGIS Pipeline Referencing Attribute

engroutename Text(100) ArcGIS Pipeline Referencing Attribute

engfromm Double(16,5) ArcGIS Pipeline Referencing Attribute

engtorouteid Text(38) ArcGIS Pipeline Referencing Attribute

engtoroutename Text(100) ArcGIS Pipeline Referencing Attribute

engtom Double(16,5) ArcGIS Pipeline Referencing Attribute

continrouteid Text(38) ArcGIS Pipeline Referencing Attribute

continroutename Text(100) ArcGIS Pipeline Referencing Attribute

continfromm Double(16,5) ArcGIS Pipeline Referencing Attribute

contintom Double(16,5) ArcGIS Pipeline Referencing Attribute

fromrefmethod Short Integer ArcGIS Pipeline Referencing Attribute

fromreflocation Text(50) ArcGIS Pipeline Referencing Attribute

fromrefoffset Text(50) ArcGIS Pipeline Referencing Attribute


torefmethod Short Integer ArcGIS Pipeline Referencing Attribute

toreflocation Text(50) ArcGIS Pipeline Referencing Attribute

torefoffset Text(50) ArcGIS Pipeline Referencing Attribute

locationerror Text(100) ArcGIS Pipeline Referencing Attribute

bondedinsulated Short Integer

cptraceability Short Integer

cpoverride Short Integer

locationdescription Text(100)

cpsubnetworkname Text(2000) Required for Utility Network

systemsubnetworkname Text(2000) Required for Utility Network

pressuresubnetworkname Text(2000) Required for Utility Network

isolationsubnetworkname Text(2000) Required for Utility Network


Pipes

The polyline derived layer Pipes describes the linear containers that transport liquid or gas. This

feature class contains distribution, transmission, and gathering pipes. The attribute

RegulatoryType is used to identify the system per regulation (Distribution, Transmission,

Transmission Operated Distribution, Offshore Transmission, Gathering, or Offshore Gathering)

with which the pipe segment is associated. Pipes is intended to be used for storing the

representation of the physical pipe through all stages of its engineering life cycle (proposed,

active, inactive, retired, removed, and abandoned). The asset types are configured to match the

U.S. DOT annual reporting classifications of material type to simplify DOT compliance reporting.

GeometryType: PolyLine with z- and m-values enabled

Relationships:

-ServiceSum_Service

Asset Groups:

Asset Group

(Code)

Asset Group

(Description)

Description

0 Unknown A pipe segment whose position in the

gas system is not known.

2 Distribution

Pipe

A distribution line is the portion of the

pipe system that delivers gas from the

town border station to the service line.

3 Transmission

Pipe

A transmission line is the portion of the


gathering subsystem to the distribution.

4 Gathering Pipe A gathering line is the portion of the


well to the transmission system.


Asset Type:

Asset Type

(Subtype Code)

Asset Type

(Description)

Description

0 Unknown A pipe segment whose material

composition cannot be verified.

1 Bare Steel Steel pipe that is not coated with a hot

or cold applied wrapper.

2 Cast Iron Pipe made from iron with a carbon

content greater than 2%.

3 Coated Steel Steel pipe that is covered with a hot or

cold applied wrapper.

4 Composite Pipe that is constructed of two or more

dissimilar materials.

5 Copper Pipe made from the refined mineral

Copper (Cu).

6 Ductile Iron Pipe made from iron with a less brittle

type of graphite carbon.

7 Plastic ABS Plastic pipe made from Acrylonitrile-

Butadiene Styrene plastic.

8 Plastic Other Plastic pipe that is not made from ABS,

PE, or PVC.

9 Plastic PE Plastic pipe made from polyethylene

plastic.

10 Plastic PVC Plastic pipe made from polyvinyl

chloride plastic.

11 Reconditioned

Cast Iron

Cast iron pipe that has been

rehabilitated.

12 Wrought Iron Pipe made from iron with a carbon

content less than 2%.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:


assetgroup (Long Integer)—The geodatabase subtype field. The subtype field models the

engineering system type of the pipe segments.

assettype (Short Integer)—The value indicating the material type of the pipe segment.


which the line feature participates.


isconnected (Short Integer) – A Boolean true/false value indicating whether the pipe segment is

connected to a subnetwork controller device.

fromdeviceterminal (Short Integer) – If the first vertex of the line is connected to a device with a

terminal definition. This integer value will indicate which port id of the terminal the pipe

segment has been associated too.

todeviceterminal (Short Integer) - If the last vertex of the line is connected to a device with a



creationdate (Date)—The date and time the pipe record was originally created in the


creator (Text[255])—The name of the system user who originally created the pipe record in the


lastupdate (Date)—The date and time the pipe record was last modified in the geodatabase.



the pipe record in the geodatabase. This value is automatically populated by the Editor Tracking.



regulatorytype (Short Integer)—The value indicating the regulatory status of the pipe segment.

This is used by the Facility Reporting tools to differentiate between Distribution, Transmission,

Offshore Transmission, Gathering, and Offshore Gathering pipe.



pinchable (Short Integer)—The yes/no Boolean value indicating whether the pipe segment is

made of a material that can be pinched during emergency operations.


piggable (Short Integer)—The yes/no Boolean value indicating whether the pipe segment can be

pigged.


warningtape (Short Integer)—The yes/no Boolean value indicating whether a warning tape was

installed with the pipe segment.


tracerwire (Short Integer)—The yes/no Boolean value indicating whether a tracer wire was

installed with the pipe segment.


seamtype (Text[20])—The type of seam used during the manufacture of the pipe.

Coded Value Domain: Pipeline_Seam_Type

girdweldtype (Text[20])—The type of welding procedure and welding equipment used to weld

the pipe segments.

Coded Value Domain: Pipeline_Girth_Weld_Type

longitudinalseamorientation (Text[20])—The clock position of the weld along a pipe length of

the installed pipe if the pipe is not a seamless pipe. A clock position of 12:00 indicates the weld

seam is on top of the pipe, and a clock position of 6:00 indicates the weld seam is at the bottom

of the pipe.

Coded Value Domain: Pipeline_Seam_Orientation

pipesurfacearea (Double[16,5])—The exterior surface area of the pipe segment. This is a

network attribute in the utility network configuration.

pipesurfaceunits (Short Integer)—The unit of measure for measuring the PIPESURFACEAREA.

Coded Value Domain: Units_For_Surface_Area

installdate (Date)—The date the construction of the pipe was completed.

inservicedate (Date)—The date the pipe segment was put into production.

installationmethod (Text[20])—The construction process used to install the pipe segment.


Coded Value Domain: Pipeline_LineInstallMethod


ownedby (Short Integer)—The name of the organization with ownership of the pipe segment. In




maintenance of the pipe segment. In most instances, this will be the name of your organization.


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the pipe feature.


nominaldiameter (Double[16,5])—The generalized edge-to-edge measured length of a straight

line through the center of the pipe orifice.

Coded Value Domains are subtype specific.

diameterunits (Short Integer)—The unit of measure defining the nominal and outside diameters

of the pipe.


operatingpressure (Double[16,5])—The nominal pressure at which the pipe system operates.

pressureunits (Short Integer)—The unit of measure for defining the operating pressure.

Coded Value Domain: Units_For_Pressure

maopdesign (Double[16,5])—The maximum allowable operating pressure as defined during

design.

maoptest (Double[16,5])—The tested maximum allowable operating pressure during

installation.

maoprecord (Double[16,5])—The maximum allowable operating pressure under which the pipe

segment is currently operating.

maopunits (Short Integer)—The unit of measure for defining the maximum allowable operating

pressure.


measuredlength (Double[16,3])—The end-to-end distance of the pipe segment.


lengthsource (Text[25])—The source of the distance value used to define the pipe segment’s

length.

Coded Value Domain: Pipeline_Length_Source

lengthunits (Short Integer)—The unit of measure for defining the measured length.


smys (Double[16,5])—The manufacturer-determined Specified Minimum Yield Strength value.

percentsmys (Double[16,5])—The percentage of the SMYS value under which the pipe segment

pressure is operating.

barcode (Text[16])—The ASTM F2897-15 code read from the bar code on the pipe segment.

manufacturer (Text[2])—The organization that built the pipe segment.

Coded Value Domain: Pipeline_ASTM_Manufacturer

manufacturerlotno (Long Integer)—The manufacturer lot number from which the pipe segment

was created.

manufacturedate (Date)—The date the pipe segment was created by the manufacturer.

manufacturecomponent (Text[2])—The manufacturer-specified, industry standard specification

that was followed when the pipe segment was created. Subtype-specific coded value domains

are based on the ASTM F2897 bar code derived values.

material(Text[2])—A code (for example, x42) indicating yield strength and minimum tensile

strength of the steel used in the fabrication of the pipe segment. Subtype-specific coded value

domains are based on ASTM F2897 list of pipe grades.

wallthickness (Double[16,5])—The manufacturer’s defined width of the pipe wall. Subtype-

specific coded value domains.

outsidediameter (Double[16,5])—The outer edge-to-outer edge measured length of a straight

line through the center of the pipe orifice.

actualinternaldiameter (Double[16,5])—The manufacturer’s defined internal edge-to-edge

measurement of a straight line through the centroid of the pipe.

commodity (Short Integer)—The federal description for the type of fluid or gas being

transported by the pipe segment.


Coded Value Domain: Pipeline_CommodityType

designclass (Long Integer)—The U.S. DOT class location for which the pipe segment was

designed. Pipelines in the U.S. are designed for the expected DOT class of the area where the

pipe segment will be installed.

Coded Value Domain: Pipeline_LineDesignClass

pipevolume (Double[16,5])—The interior volume of the pipe segment.

pipevolumeunits (Short Integer)—The unit of measure for measuring the interior volume of the

pipe segment.

Coded Value Domain: Units_For_Volume

covertype (Text[20])—The type of surface above the buried pipe segment.

Coded Value Domain: Pipeline_SurfaceType

originalcoverdepth (Double[16,5])—The depth below the ground surface at which the pipe was

placed during original construction.

depthunits (Short Integer)—The unit of measure defining the original cover depth.

primarycoatingtype (Text[30])—The initial type of protective coating applied to the exterior of

the pipe segment.

Coded Value Domain: Pipeline_Line_Coating_Type

primarycoatingappdate (Date)—The date the initial type of protective coating was applied to

the pipe segment.

secondarycoatingtype (Text[30])—The secondary type of protective coating applied to the

exterior of the pipe segment.


secondarycoatingappdate (Date)—The date the secondary type of protective coating was

applied to the pipe segment.

tertiarycoatingtype (Text[30])—The third type of protective coating applied to the exterior of

the pipe segment.


tertiarycoatingappdate (Date)—The date the third type of protective coating was applied to the

pipe segment.


retireddate (Date)—The date the pipe segment was permanently removed from production.

criticalindicator (Short Integer)—The yes/no Boolean value indicating whether the pipe segment

is considered critical to the operation of the overall system.


stubbed (Short Integer)—The yes/no Boolean value indicating whether the pipe segment has

been stubbed.


pipetestdate (Date)—The date the newly installed pipe segment was pressure tested.

pipetestduration (Double[16,5])—The length of time the pipe segment was under pressure

during the test.

pipetestpressure (Double[16,5])—The internal force to which the pipe segment was exposed

during the pipe test.

pipetesttype (Text[30])—The method used to perform the pipe test.

Coded Value Domain: Pipeline_Line_Pipe_Test_Type

designpressureentered (Double[16,5])—The internal force under which the pipe segment is

designed to operate.

designpressurestandard (Double[16,5])—The average internal force under which the pipe

segment is designed to operate.

designpressureunits (Short Integer)—The unit of measure defining the internal force specified as

the design pressure.


designfactor (Double[16,5])—The margin of safety that was used during the design of the pipe

segment when determining the design class. DOT regulations 192.103, 192.105, 192.107, and

192.111 require the use of class location design factors for steel pipes.



geodatabase.

Coded Domain: Spatial Accuracy

assetunitcode (Text[20])—The foreign key value used to link this record to the utilities asset

management system information for this pipe segment.


workorderid (Text[38])—The work management system value used to identify the task number

under which the pipe segment was installed.

projectnumber (Text[38])—The work management system value used to identify the project

number under which a work order was generated to install the pipe segment.

legacyid (Text[38]) —A unique identifier used to relate this record to its predecessor record from



eventid (Text[38])—The unique ID for each pipe segment record. This attribute is only used by

organizations wanting to maintain the Pipes features as event records with the ArcGIS Pipeline

Referencing tools. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.

fromdate (Date)—The date the pipe segment became active on the route. This attribute is only

used by organizations wanting to maintain the Pipes features as event records with the ArcGIS



todate (Date)—The date the pipe segment was retired from the route. This attribute is only used

by organizations wanting to maintain the Pipes features as event records with the ArcGIS




the linear event is located. This attribute is only used by organizations wanting to maintain the

Pipes features as event records with the ArcGIS Pipeline Referencing tools. The value is

automatically generated and populated by the ArcGIS Pipeline Referencing tools. engrouteid is


engroutename (Text[100])—The user-defined name of the engineering network route where the

beginning of the linear event is located. This attribute is only used by organizations wanting to

maintain the Pipes features as event records with the ArcGIS Pipeline Referencing tools. The


engroutename is not required if modeling in ArcGIS Pipeline Referencing (APR) as continuous

networks.

ENGFROMM (Double)—The measure location along the engineering network engrouteid

specified route where the beginning of the linear event is located. This attribute is only used by

organizations wanting to maintain the Pipes features as event records with the ArcGIS Pipeline



Referencing tools. ENGFROMM is not required if modeling in ArcGIS Pipeline Referencing (APR)

as continuous networks.

engtorouteid (Text[38])—The unique ID of the engineering network route where the completion

of the linear event is located. This attribute is only used by organizations wanting to maintain

the Pipes features as event records with the ArcGIS Pipeline Referencing tools. The value is

automatically generated and populated by the ArcGIS Pipeline Referencing tools. engtorouteid is


engtoroutename (Text[100])—The user-defined name of the engineering network route where

the end of the linear event is located. This attribute is only used by organizations wanting to



engtoroutename is not required if modeling in ArcGIS Pipeline Referencing (APR) as continuous

networks.

engtom (Double)—The measure location along the engrouteid or engtorouteid specified route

where the completion of the linear event is located. This attribute is only used by organizations

wanting to maintain the Pipes features as event records with the ArcGIS Pipeline Referencing

tools. The value is automatically generated and populated by the ArcGIS Pipeline Referencing

tools. engtom is not required if modeling in ArcGIS Pipeline Referencing (APR) as continuous

networks.




tools.




tools.

continfrommeasure (Double)—The continuous network beginning measure along the derived

route ID. This value is automatically created and maintained by the ArcGIS Pipeline Referencing

tools. This attribute is only used by organizations wanting to maintain the Pipes features as


contintomeasure (Double)—The continuous network ending measure along the derived route

ID. This value is automatically created and maintained by the ArcGIS Pipeline Referencing tools.


This attribute is only used by organizations wanting to maintain the Pipes features as event

records with the ArcGIS Pipeline Referencing tools.

fromrefmethod (Short Integer)—The method of referencing the offset feature. This can be




Referencing tools.

fromreflocation (Text[50])—The location of the offsetting feature. This can be Coordinates,




fromrefoffset (Text[50])—The offset measure. This attribute is only used by organizations



torefmethod (Short Integer)—The method of referencing the offset feature. This can be




Referencing tools.

toreflocation (Text[50])—The location of the offsetting feature. This can be Coordinates,




torefoffset (Text[50])—The offset measure. This attribute is only used by organizations wanting

to maintain the Pipes features as event records with the ArcGIS Pipeline Referencing tools. The



location on a route. This attribute is only used by organizations wanting to maintain the Pipes



bondedinsulated (Short Integer) – Indicator of whether the pipe segment is Bonded or Insulated.

Coded Value Domain: Bonded_Insulated


cptraceability (Short Integer) – Indicator of whether the pipe segment participates in a cathodic

protection zone. A code value of “2” (not traceable) is a barrier for the subnetwork cathodic

protection zone. Coded Value Domain: CP_Traceability

cpoverride (Short Integer)- Override of the default cptraceability Indicator of whether the pipe

segment participates in a cathodic protection zone. Coded Value Domain: CP_Traceability

systemsubnetworkname (Text[2000])—The name of the system tier subnetwork where the pipe

segment is located.


pipe segment is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the pipe segment is located. cpsubnetworkname (Text[2000])—The name of the cathodic protection tier subnetwork where the pipe segment is located.


Pipes Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Pipes




isconnected Is Connected N/A

fromterminal From Terminal N/A

toterminal To Terminal N/A


creator Creator creator





pinchable Pinchable PINCHABLE

piggable Piggable PIGGABLE

warningtape Warning Tape WARNINGTAPE

tracerwire Tracer Wire TRACERWIRE

seamtype Seam Type SEAMTYPE

girthweldtype Gird Weld Type GIRTHWELDTYPE

longitudinalseamorientation Longitudinal Seam

Orientation

LONGITUDINALSEAMORIENTA

TION

pipesurfacearea Pipe Surface Area N/A




installationmethod Install Method INSTALLATIONMETHOD


ownedby Owner OWNER



nominaldiameter Nominal Diameter NOMINALDIAMETER

operatingpressure Operating Pressure OPERATINGPRESSURE

maopdesign MAOP Design MAOPDESIGN

maoptest MAOP Test MAOPTEST

maoprecord MAOP Record MAOPRECORD

measuredlength Measured Length MEASUREDlength

lengthsource Length Source lengthSOURCE


outsidediameter Outside Diameter OUTSIDEDIAMETER

barcode Barcode BARCODE


manufacturerlotno Manufacturer Lot No MANUFACTURERLOTNO

manufacturedate Manufacture Date MANUFACTUREDATE

manufacturecomponent Pipe Specification PIPESPECIFICATION

material Pipe Grade PIPEGRADE

pipevolume Pipe Volume N/A

commodity Commodity COMMODITY

actualinternaldiameter Actual Internal Diameter ACTUALINTERNALDIAMETER

covertype Cover Type N/A


originalcoverdepth Original Cover Depth N/A

depthunits Depth Units N/A

primarycoatingtype Primary Coating Type COATINGTYPE

primarycoatingappdate Primary Coating

Application Date

N/A

secondarycoatingtype Secondary Coating Type COATINGTYPE

secondarycoatingappdate Secondary Coating

Application Date

N/A

tertiarycoatingtype Tertiary Coating Type COATINGTYPE

tertiarycoatingappdate Tertiary Coating App

Date

N/A

smys SMYS SMYS

percent smys Percent SMYS PERCENTSMYS

retireddate Retired Date DATE_RETIRED

criticalindicator Critical Indicator CRITICALINDICATOR

stubbed Stubbed N/A

designclass Design Class DESIGNCLASS


pipetestdate Pipe Test Date PIPETESTDATE

pipetestduration Pipe Test Duration PIPETESTDURATION

pipetestpressure Pipe Test Pressure PIPETESTPRESSURE

pipetesttype Pipe Test Type PIPETESTTYPE

designpressureentered Design Pressure Entered DESIGNPRESSUREENTERED

designpressurestandard Design Pressure

Standard

DESIGNPRESSURESTANDARD

designpressureunits Design Pressure Units N/A


designfactor Design Factor DESIGNFACTOR

maopunits MAOP Unit of Measure MAOPUNITOFMEASURE



pressureunits Pressure Units DESIGNPRESSUREUNITOFMEA

SURE

pipesurfaceareaunits Pipe Surface Area Units N/A

pipevolumeunits Pipe Volume Units N/A










Name

ENGROUTENAME

engfromm Engineering From

Measure

ENGFROMM

engtorouteid Engineering To RouteID ENGTOROUTEID

engtoroutename Engineering To Route

Name

ENGTOROUTENAME

engtom Engineering To Measure ENGTOM




continfrommeasure Continuous From

Measure

CONTINFROMMEASURE

contintomeasure Continuous To Measure CONTINTOMEASURE

fromrefmethod From Reference Method FROMREFMETHOD

fromreflocation From Reference

Location

FROMREFLOCATION

fromrefoffset From Reference Offset FROMREFOFFSET

torefmethod To Reference Method TOREFMETHOD

toreflocation To Reference Location TOREFLOCATION

torefoffset To Reference Offset TOREFOFFSET


N/A ELECTRICSURVEYINDICATOR

N/A GASTRACEWEIGHT

N/A Pressure Zone ID PRESSURESYSTEM_GlobalID

N/A Isolation Zone ID EMERISOSYSTEM_GlobalID

N/A CP Zone ID CPSYSTEM_GlobalID


Service Line

The subtype feature layer Service Line describes the pipes that transport gas or liquid to the

customer. Service Line is intended to be used for storing the representation of the physical pipe

through all stages of its engineering life cycle (proposed, active, inactive, retired, and removed).

The asset types are configured to match the U.S. DOT annual reporting classifications of material

type to simplify DOT compliance reporting.


Relationships:

-ServiceSum_Service

Asset Groups:

Asset Group

(Code)

Asset Group

(Description)

Description



1 Service Line A service line is the portion of the pipe

system that connects a customer to the

distribution pipe.

6 Customer Pipe A customer pipe is the portion of the

pipe system that the gas organization

does not own or maintain.

7 Riser Pipe A riser is the vertical pipe where a pipe

system transitions from below ground

to above ground.


Asset Type:

Asset Type

(Subtype Code)

Asset Type

(Description)

Description







3 Coated Steel Steel pipe that has been covered with a

hot or cold applied wrapper.




Copper (Cu).






PE, or PVC.


plastic.


chloride plastic.

11 Reconditioned

Cast Iron


rehabilitated.



Container: No

Attachments: Yes

Editor Tracking:







Attributes:



engineering system type of the pipe segments.

assettype (Short Integer)—The value indicating the material type of the pipe segment.




isconnected (Short Integer) – A Boolean true/false value indicating whether the pipe segment is

connected to a subnetwork controller device.




todeviceterminaL (Short Integer) - If the last vertex of the line is connected to a device with a



creationdate (Date)—The date and time the service line record was originally created in the


creator (Text[255])—The name of the system user who originally created the service line record


lastupdate (Date)—The date and time the service line record was last modified in the



the pipe record in the geodatabase. This value is automatically populated by the Editor Tracking.




regulatorytype (Short Integer)—The value indicating the regulatory status of the service line

segment. This is used by the Facility Reporting tools to differentiate between Distribution,

Transmission, Offshore Transmission, Gathering, and Offshore Gathering pipe.


pinchable (Short Integer)—The yes/no Boolean value indicating whether the service line

segment is made of a material that can be pinched during emergency operations.


piggable (Short Integer)—The yes/no Boolean value indicating whether the service line segment

can be pigged.


warningtape (Short Integer)—The yes/no Boolean value indicating whether a warning tape was

installed with the service line segment.


tracerwire (Short Integer)—The yes/no Boolean value indicating whether a tracer wire was

installed with the service line segment.


pipesurfacearea (Double[16,5])—The exterior surface area of the service line segment. This is a


installdate (Date)—The date the construction of the service line was completed.

inservicedate (Date)—The date the service line segment was put into production.

installationmethod (Text[20])—The construction process used to install the service line segment.

Coded Value Domain: Pipeline_Line_Install_Method

assetid (Text[64])— A layer-specific textual unique identifier.

ownedby (Short Integer)—The organization responsible for the service line segment.


maintby (Short Integer) – The organization responsible for the maintenance and operation of

the service line segment


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the service line

feature.




line through the center of the service line orifice.


operatingpressure (Double[16,5])—The nominal pressure at which the service line system

operates.


design.


installation.

maoprecord (Double[16,5])—The maximum allowable operating pressure under which the

service line segment is currently operating.


lengthsource (Text[25])—The source of the distance value used to define the length of the

service line segment.


wallthickness (Double[16,5])—The manufacturer-defined width of the pipe wall. Subtype specific

coded value domains are based on.

barcode (Text[16])—The ASTM F2897-15 code read from the bar code on the service line

segment.

manufacturer (Text[2])—The organization that built the service line segment.


manufacturerlotno (Long Integer)—The manufacturer lot number from which the service line

segment was created.

manufacturedate (Date)—The date the service line segment was created by the manufacturer.


that was followed when the pipe segment was created. Subtype-specific coded value domains

are based on the ASTM F2897 bar code derived values.


material (Text[2])—A code (for example, x42) indicating yield strength and minimum tensile

strength of the steel used in the fabrication of the service line segment. Subtype-specific coded

value domains are based on the ASTM F2897 list of pipe grades.

pipevolume (Double[16,5])—The interior volume of the service line segment.


transported by the service line segment.

Coded Domain: Pipeline_Commodity_Type

actualinternaldiameter (Double[16,5])—The manufacturer-defined internal edge-to-edge


covertype (Text[20])—The type of surface above the buried service line segment.

Coded Value Domain: Pipeline_Surface_Type

originalcoverdepth (Double[16,5])—The depth below the ground surface at which the service

line was placed during original construction.

depthunits (Short Integer)—The unit of measure defining the original cover depth.

Coded Value Domain: Units_For_Depth


the service line segment.





exterior of the service line segment.



applied to the service line segment.







retireddate (Date)—The date the service line segment was permanently removed from

production.

stubbed (Short Integer)—The yes/no Boolean value indicating whether the service line segment

has been stubbed.




geodatabase.


pipetestdate (Date)—The date the newly installed service line segment was pressure tested.

pipetestduration (Double[16,5])—The length of time the service line segment was under

pressure during the test.

pipetestpressure (Double[16,5])—The internal force to which the service line segment was

exposed during the pipe test.

pipetesttype (Text[30])—The method used to perform the service line test.


designpressureentered (Double[16,5])—The internal force under which the service line segment

is designed to operate.

designpressurestandard (Double[16,5])—The average internal force under which the service line

segment is designed to operate.




designfactor (Double[16,5])—The margin of safety that was used during the design of the service

line segment when determining the design class. DOT regulations 192.103, 192.105, 192.107,

and 192.111 require the use of class location design factors for steel pipes.


under which the service line segment was installed.



number under which a work order was generated to install the service line segment.





management system information for this service line segment.



lengthunits (Short Integer)—The unit of measure defining the measured length.

Coded Valve Domain: Units_For_Length

maopunits (Short Integer)—The unit of measure defining the maximum allowable operating

pressure.


pressureunits (Short Integer)—The unit of measure defining the operating pressure.



of the service line.





servicesummaryid (GUID)—The foreign key unique value used to relate the service line segment

to the SERVICESSUMMARY feature class record with which it participates.










service line segment is located.


service line segment is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the service line segment is located.


Service line Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Services













pinchable Pinchable PINCHABLE

warningtape Warning Tape WARNINGTAPE

tracerwire Tracer Wire TRACERWIRE

pipesurfacearea Pipe Surface Area N/A



installationmethod Install Method INSTALLATIONMETHOD


ownedby Owner N/A




nominaldiameter Nominal Diameter DIAMETER

operatingpressure Operating Pressure OPERATINGPRESSURE

maopdesign MAOP Design N/A

maoptest MAOP Test N/A

maoprecord MAOP Record N/A






manufacturerlotno Manufacturer Lot

No

MANUFACTURERLOTNO


materialcomponent Pipe Specification PIPESPECIFICATION

material Pipe Grade PIPEGRADE

pipevolume Pipe Volume N/A

commodity Commodity COMMODITY

actualinternaldiameter Actual Internal

Diameter

ACTUALINTERNALDIAMETER

covertype Cover Type COVERTYPE

originalcoverdepth Original Cover

Depth

ORIGINALCOVERDEPTH


primarycoatingtype Primary Coating

Type

COATINGTYPE


primarycoatingappdate Primary Coating App

Date

N/A

secondarycoatingtype Secondary Coating

Type

N/A

secondarycoatingappdate Secondary Coating

App Date

N/A

tertiarycoatingtype Tertiary Coating

Type

N/A

tertiarycoatingappdate Tertiary Coating App

Date

N/A

retireddate Date Retired DATE_RETIRED

maopunits MAOP Units N/A


pressureunits Pressure Units DESIGNPRESSUREUNITOFMEASURE

pipevolumeunits Pipe Volume Units N/A

piggable Piggable N/A

stubbed Stubbed STUBBED

pipetestdate Pipe Test Date PIPETESTDATE

pipetestduration Pipe Test Duration PIPETESTDURATION

pipetestpressure Pipe Test Pressure PIPETESTPRESSURE

pipetesttype Pipe Test Type PIPETESTTYPE

designpressureentered Design Pressure

Entered

DESIGNPRESSUREENTERED

designpressurestandard Design Pressure

Standard

DESIGNPRESSURESTANDARD

designpressureunits Design Pressure

Units

DESIGNPRESSUREUNITOFMEASURE

designfactor Design Factor N/A



pipesurfaceareaunits Pipe Surface Area

Units

N/A






servicesummaryid Service Summary ID SERVICESUMMARY_GlobalID

N/A Electric Survey

Indicator

ELECTRICSURVEYINDICATOR

N/A Gas Trace Weight GASTRACEWEIGHT

N/A Pressure Zone ID PRESSURESYSTEM_GlobalID

N/A Isolation Zone ID EMERISOSYSTEM_GlobalID

N/A CP Zone ID CPSYSTEM_GlobalID


Station Pipe

The subtype feature layer Station Pipe describes the pipes in a gas facility that transport gas or

liquid. Station Pipe is intended to be used for storing the representation of the physical pipe

through all stages of its engineering life cycle (proposed, active, inactive, retired, and removed).

The asset types are configured to match the U.S. DOT annual reporting classifications of material

type to simplify DOT compliance reporting.


Relationships:

-ServiceSum_Service

Asset Groups:

Asset Group

(Code)

Asset Group

(Description)

Description



5 Station Pipe A station pipe is the portion of the pipe

system within a gas facility.

Asset Type:

Asset Type

(Subtype Code)

Asset Type

(Description)

Description







3 Coated Steel Steel pipe that has been covered with a

hot or cold applied wrapper.




Copper (Cu).







PE, or PVC.


plastic.


chloride plastic.

11 Reconditioned

Cast Iron


rehabilitated.



Container: No

Attachments: Yes

Editor Tracking:







Attributes:



engineering system type of the station pipe segments.

assettype (Short Integer)—The value indicating the material type of the station pipe segment.




isconnected (Short Integer) – A Boolean true/false value indicating whether the station pipe

segment is connected to a subnetwork controller device.


terminal definition. This integer value will indicate which port id of the terminal the station pipe



terminal definition. This integer value will indicate which port id of the terminal the station pipe


creationdate (Date)—The date and time the station pipe record was originally created in the


creator (Text[255])—The name of the system user who originally created the station pipe record


lastupdate (Date)—The date and time the station pipe record was last modified in the



the station pipe record in the geodatabase. This value is automatically populated by the Editor

Tracking.




regulatorytype (Short Integer)— The value indicating the regulatory status of the station pipe




pinchable (Short Integer)—The yes/no Boolean value indicating whether the station pipe

segment is made of a material that can be pinched during emergency operations.


pipesurfacearea (Double[16,5])—The exterior surface area of the station pipe segment. This is a


installdate (Date)—The date the construction of the station pipe was completed.

inservicedate (Date)—The date the station pipe segment was put into production.

installationmethod (Text[20])—The construction process used to install the station pipe

segment.

Coded Value Domain: Pipeline_Line_Install_Method


ownedby (Short Integer)—The name of the organization with ownership of the station pipe

segment. In most instances, this will be the name of your organization.



maintenance of the station pipe segment. In most instances, this will be the name of your

organization.


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the station pipe

feature.



line through the center of the station pipe orifice.


operatingpressure (Double[16,5])—The nominal pressure at which the station pipe system

operates.


pressureunits (Short Integer)—The unit of measure defining the operating pressure.



design.


installation.


service line segment is currently operating.



station pipe segment.


wallthickness (Double[16,5])—The manufacturer-defined width of the pipe wall. Subtype-

specific coded value domains.

barcode (Text[16])—The ASTM F2897-15 code read from the bar code on the station pipe

segment.

manufacturer (Text[2])—The organization that built the station pipe segment.


manufacturerlotno (Long Integer)—The manufacturer lot number from which the station pipe

segment was created.

manufacturedate (Date)—The date the station pipe segment was created by the manufacturer.


that was followed when the station pipe segment was created. Subtype-specific coded value

domains are based on the ASTM F2897 bar code derived values.

material (Text[2])—A code (for example, x42) indicating yield strength and minimum tensile

strength of the steel used in the fabrication of the station pipe segment. Subtype-specific coded

value domains are based on the ASTM F2897 list of pipe grades.

pipevolume (Double[16,5])—The interior volume of the station pipe segment.



transported by the station pipe segment.

Coded Domain: Pipeline_CommodityType

actualinternaldiameter (Double[16,5])—The manufacturer-defined internal edge-to-edge



the station pipe segment.





exterior of the station pipe segment.



applied to the station pipe segment.






retireddate(Date)—The date the station pipe segment was permanently removed from

production.



geodatabase.


pipetestdate (Date)—The date the newly installed station pipe segment was pressure tested.

pipetestduration (Double[16,5])—The length of time the station pipe segment was under

pressure during the test.


pipetestpressure (Double[16,5])—The internal force to which the station pipe segment was

exposed during the pipe test.

pipetesttype (Text[30])—The method used to perform the station pipe test.


designpressureentered (Double[16,5])—The internal force under which the station pipe segment

is designed to operate.

designpressurestandard (Double[16,5])—The average internal force under which the station

pipe segment is designed to operate.










pressure.



of the station pipe.




designfactor (Double[16,5])—The margin of safety that was used during the design of the station

pipe segment when determining the design class. DOT regulations 192.103, 192.105, 192.107,

and 192.111 require the use of class location design factors for steel pipes.


management system information for this station pipe segment.



under which the station pipe segment was installed.


number under which a work order was generated to install the station pipe segment.




servicesummaryid (GUID)—The foreign key unique value used to relate the station pipe segment

to the SERVICESSUMMARY feature class record with which it participates.









station pipe segment is located.


station pipe segment is located.

isolationsubnetworkname(Text[2000])—The name of the isolation tier subnetwork where the station pipe segment is located. cpsubnetworkname (Text[2000])—The name of the cathodic protection tier subnetwork where the station pipe segment is located.


Station Pipe Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Station Pipe as a separate feature class. This is a new feature layer as of UPDM 2018.


Bonding Line

The subtype feature layer Bonding Line describes the wire that is used to continue the electrical

connection in a cathodic protection system. Bonding Lines are used to span nonconductive

assets such as plastic pipe segments.


Relationships: None

Asset Groups:

Asset Group

(Subtype Code)

Asset Group

(Description)

Description

0 Unknown A wire whose type is unknown.

50 Bonding Line A wire that connects conductive pipe

system assets while spanning

nonconductive pipe system assets.

Asset Type:

Asset Type

(Code)

Asset Type

(Description)

Description

0 Unknown A bond wire whose type is not known.

961 Wire A generic bond wire that connects

conductive pipe system assets while

spanning nonconductive pipe system

assets

962 Strap A generic bonding strap connects two

conductive pipe system assets.

Container: No

Attachments: Yes

Editor Tracking:


Attributes:


assetgroup (Long Integer)—The geodatabase subtype field. The subtype field designates the

type as a bond wire.

assettype (Short Integer)—The value indicating the type of the bond wire segment.




isconnected (Short Integer) – A Boolean true/false value indicating whether the bond wire



terminal definition. This integer value will indicate which port id of the terminal the bond wire

has been associated too.




creationdate (Date)—The date and time the bond wire record was originally created in the


creator (Text[255])—The name of the system user who originally created the bond wire record


lastupdate (Date)—The date and time the bond wire record was last modified in the



the bond wire record in the geodatabase. This value is automatically populated by the Editor

Tracking.




regulatorytype (Short Integer)—The value indicating the regulatory status of the bond wire




installdate (Date)—The date the construction of the bond wire was completed.

inservicedate (Date)—The date the bond wire was put into production.


lengthsource (Text[25])—The source of the distance value used to define the length of the bond

wire segment.



lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the bond wire

feature.




wirematerial (Text[20])—The material used in the construction of the bond wire.

color (Text[15])—The color of the bond wire.

Coded Value Domain: CPColorCode

depth (Double[10,5])—The vertical distance below the surface to the location of the bond wire.

depthunits (Short Integer)—The unit of measure for DEPTH.


wiresize (Short)—The size of the wire.

gauge (Short)—The diameter size of the wire.



geodatabase.




management system information for this bond wire segment.


under which the bond wire segment was installed.


number under which a work order was generated to install the bond wire segment.




eventid (Text[38])—The unique ID for each bond wire record. This attribute is only used by

organizations wanting to maintain the Bond Wire features as event records with the ArcGIS



fromdate (Date)—The date the bond wire became active on the route. This attribute is only used

by organizations wanting to maintain the Bond Wire features as event records with the ArcGIS



todate (Date)—The date the bond wire was retired from the route. This attribute is only used by






Bond Wire features as event records with the ArcGIS Pipeline Referencing tools. The value is





maintain the Bond Wire features as event records with the ArcGIS Pipeline Referencing tools.

The value is automatically generated and populated by the ArcGIS Pipeline Referencing tools.


networks.


engfromm (Double)—The measure location along the engineering network engrouteid specified

route where the beginning of the linear event is located. This attribute is only used by



Pipeline Referencing tools. ENGFROMM is not required if modeling in ArcGIS Pipeline

Referencing (APR) as continuous networks.



the Bond Wire features as event records with the ArcGIS Pipeline Referencing tools. The value is

automatically generated and populated by the ArcGIS Pipeline Referencing tools. engtorouteid is







networks.

engtom (Double)—The measure location along the engrouteid or ENGTOROUTEID specified

route where the completion of the linear event is located. This attribute is only used by



Pipeline Referencing tools. engtom is not required if modeling in ArcGIS Pipeline Referencing

(APR) as continuous networks.



wanting to maintain the Bond Wire features as event records with the ArcGIS Pipeline

Referencing tools.




Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the Bond Wire features as





This attribute is only used by organizations wanting to maintain the Bond Wire features as event






Referencing tools.












Referencing tools.






to maintain the Bond Wire features as event records with the ArcGIS Pipeline Referencing tools.



location on a route. This attribute is only used by organizations wanting to maintain the Bond

Wire features as event records with the ArcGIS Pipeline Referencing tools. The value is


bondedinsulated (Short Integer) – Indicator of whether the bond wire is Bonded or Insulated.



cptraceability (Short Integer) – Indicator of whether the bond wire participates in a cathodic



cpoverride (Short Integer)- Override of the default cptraceability Indicator of whether the bond

wire participates in a cathodic protection zone. Coded Value Domain: CP_Traceability

cpsubnetworkname (Text[2000])—The name of the cathodic protection tier subnetwork where

the bond wire segment is located.


Bond Wire Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016










inservicedate Inservice Date INSERVICEDATE

assetid FacilityID FACILITYID





wirematerial Material MATERIAL

color Color COLOR

depth Depth DEPTH


wiresize Wire size WIRESIZE






workorderid Work OrderID WORKORDERID






engroutename Engineering RouteName ENGROUTENAME

engfromm Engineering From Measure ENGFROMM

engtorouteid Engineering to RouteID ENGTOROUTEID

engtoroutename Engineering to RouteName ENGTOROUTENAME

engtom Engineering to Measure ENGTOM


continroutename Continuous RouteName CONTINROUTENAME

continfromm Continuous From Measure CONTINFROMM

contintom Continuous To Measure CONTINTOM



fromreflocation From Reference Location FROMREFLOCATION







bondedinsulated Bonded insulated N/A

cptraceability cp traceability N/A

cpoverride cp override N/A

N/A CPTRACEWEIGHT


Test Lead Wire

The subtype feature layer Test Lead Wire describes the wire that is used to connect the test lead

device to the cathodic protection system..


Relationships: None

Asset Groups:

Asset Group

(Subtype Code)

Asset Group

(Description)

Description

0 Unknown A wire whose type is unknown.

51 Test Lead Wire A wire that connects test point devices

to the cathodic protection system.

Asset Type:

Asset Type

(Code)

Asset Type

(Description)

Description

0 Unknown A test lead wire whose color is not

known.

901 Aqua Test lead wire coating color of aqua.

902 Blue Test lead wire coating color of blue.

903 Forest Test lead wire coating color of forest.

904 Green Test lead wire coating color of green.

905 Lavender Test lead wire coating color of lavender.

906 Orange Test lead wire coating color of orange.

907 Pink Test lead wire coating color of pink.

908 Red Test lead wire coating color of red.

909 Yellow Test lead wire coating color of yellow.

910 Purple Test lead wire coating color of purple.


Container: No

Attachments: Yes

Editor Tracking:







Attributes:



type as a bond wire.

assettype (Short Integer)—The value indicating the type of the bond wire segment.




isconnected (Short Integer) – A Boolean true/false value indicating whether the bond wire








creationdate (Date)—The date and time the bond wire record was originally created in the


creator (Text[255])—The name of the system user who originally created the bond wire record


lastupdate (Date)—The date and time the bond wire record was last modified in the



the bond wire record in the geodatabase. This value is automatically populated by the Editor

Tracking.




regulatorytype (Short Integer)—The value indicating the regulatory status of the bond wire




installdate (Date)—The date the construction of the bond wire was completed.

inservicedate (Date)—The date the bond wire was put into production.


lengthsource (Text[25])—The source of the distance value used to define the length of the test

lead wire segment.



lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the test lead wire

feature.




wirematerial (Text[20])—The material used in the construction of the test lead wire.

depth (Double[10,5])—The vertical distance below the surface to the location of the test lead

wire.

depthunits (Short Integer)—The unit of measure for depth.


wiresize (Short)—The size of the wire.

gauge (Short)—The diameter size of the wire.



geodatabase.




management system information for this test lead wire segment.


under which the test lead wire segment was installed.


number under which a work order was generated to install the test lead wire segment.




eventid (Text[38])—The unique ID for each bond wire record. This attribute is only used by

organizations wanting to maintain the Test Lead Wire features as event records with the ArcGIS



fromdate (Date)—The date the bond wire became active on the route. This attribute is only used

by organizations wanting to maintain the Test Lead Wire features as event records with the



todate (Date)—The date the bond wire was retired from the route. This attribute is only used by






Test Lead Wire features as event records with the ArcGIS Pipeline Referencing tools. The value is





maintain the Test Lead Wire features as event records with the ArcGIS Pipeline Referencing


tools. engroutename is not required if modeling in ArcGIS Pipeline Referencing (APR) as

continuous networks.






Pipeline Referencing tools. engfromm is not required if modeling in ArcGIS Pipeline Referencing




the Test Lead Wire features as event records with the ArcGIS Pipeline Referencing tools. The


engtorouteid is not required if modeling in ArcGIS Pipeline Referencing (APR) as continuous

networks.





tools. engtoroutename is not required if modeling in ArcGIS Pipeline Referencing (APR) as




wanting to maintain the Test Lead Wire features as event records with the ArcGIS Pipeline


Referencing tools. engtom is not required if modeling in ArcGIS Pipeline Referencing (APR) as





Referencing tools.




Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the Test Lead Wire

features as event records with the ArcGIS Pipeline Referencing tools.




This attribute is only used by organizations wanting to maintain the Test Lead Wire features as
























to maintain the Test Lead Wire features as event records with the ArcGIS Pipeline Referencing



location on a route. This attribute is only used by organizations wanting to maintain the Test

Lead Wire features as event records with the ArcGIS Pipeline Referencing tools. The value is



bondedinsulated (Short Integer) – Indicator of whether the test lead wire is Bonded or Insulated.


cptraceability (Short Integer) – Indicator of whether the test lead wire participates in a cathodic



cpoverride (Short Integer)- Override of the default cptraceability Indicator of whether the test

lead wire participates in a cathodic protection zone. Coded Value Domain: CP_Traceability


the Test Lead Wire segment is located.


Test Lead Wire Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Test Lead Wire as a separate feature class. This is a new feature layer as of UPDM 2019.


Rectifier Cable

The subtype feature layer CP Rectifier Cable describes the cable that transmits electricity from

the rectifier to the cathodic protection system.


Relationships:

-ServiceSum_Service

Asset Groups:

Asset Group

(Subtype Code)

Asset Group

(Description)

Description

52 Unknown A cable whose type is unknown.

52 Rectifier Cable A cable that connects a rectifier to the

cathodic protection system.

Asset Type:

Asset Type

(Code)

Asset Type

(Description)

Description

0 Unknown A cable type is not known.

941 Rectifier Cable A generic rectifier cable that connects a

rectifier to the cathodic protection

system.

Container: No

Attachments: Yes


Editor Tracking:







Attributes:



type of the features.

assettype (Short Integer)—The value indicating the engineering system type of the rectifier

cable segment.




isconnected (Short Integer) – A Boolean true/false value indicating whether the rectifier cable



terminal definition. This integer value will indicate which port id of the terminal the rectifier

cable has been associated too.


terminal definition. This integer value will indicate which port id of the terminal the rectifier

cable has been associated too.

creationdate (Date)—The date and time the rectifier cable record was originally created in the


creator (Text[255])—The name of the system user who originally created the rectifier cable


lastupdate (Date)—The date and time the rectifier cable record was last modified in the



the rectifier cable record in the geodatabase. This value is automatically populated by the Editor

Tracking.




regulatorytype (Short Integer)—The value indicating the regulatory status of the rectifier cable




installdate (Date)—The date the construction of the rectifier cable was completed.

inservicedate (Date)—The date the rectifier cable was put into production.


measuredlength (Double[16,3])—The end-to-end distance of the rectifier cable.


rectifier cable.


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the rectifier cable

feature.




wirematerial (Text[20])—The metallic wire material used in the construction of the rectifier

cable.

color (Text[15])—The color of the rectifier cable.

Coded Value Domain: CPColorCode

depth (Double[10,5])—The vertical distance below the surface to the location of the rectifier

cable.

depthunits (Short Integer)—The unit of measure for DEPTH.


wiresize (Short)—The size of the rectifier cable.

gauge (Short)—The diameter size of the rectifier cable.



geodatabase.




management system information for this rectifier cable segment.


under which the rectifier cable segment was installed.


number under which a work order was generated to install the rectifier cable segment.




eventid (Text[38])—The unique ID for each rectifier cable record. This attribute is only used by

organizations wanting to maintain the Rectifier Cable features as event records with the ArcGIS



fromdate (Date)—The date the rectifier cable became active on the route. This attribute is only

used by organizations wanting to maintain the Rectifier Cable features as event records with the



todate (Date)—The date the rectifier cable was retired from the route. This attribute is only used

by organizations wanting to maintain the Rectifier Cable features as event records with the





Rectifier Cable features as event records with the ArcGIS Pipeline Referencing tools. The value is





maintain the Rectifier Cable features as event records with the ArcGIS Pipeline Referencing


tools. engroutename is not required if modeling in ArcGIS Pipeline Referencing (APR) as











the Rectifier Cable features as event records with the ArcGIS Pipeline Referencing tools. The



networks.





tools. engtoroutename is not required if modeling in ArcGIS Pipeline Referencing (APR) as


engtom (Double)—The measure location along the engrouteid or ENGTOROUTEID specified

route where the completion of the linear event is located. This attribute is only used by



Pipeline Referencing tools. engtom is not required if modeling in ArcGIS Pipeline Referencing




wanting to maintain the Rectifier Cable features as event records with the ArcGIS Pipeline

Referencing tools.




Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the Rectifier Cable





This attribute is only used by organizations wanting to maintain the Rectifier Cable features as


fromrefmethod (Short Integer)—The method of referencing the offset feature. It can be






















to maintain the Rectifier Cable features as event records with the ArcGIS Pipeline Referencing



location on a route. This attribute is only used by organizations wanting to maintain the Rectifier

Cable features as event records with the ArcGIS Pipeline Referencing tools. The value is



bondedinsulated (Short Integer) – Indicator of whether the rectifier cable is Bonded or Insulated.


cptraceability (Short Integer) – Indicator of whether the rectifier cable participates in a cathodic



cpoverride (Short Integer)- Override of the default cptraceability Indicator of whether the

rectifier cable participates in a cathodic protection zone. Coded Value Domain: CP_Traceability


the rectifier cable segment is located.


Rectifier Cable Migration Table UPDM 2016 to UPDM 2019:

















wirematerial Material N/A

depth Depth DEPTH


gauge Gauge GAUGE











engroutename Engineering RouteName ENGROUTENAME

engtom Engineering To Measure ENGTOM


continroutename Continuous RouteName CONTINROUTENAME

continfromm Continuous From Measure CONTINFROMM




fromreflocation From Reference Location FROMREFLOCATION






bondedinsulated Bonded Insulated N/A

cptraceability CP traceability N/A

cpoverride CP Override N/A

N/A CPTRACEWEIGHT


Devices Definition: The Device feature class models those components in the pipe system that have the ability to

interact with the commodity through impedance, filtration, or measurement.

Device features can be either stand-alone features on the map or contained in gas assemblies. For

example, a critical valve can be a single feature on the map, or it can be contained in an assembly such

as a compressor station.

Subtype Feature Layers:


• A device can connect to the following:

o Line at the end or beginning vertex—For example, an excess flow valve can connect

to a plastic PE service line.

o Junction—For example, a valve can connect to a coupling with a connectivity

association.

• A gas device can be contained in the following:

o Assembly—For example, a regulator can be contained in a regulator station.

o Structure boundary—For example, a compressor can be contained in a station

structure or vault.

Devices

Anode Compressor Controllable Tee

Controllable Valve

Excess Flow Valve

Flow Valve

Lamp Meter Pump Pressure Monitoring Device

Rectifier Regulator

Scrubber Short Stop

Relief Valve

Strainer Wellhead Source Flange

Test Point



This is the schema for the Device feature class.





issubnetworkcontroller Short Integer Required for Utility Network


subnetworkcontrollername Text(2000) Required for Utility Network

tiername Long Integer Required for Utility Network

tierrank Long Integer Required for Utility Network

terminalconfiguration Text(128) Required for Utility Network






adddetails Short Integer

devicestatus Short Integer Utility Network: Network Attribute


designtype Short Integer

accessible Short Integer Utility Network: Network Attribute

yesno Short Integer

turnstoclose Double(8,3)

normalposition Short Integer Utility Network: Network Attribute

installdate Date

inservicedate Date

assetid Text(64)

serialnumber Text(20)



lifecyclestatus Short Integer Utility Network: Network Attribute

maopdesign Double(16,5) Utility Network: Network Attribute

maoptest Double(16,5) Utility Network: Network Attribute

maoprecord Double(16,5) Utility Network: Network Attribute


depth Double(16,5)

depthtonut Double(16,5)

length Double(16,5)


maxinletpressure Double(16,5)

maxoutletpressure Double(16,5)

setpressureentered Double(16,5)

setpressurestandard Double(16,5)

rotation Short Integer

barcode Text(16)





material Text(2)

casingmaterial Text(20)

devicename Text(20)

quantity Double(8,2)

weight Double(16,5)

amperage Double(16,6)

usage Double(16,5)

duration Long Integer

height Double(16,5)

notes Text(2000)

iscritical Short Integer

flowcapacity Double(16,5)

permanentindicator Short Integer


depthunits Short Integer


flowcapacityunits Short Integer

heightunits Short Integer





usageunits Short Integer

usagerateunits Short Integer

recordingmethod Text(25)

regulatorbodytype Text(20)

outletdiameter Double(16,5)

diaphragmdiameter Double(16,5)

premise Text(10)

indoormeter Short Integer

operatingclassification Text(40)

maxdifferentialpressure Double(16,5)

companypaidtelephone Short Integer

telephonenumber Text(15)

usagerate Double(16,5)

gpsx Double(16,8)

gpsy Double(16,8)

gpsz Double(16,8)

legacyid Text(38)











engm Double(16,5) ArcGIS Pipeline Referencing Attribute



continm Double(16,5) ArcGIS Pipeline Referencing Attribute

refmethod Short Integer ArcGIS Pipeline Referencing Attribute

reflocation Text(50) ArcGIS Pipeline Referencing Attribute

refoffset Text(50) ArcGIS Pipeline Referencing Attribute



cptraceability Short Integer Utility Network: Network Attribute




wallthickness2 Doube(16,5)

diameter2 Double(16,5)

temprating Text(20)

usagetype Text(3)

coolingmethod Text(20)

rectifiertype Text(25)






Excess Flow Valve

The subtype feature layer Excess Flow Valve describes the devices typically installed in a service

line to prevent a pressure surge from propagating further down the pipe system. CFR 49

192.381 defines the performance standards for service line excess flow valves (EFV).


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

1 0 Unknown An unknown is an excess flow valve


1 1 Automatic

Reset

An excess flow valve with an

automatic reset.

1 2 Manual Reset An excess flow valve with a manual

reset.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the device feature participates.


issubnetworkcontroller (Short Integer) – The boolean true/false value indicating whether the

device is a subnetwork controller.

Coded Value Domain: Pipeline_IsSubnetworkController

isconnected (Short Integer) – The Boolean true/false value indicating whether the device is

connected to a subnetwork controller.

Coded Value Domain: Pipeline_IsConnected

subnetworkcontrollername (Text [2000]) – If the device is of an asset group/asset type which has

been designated as a subnetwork controller within the Utility Network configuration, this is the

unique name assigned to the device.

tiername (Long Integer) – If the device is of an asset group/asset type which has been

designated as a subnetwork controller within the Utility Network configuration, this is the name

of the tier to which the subnetwork controller is associated.

Coded Value Domain: Pipeline_TierName

tierrank (Long Integer) – If the device is of an asset group/asset type which has been designated

as a subnetwork controller within the Utility Network configuration, this is the rank of the tier to

which the subnetwork controller is associated.

terminalconfiguration (Text(128) - If the device is of an asset group/asset type which has been

designated as a subnetwork controller within the Utility Network configuration, this is name of

the terminal to which the subnetwork controller is associated.

creationdate (Date)—The date and time the excess flow valve record was originally created in



creator (Text[255])—The name of the system user who originally created the excess flow valve


lastupdate (Date)—The date and time the excess flow valve record was last modified in the



the excess flow valve record in the geodatabase. This value is automatically populated by the

Editor Tracking.



devicestatus (Short Integer) – A Boolean indicator of whether the device is open or closed to

allowing the flow of the commodity thru the device.

Coded Value Domain: Pipeline_DeviceStatus

regulatorytype (Short Integer)— The value indicating the regulatory status of the excess flow

valve feature. This is used by the Facility Reporting tools to differentiate between Distribution,



installdate (Date)—The date the construction of the excess flow valve was completed.

inservicedate (Date)—The date the excess flow valve was put into production.






ownedby (Short Integer)—The name of the organization with ownership of the excess flow valve




maintenance of the excess flow valve. In most instances, this will be the name of your

organization.



locationdescription (Text[255])—The textual description of the location of the excess flow valve.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the excess flow

valve.


diameter (Double[16,5])—The generalized edge-to-edge measured length of a straight line

through the center of the upstream excess flow valve orifice.


Diameter2 (Double[16,5])—The generalized edge-to-edge measured length of a straight line

through the center of the downstream excess flow valve orifice.


diameterunits (Short Integer)—The unit of measure used to define the diameter of the excess

flow valve.


wallthickness (Double[16,5])—The manufacturer defined thickness of the exterior wall of the

upstream excess flow valve orifice.


wallthickness2 (Double[16,5])— The manufacturer defined thickness of the exterior wall of the

downstream excess flow valve orifice



design.

Coded Value Domain: Pipeline_Pressure_Range


installation.



excess flow valve is currently operating.



pressure.



depth (Double[16,5])—The distance below the ground cover where the excess flow valve is

buried.

depthunits (Short Integer)—The unit of measure used to define the distance below the surface

where the excess flow valve is located.


barcode (Text[16])—The ASTM F2897-15 code read from the bar code on the device.

manufacturer (Text[2])—The organization that built the device.


manufacturerlotno (Long Integer)—The manufacturer lot number from which the device was

created.

manufacturedate (Date)—The date the device was created by the manufacturer.


that was followed when the excess flow valve feature was created.

Coded Value Domain: Pipeline_ASTMEFVModel

flowcapacity (Double[16,5])—The volume-based measurement of the flow of gas through the

excess flow valve.

flowcapacityunits (Short Integer)—The unit of measure for the volume of flow capacity.


notes (Text[2000])—Additional information about the excess flow valve.


management system information for this excess flow valve feature.


under which the excess flow valve feature was installed.


number under which a work order was generated to install the excess flow valve feature.







geodatabase.




populated.



populated.



populated.

servicesummaryid (GUID)—The foreign key unique value used to relate the excess flow valve

feature to the SERVICESSUMMARY feature class record with which it participates.

bondedinsulated (Short Integer) – A Boolean indicator of whether the device acts as a

conductive device (bonded) or an non-conductive device (insulated) in a cathodic protection

system. Coded Valve Domain: Bonded_Insulated.

cptraceability (Short Integer) – A Boolean indicator of whether the normal function of the device

is traceable in a cathodic protection zone. Coded Value Domain: CP_Traceability

cpoverride (Short Integer)- A Boolean indicator of a temporary state of whether the device is

traceable in a cathodic protection zone. Coded Valve Domain: CP_Traceability


organizations wanting to maintain the Excess Flow Valve features as event records with the













location on a route. This attribute is only used by organizations wanting to maintain the Excess

Flow Valve features as event records with the ArcGIS Pipeline Referencing tools. The value is



located. This attribute is only used by organizations wanting to maintain the Excess Flow Valve




located. This attribute is only used by organizations wanting to maintain the Excess Flow Valve




anomaly is located. This attribute is only used by organizations wanting to maintain the Excess

Flow Valve features as event records with the ArcGIS Pipeline Referencing tools. The value is




wanting to maintain the Excess Flow Valve features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the Excess Flow Valve features as event records with the ArcGIS Pipeline

Referencing tools.





This attribute is only used by organizations wanting to maintain the Excess Flow Valve features






maintain the Excess Flow Valve features as event records with the ArcGIS Pipeline Referencing



maintain the Excess Flow Valve features as event records with the ArcGIS Pipeline Referencing



the device is located.

systemsubnetworkname (Text[2000])—The name of the system zone tier subnetwork where the

device is located.

pressuresubnetworkname (Text[2000])—The name of the pressure zone tier subnetwork where


isolationsubnetworkname (Text[2000])—The name of the isolation zone tier subnetwork where



Excess Flow Valve Migration Table UPDM 2016 to UPDM 2019:





issubnetworkcontroller Is Subnetwork Controller N/A


subnetworkcontroller Subnetwork Controller N/A

tiername Tier Name N/A

tierrank Tier Rank N/A

terminalconfiguration Terminal Configuration N/A





globalid GlobalID Global ID

devicestatus Present Status N/A




assetid Asset ID FACILITYID

ownedby Owner OWNER






flowcapacity Flow Capacity CAPACITY

flowcapacityunits Flow Capacity Units N/A

diameter Diameter DIAMETER

diameter2 Diameter2 N/A


wallthickness Wall Thickness N/A

wallthickness2 Wall Thickness2 N/A

depth Depth DEPTH








manufacturerlotno Manufacture Lot# MANUFACTURERLOTNO


manufacturecomponent Manufacture Model MANUFACTUREMODEL







servicesummaryid Service Summary ID SERVICESUMMARY_GlobalID


gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z GPSZ

bondedinsulated Bonded Insulated INSULATORDEVICE

cptraceability CP Traceability N/A











N/A GASTRACEWEIGHT

cpsubnetworkname CP Subnetwork Name N/A

systemsubnetworkname System Subnetwork Name N/A

pressuresubnetworkname Pressure Subnetwork Name N/A

isolationsubnetworkname Isolation Subnetwork Name N/A


Meter

The subtype feature layer Meter describes a measuring device of the volume of commodity

flowing through the meter.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

2 0 Unknown An unknown is a meter whose type is

not known.

2 41 Custody

Transfer

A custody transfer meter is the

measuring device of the volume

received from another pipe

organization. A custody transfer

meter is typically located in a gas

facility such as a regulator station.

Custody transfer can be a source of

gas for a gas system.

2 42 Customer A customer meter is the measuring

device of the volume of the

commodity consumed by an

individual customer. A customer

meter is typically located in a meter

setting.

2 43 Utility A utility meter is the measuring

device of the volume of gas or oil at a

facility. A utility meter is typically

located in a facility such as a regulator

station or compressor station.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:




assettype (Short Integer)—A dscriminator field with a subtype-specific coded domain.























creationdate (Date)—The date and time the meter record was originally created in the



creator (Text[255])—The name of the system user who originally created the meter record in


lastupdate (Date)—The date and time the meter record was last modified in the geodatabase.



the meter record in the geodatabase. This value is automatically populated by the Editor

Tracking.



devicestatus (Short Integer) —The Boolean indicator of whether the device is open or closed.

Coded Value Domain: Pipeline_DeviceStatus

regulatorytype (Short Integer) —The value indicating the regulatory status of the meter feature.


Offshore Transmission, Gathering, and Offshore Gathering pipe.


designtype (Short Integer) —The type of meter device.

Coded Value Domain: Pipeline_MeterType

installdate (Date)—The date the construction of the meter was completed.

inservicedate (Date)—The date the meter was put into production.

assetid (Text[64]) —A layer-specific textual unique identifier.

ownedby (Short Integer)—The name of the organization with ownership of the meter. In most




maintenance of the meter. In most instances, this will be the name of your organization.


locationdescription (Text [100]) —The textual description of the location where the meter is

located.

lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the meter.



maopdesign (Double[16,5]) —The maximum allowable operating pressure as defined during

design.


maoptest (Double[16,5]) —The tested maximum allowable operating pressure during

installation.


maoprecord (Double[16,5]) —The maximum allowable operating pressure under which the

device is currently operating.


maopunits (Short Integer) —The unit of measure for defining the maximum allowable operating

pressure.


length (Double[16,5]) —The field measured longitudinal length of the device. The purpose of

this value is to provide additional information to load flow packages such as Synergee Gas.

lengthunits (Short Integer) —The unit of measure used to define the longitudinal length of the

meter.






barcode (Text [16]) —The ASTM F2897 code read from the bar code on the device.

manufacturer (Text [2]) —The organization who built the device.


manufacturerlotno (Long Integer) —The manufacturer lot number from which the device was

created.

manufacturedate (Date) —The date the device was created by the manufacturer.

manufacturecomponent (Text [2]) —The manufacturer-specified, industry standard specification

followed when the device feature was created.


Coded Value Domain: Pipeline_ASTM_Meter_Manufacture_Component


through the center of the upstream meter orifice.

Coded Value Domain: Pipeline_Meter_Diameter_Customer.


through the center of the downstream meter orifice.

Coded Value Domain: Pipeline_Meter_Diameter_Customer.

diameterunits (Short Integer)—The unit of measure used to define the diameter of the meter



upstream meter orifice.

Wallthickness2 (Double[16,5])—The manufacturer defined thickness of the exterior wall of the

downstream meter orifice.

flowcapacity (Double[16,5]) —The volume-based measurement of the flow of gas through the

meter.

flowcapacityunits (Short Integer) —The units of measure used for the volume of flow capacity.


yesno (Short Integer) —Indicates whether the meter is classified as an internal meter.


recordingmethod (Text[20]) —The method used by the meter to record the volume of flow.

serialnumber (Text[20]) —The unique identifier physically labeled on the device.

premise (Text[10]) —The Customer Information System unique identifier that links the meter to

the customer record.

notes (Text[2000]) —Additional information about the device.

assetunitcode (Text [38]) —The foreign key value used to link this record to the utilities asset

management system information for this device feature.

workorderid (Text [38]) —The work management system value used to identify the task number

under which the device feature was installed.


projectnumber (Text [38]) —The work management system value used to identify the project

number under which a work order was generated to install the device feature.

legacyid (Text (38]) —A unique identifier used to relate this record to its predecessor record

from a previous mapping/asset system. This provides continuity between the old system and the


servicesummaryid (GUID) —The foreign key unique value used to relate the device feature to

the SERVICESSUMMARY feature class record with which it participates.

spatialaccuracy (Short Integer) —This short integer value provides an assessment of the spatial


geodatabase.

Coded Value Domain: Spatial_Accuracy

gpsx(Double[16,8]) —The original longitudinal coordinate of the feature when it was originally

included in the geodatabase. If using the attribute rules capability, this value can be

automatically populated.

gpsy (Double[16,8]) —The original latitudinal coordinate of the feature when it was originally



gpsz (Double[16,8]) —The original elevation coordinate of the feature when it was originally










eventid (Text [38]) —The unique ID for each event record. This attribute is only used by

organizations wanting to maintain the device features as event records with the ArcGIS Pipeline


Referencing tools.


fromdate (Date) —The date the event became active on the route. This attribute is only used by



Referencing tools.

todate (Date) —The date the event was retired from the route. This attribute is only used by



Referencing tools.

locationerror(Text [100]) —The resultant message from the process of defining the event’s

location on a route. This attribute is only used by organizations wanting to maintain the device



engrouteid (Text [38]) —The unique ID of the engineering network route where the event is

located. This attribute is only used by organizations wanting to maintain the device features as

event records with the ArcGIS Pipeline Referencing tools. The value is automatically generated

and populated by the ArcGIS Pipeline Referencing tools.

engroutename (Text [100]) —The unique ID of the engineering network route where the event is




engm (Double[16,5]) —The measure location along the engineering network route where the

anomaly is located. This attribute is only used by organizations wanting to maintain the device



continrouteid (Text[38]) —The continuous network route ID that is automatically created and


wanting to maintain the Meter features as event records with the ArcGIS Pipeline Referencing

tools.

continroutename (Text[100]) —The continuous network name that is automatically created and


wanting to maintain the Meter features as event records with the ArcGIS Pipeline Referencing

tools.


continm (Double[16,5]) —The continuous network measure along the continrouteid route. This


refmethod (Short Integer) —The method of referencing the offset feature. This can be


This attribute is only used by organizations wanting to maintain the device features as event


Referencing tools.

reflocation (Text [50]) —The location of the offsetting feature. This can be Coordinates,


maintain the device features as event records with the ArcGIS Pipeline Referencing tools. The


refoffset(Text [50]) —The offset measure. This attribute is only used by organizations wanting to






device is located.






Meter Migration Table UPDM 2016 to UPDM 2019:





issubnetworkcontroller Is Subnetwork

Controller

N/A


subnetworkcontroller Subnetwork

Controller

N/A



terminalconfiguration Terminal

Configuration

N/A






devicestatus Device Status N/A

designtype Meter Type METERTYPE

regulatorytype System Type N/A

installdate Install Date N/A



ownedby Owner OWNER



locationdescription Location Description N/A

lifecyclestatus Life Cycle Status N/A




rotation Rotation N/A

barcode Barcode N/A

manufacturer Manufacturer N/A

manufacturerlotno Manufacture Lot# N/A

manufacturedate Manufacture Date N/A

manufacturecomponent Manufacture Model N/A

maopunits MAOP Units MAOPUNITOFMEASURE

diameter Diameter N/A

diameter2 Diameter 2 N/A


wallthickness2 Wall Thickness 2 N/A

recordingmethod Recording Method RECORDINGMETHOD

flowcapacity Flow Capacity FLOWCAPACITY


serialnumber Serial Number SERIALNUMBER

premise Premise N/A

yesno Indoor Meter N/A

projectnumber Project Number N/A


workorderid Work Order ID N/A


notes Comments N/A

servicesummaryid Service Summary ID N/A


gpsx GPS X N/A

gpsy GPS Y N/A

gpsz GPS Z N/A

eventid N/A

fromdate N/A

todate N/A

locationerror N/A

engrouteid N/A

engroutename N/A

engm N/A

continrouteid N/A

continroutename N/A

continm N/A

refmethod N/A

refoffset N/A

reflocation N/A

N/A MeterSetting_GlobalID

N/A RURALTAP_GlobalID

N/A TOWNBORDERSTATION_GlobalID





isolationsubnetworkname Isolation Subnetwork Name N/A


Controllable Valve

The subtype feature layer Controllable Valve describes the component that can permit or

prevent the flow through the pipe system. These components are used within a utility network

to perform valve isolation traces.

GeometryType: Point with Z and M enabled

Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

3 0 Unknown An unknown is a valve whose type is not

known.

3 482 Bypass A bypass controllable valve is a device

typically located within a facility such as

a regulator station or pump station. Its

purpose is to allow or disallow the flow

of the commodity around the facilities

primary devices such as a regulator or

pump.

3 483 Emergency An emergency controllable valve is a

device capable of impeding the flow of

the commodity through the pipe

system. The emergency controllable

valve is considered a source for the

commodity in an isolation subnetwork.

3 485 System A system controllable valve is a device

capable of impeding the flow of the

commodity through the pipe system.

The system controllable valve is not

considered a source for the commodity

in an isolation subnetwork.

3 486 Meter A meter controllable valve is the valve

located within a meter set.

Container: No

Attachments: Yes


Editor Tracking:







Attributes:

objectid (Long Integer)–The geodatabase generated and maintained unique identifier value.

assetgroup (Long Integer) - Geodatabase subtype field. The subtype field defines the general

classification of the device features.

assettype (Short Integer) – Defines the sub-classification of the device features.

associationstatus (Short Integer) – An indicator of the type of utility network association to


Coded Value Domain: Pipeline_AssocationStatus.




















creationdate (Date) - The date and time when the device record was originally created in the



creator (Text[255]) - The name of the system user who originally created the device record in


lastupdate (Date) - The date and time when the device record was last modified in the


updatedby (Text[255]) - The name of the system user responsible for the last modification to the

device record in the geodatabase. This value is automatically populated by the Editor Tracking.

globalid (GlobalID)- The system-wide unique identifier. This is the primary key value for


devicestatus (Short Integer) – The Boolean indicator of whether the device is open or closed.

Coded Value Domain: Pipeline_Valve_Status

regulatorytype (Short Integer) – The value indicating the regulatory status of valve feature.


Offshore Transmission, Gathering or Offshore Gathering pipe.


designtype (Short Integer) - The type of valve.

Coded Value Domain: Pipeline_Valve_type

accessible (Short Integer) - The value used by the Gas Editing solution’s isolation trace tool to

identify when a valve is no longer accessible for the purpose of emergency shutoffs.


turnstoclose (Double[8,3]) - The number of 360-degree turns required to close the valve.

Yesno (Short Integer) - The yes/no Boolean value indicating whether the valve is turned

clockwise to close.


normalposition (Short) - The Boolean value indicating whether the valve’s most frequent

position is open or closed.

Coded Value Domain: Pipeline_Valve_Position

installdate (Date)–The date when the construction of the device feature was completed.

inservicedate (Date) – The date when the device feature was put into production.

assetid (Text[64]) - A layer-specific textual unique identifier.


locationdescription (Text[100]) - The textual description of the location where the valve is

located.

lifecyclestatus (Short Integer) - The text value indicating the life cycle state of the device. Coded

Value Domain: Pipeline_LifeCycle_Status

maopdesign (Double[16,5]) – The maximum allowable operating pressure as defined during

design.


maoptest (Double[16,5]) – The tested maximum allowable operating pressure during

installation.


maoprecord (Double[16,5]) – The maximum allowable operating pressure under which the



depth (Double[8,3]) – The DEPTH value is the vertical distance below the surface.

depthtonut (Double[16,5]) - The DEPTHTONUT value is the vertical distance below the surface to

access the valve nut.

length (Double[16,5]) - The field measured longitudinal length of the device. The purpose of this

value is to provide additional information to load flow packages like Synergee Gas.

lengthunits (Short Integer) - The unit of measure used to define the longitudinal length of the

Valve.


diameter (Double[16,5]) - The nominal edge to edge measured length of a straight line through

the center of the inflow valve orifice.

Coded Value Domain: Pipeline_Valve_Diameter

Diameter2 (Double[16,5]) - The nominal edge to edge measured length of a straight line through

the center of the outflow valve orifice.


diameterunits (Short Integer) - The unit of measure for defining the width of the orifice of the

valve.

Coded Value Domain: Units_For_Diameter.



inflow controllable valve orifice.


outflow controllable valve orifice.

rotation (Short Integer) - This value defines the angular degrees that the point symbol should be

rotated. The purpose is to have the device display symbology automatically rotated to the angle



barcode (Text [16])–The ASTM F2897 code read from the bar code on the device.

manufacturer (Text [2])–The organization who built the device.


manufacturerlotno (Long Integer)–The manufacturer lot number from which the device was

created.

manufacturedate (Date)–The date when the device was created by the manufacturer.

manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification


Coded Value Domain: Pipeline_ASTMF_Valve_Manufacture_Component

material (Text [2]) - The primary material used in the construction of the valve.

Coded Value Domain: Pipeline_ASTM_Material

maopunits (Short Integer) – The unit of measure for defining the maximum allowable operating

pressure.

Coded Value Domain: Units_For_Pressure.

depthunits (Short Integer) – The unit of measure for defining the distance of the valve below the

ground surface.

Coded Value Domain: Units_For_Depth.

notes (text[2000]) – Additional information about the device.

assetunitcode (Text [38])–The foreign key value used to link this record to the utilities asset



workorderid (Text [38])–The work management system value used to identify the task number


projectnumber (Text [38])–The work management system value used to identify the project


legacyid (Text (38])–A unique identifier used to relate this record to its predecessor record from

a previous mapping/asset system. This provides continuity between the old system and the


spatialaccuracy (Short Integer)- This short integer value provides and assessment of the spatial

accuracy of the coordinates of the feature’s geometry when the feature is inserted into the

geodatabase.

Coded Value Domain: Spatial_Accuracy.

gpsx(Double[16,8])- The original longitudinal coordinate when the feature was originally

inserted into the geodatabase. If using attribute rules capability, this value can be automatically

populated.

gpsy (Double[16,8])- The original latitudinal coordinate when the feature was originally inserted

into the geodatabase. If using the attribute rules capability, this value can be automatically

populated.

gpsz (Double[16,8])- The original elevation coordinate when the feature was originally inserted


populated.








eventid (Text [38])–The unique ID for each event record. This attribute is only used by



Referencing tools.


fromdate (Date)–The date the event became active on the route. This attribute is only used by



Referencing tools.

todate (Date)–The date the event was retired from the route. This attribute is only used by



Referencing tools.

locationerror(Text [100])–The resultant message from the process of defining the event’s




engrouteid (Text [38])–The unique ID of the engineering network route which the event is




engroutename (Text [100])–The unique ID of the engineering network route which the event is




engm(Double[16,5])–The measure location along the engineering network route where the




continrouteid (Text[38]) – The continuous network Route ID which will be automatically created

and maintained by the ArcGIS Pipeline Referencing tools. This attribute is only used by

organizations wanting to maintain the features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100]) – The continuous network name which will be automatically

created and maintained by the ArcGIS Pipeline Referencing tools. This attribute is only used by


Referencing tools.

continm (Double[16,5]) – The continuous network measure along the continrouteid route. This

value will be automatically created and maintained by the ArcGIS Pipeline Referencing tools.


refmethod (Short Integer)–The method of referencing the offset feature. Can be Coordinates,

Stationing, Length, LRS Network, Event Intersection, or other point feature class. This attribute is

only used by organizations wanting to maintain the device features as event records with the

ArcGIS Pipeline Referencing tools. The value is populated by the ArcGIS Pipeline Referencing

tools.

reflocation (Text [50])–The location of the offsetting feature. Can be Coordinates,

Feature/EventID and/or IntersectionID. This attribute is only used by organizations wanting to



refoffset(Text [50])–The offset measure. This attribute is only used by organizations wanting to






device is located.






Controllable Valve Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Valve


assettype Asset Type VALVEUSE



Controller

N/A


subnetworkcontrollername Subnetwork

Controller Name

N/A




Configuraiton

N/A






devicestatus Device Status PRESENTPOSITION


designtype Valve Type VALVETYPE

accessible Accessible ACCESIBLE

turnstoclose Turns to Close TURNSTOCLOSE

yesno Clockwise to Close CLOCKWISETOCLOSE

normalposition Normal Position NORMALSTATUS





locationdescription Location

Description

LOCATIONDESCRIPTION




maoprecord maoprecord MAOPRECORD

depth Depth DEPTH

depthtonut Depth to Nut DEPTHTONUT

length Length N/A








manufacturerlotno Manufacture Lot

No

MANUFACTURELOTNO


manufacturecomponent Manufacture

Model

MANUFACTUREMODEL

material Material MATERIAL

maopunits MAOP Units MAOPUNITMEASURE




notes Comments COMMENTS






GPSX GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A

bondedinsulated Bonded Insulated INSULATORDEVICE







engrouteid Engineering

RouteID

ENGROUTEID


Name

ENGROUTENAME

engm Engineering

Measure

ENGM

continrouteid Continuous

RouteID

CONTINROUTEID



Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM




cpsubnetworkname CP Subnetwork

Name

N/A

systemsubnetworkname System Subnetwork

Name

N/A

pressuresubnetworkname Pressure

Subnetwork Name

N/A

isolation subnetwork name Isolation

Subnetwork Name

N/A


Flow Valve

The subtype feature layer Flow Valve describes the component that restricts the flow of the

commodity to a singe direction.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

4 0 Unknown An unknown is a valve whose type is not

known.

4 261 Check A check flow valve is a device which

restricts the flow of the commodity to a

single direction. These devices typically

have a spring hinged flap which will

automatically close if the commodity

attempts to flow in the reverse

direction.

4 262 Slam-Shut A flow slam-shut valve is a device which

automaticailly closes when a pressure

reading is outside of the specified

range.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:







































Coded Value Domain: Pipeline_DeviceStatus.

regulatorytype (Short Integer) – The value indicating the regulatory status of valve feature.







locationdescription (Text[100]) - The textual description of the location where the valve is

located.




design.



installation.







pressure.




ground surface.





Valve.


diameter (Double[16,5]) - The nominal edge to edge measured length of a straight line through



diameter2 (Double[16,5]) - The nominal edge to edge measured length of a straight line through

the center of the outflow valve orifice.



valve.



inflow flow valve orifice.


outflow flow valve orifice.







manufacturer (Text [2])–The organization who built the device.


manufacturerlotno (Long Integer)–The manufacturer lot number from which the device was

created.

manufacturedate (Date)–The date when the device was created by the manufacturer.



Coded Value Domain: Pipeline_ASTMMeterModel

material (Text[2]) - The primary material used in the construction of the valve.


notes(Text[2000]) – Additional information about the device.







legacyid (Text (38])–A unique identifier used to relate this record to its predecessor record from





geodatabase.




populated.




populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Flow Valve Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Valve





Controller

N/A



Controller Name

N/A




Configuration

N/A












Description

LOCATIONDESCRIPTION





maoprecord maoprecord MAOPRECORD

depth Depth DEPTH





length Length N/A





No

MANUFACTURELOTNO



Model

MANUFACTUREMODEL













gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A









RouteID

ENGROUTEID


Name

ENGROUTENAME

engm Engineering

Measure

ENGM


RouteID

CONTINROUTEID


Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM






Name

N/A


Name

N/A


Subnetwork Name

N/A

isolationsubnetworkname Isolation

Subnetwork Name

N/A


Relief Valve

The subtype feature layer Relief Valve describes the device in a pipe system that is responsible

for automatically opening when the pressure rises above a set pressure. This is designed to

prevent over pressure damage to the pipe system. Relief valves are typically located within

facilities such as regulator stations and town border stations.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

5 0 Unknown An unknown is a relief valve whose

type is not known.

5 21 Blow off A pressure sensitive device which will

open to release pressure when a set

pressure is exceeded.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:








































regulatorytype (Short Integer) – The value indicating the regulatory status of device feature.







ownedby (Short Integer)—The name of the organization with ownership of the relief valve. In




maintenance of the relief valve. In most instances, this will be the name of your organization.


locationdescription (Text[100]) - Textual description of the location of the relief valve.



maopdesign (Double[16,5]) – The maximum allowable operating pressure as defined during design. Coded Value Domain: Pipeline_Pressure_Range



installation.





maopunits (Short Integer) – The unit of measure for defining the maximum allowable operating pressure. Coded Value Domain: Units_For_Pressure.

diameter (Double[16,5]) - The nominal edge to edge, measured length of a straight line through


diameter2 (Double[16,5]) - The nominal edge to edge, measured length of a straight line

through the center of the outflow valve orifice.


valve.



inflow flow valve orifice.


outflow flow valve orifice.




Relief Valve.


setpressureentered (Double[16,5]) - The pressure at which the relief valve is designed to open.

setpressurestandard (Double[16,5]) - The standard operating pressure through the relief valve.






barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. Coded Value Domain: Pipeline_ASTM_Manufacturer manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification followed when the device feature was created. material (Text[2]) – Primary material used for the construction of the relief valve. Coded Value Domain: Pipeline_ASTM_Material pressureunits (Short Integer) - The unit of measure for defining the set pressure.


flowcapacity (Double[16,5]) – The volume based measurement of the flow of gas thru the relief valve. flowcapacityunits (Short Integer) – The units of measure used for the volume of flow capacity. Coded Value Domain: Units_For_Volume

notes (Text[2000]) - The nonstructured information about the relief valve.

assetunitcode (Text [38])–The foreign key value used to link this record to the utilities asset management system information for this device feature.







geodatabase.





populated.



populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Relief Valve Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_ReliefValve



associationstatus Association

Status

N/A











ownedby Owned By N/A



Description

LOCATIONDESCRIPTION








diameterunits DiameterUnits N/A



length Length N/A


flowcapacity Flow Capacity CAPACITY

flowcapacityunits Flow Capacity

Units

N/A

setpressureentered Set Pressure

Entered

SETPRESSUREENTERED

setpressurestandard Set Pressure

Standard

SETPRESSUURESTANDARD





No

MANUFACTURELOTNO

manufacturedate Manufacture

Date

MANUFACTUREDATE


Model

MANUFACTUREMODEL


pressureunits Pressure Units SETPRESSUREUNITOFMEASURE











gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A






RouteID

ENGROUTEID

engroutename Engineering

Route Name

ENGROUTENAME

engm Engineering

Measure

ENGM


RouteID

CONTINROUTEID

continroutename Continuous

Route Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM

refmethod Reference

Method

REFMETHOD


reflocation Reference

Location

REFLOCATION


N/A REGULATORSTATION_globalid

N/A TOWNBORDERSTATION_globalid


Name

N/A

systemsubnetworkname System

Subnetwork

Name

N/A


Subnetwork

Name

N/A


Subnetwork

Name

N/A


Scrubber

The subtype feature layer Scrubber describes the component within a pipe system that removes

free liquids or dirt particles from the commodity fluid or gas.


Relationships:

-P_Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

20 0 Unknown An unknown is a scrubber whose

type is not known.

20 561 Scrubber A generic scrubber asset.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:















































ownedby (Short Integer)—The name of the organization with ownership of the scrubber. In




maintenance of the scrubber. In most instances, this will be the name of your organization.







installation.








Scrubber.



the center of the inflow scrubber orifice.


through the center of the outflow scrubber orifice.


scrubber.



inflow flow scrubber orifice.


outflow flow scrubber orifice.





barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created.


manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification


material (Text[2]) - The primary material used in the construction of the srubber encasement.


pressure.


notes (Text[2000]) - The nonstructured information about the scrubber.

assetunitcode (Text [38])–The foreign key value used to link this record to the utilities asset management system information for this device feature. legacyid (Text [38])–A unique identifier used to relate this record to its predecessor record from









geodatabase.




populated.



populated.




populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.











device is located.


Scrubber Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Scrubber





Controller

N/A

isconnected isconnected N/A


Controller Name

N/A




Configuration

N/A











ownedby Owner By OWNER









length Length N/A











No

MANUFACTURELOTNO



Model

MANUFACTUREMODEL

material Material N/A








gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A









RouteID

ENGROUTEID


Name

ENGROUTENAME

engm Engineering

Measure

ENGM


RouteID

CONTINROUTEID


Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM






Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Strainer

The subtype feature layer Strainer describes the component within a pipe system that removes

free liquids or dirt particles from the commodity fluid or gas.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

6 0 Unknown An unknown is a strainer whose

type is not known.

6 442 Strainer A generic strainer asset.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:







































Coded Value Domain: Pipeline_Device_Status.








ownedby (Short Integer)—The name of the organization with ownership of the strainer. In most




maintenance of the strainer. In most instances, this will be the name of your organization.







installation.






pressure.



the center of the inflow strainer orifice.


through the center of the outflow strainer orifice.


strainer.



inflow flow strainer orifice.


outflow flow strainer orifice.




Strainer.








manufacturer (Text [2])–The organization who built the device. Coded Value Domain: Pipeline_ASTM_Manufacturer manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification


Coded Value Domain: Pipeline_ASTMStrainerModel

material (Text[2]) - The primary material used in the construction of the strainer encasement.

Coded Value Domain: Pipeline_ASTM_Component_Material

pressureunits (Short Integer) - The unit of measure for defining the maximum differential

pressure.


yesno (Short Integer) - The yes/no Boolean value indicating whether the strainer is equipped

with a drain valve.


maxdifferentialpressure (Double[16,5]) - The manufacturer-specified maximum pressure drop

difference between the strainer upstream pressure and the strainer downstream pressure.

notes(Text[2000]) - The nonstructured information about the strainer.











geodatabase.




populated.



populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Scrubber Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Scrubber





Controller

N/A


subnetworkcontrollername Subnetwork Controller

Name

N/A















owner Owner OWNER



diameter Connection Diameter CONNECTIONDIAMETER





maxdifferentialpressure Max Differential

Pressure

MAXDIFFERENTIALPRESSURE


yesno Drain Valve Indicator DRAINVALVEINDICATOR








manufacturerlotno Manufacture Lot No MANUFACTURELOTNO











gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A










Name

ENGROUTENAME




Name

CONTINROUTENAME







Name

N/A


pressuresubnetworkname Pressure Subnetwork

Name

N/A

isolationsubnetworkname Isolation Subnetwork

Name

N/A


Pressure Monitoring Device

The subtype feature layer Pressure Monitoring Device describes the component in a pipe system

that can measure and record the flow at the installed location. These devices can be installed to

permanently measure flow and to temporarily measure flow at a specific location.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

8 0 Unknown An unknown is a pressure

monitoring device whose type is

not known.

8 81 Pressure

Monitoring

Device

A generic pressure monitoring

device asset.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:















































locationdescription (Text[100]) - The textual description of the location of the device.



ownedby (Short Integer)—The name of the organization with ownership of the pressure

monitoring device. In most instances, this will be the name of your organization.



maintenance of the pressure monitoring device. In most instances, this will be the name of your





installation.






pressure.



the center of the inflow pressure monitoring device orifice.


through the center of the outflow pressure monitoring device orifice.


pressure monitoring device.



inflow flow pressure monitoring device orifice.


outflow flow pressure monitoring device orifice.




Strainer.










companypaidtelephone (Short Integer) - The yes/no Boolean value indicating whether the device can be monitored remotely. Coded Value Domain: Yes_No telephonenumber (Text[15]) - The telephone number to access the pressure monitoring device. quantity (Long Integer) - The length of time the pressure monitoring device will be in use. Yesno (Short Integer) - The yes/no Boolean value indicating whether the installation of the device is permanent. Coded Value Domain: Yes_No recordingmethod (Short Integer) - The method used by the device to record pressure data. scada (Short Integer) - The yes/no Boolean value indicating whether the device is SCADA monitored. Coded Value Domain: Yes_No. temprating (Text[20]) - The manufacturer’s specified temperature rating. usagetype (Text[3]) - The type of pressure monitoring device.

notes (Text[2000]) - The nonstructured information about the pressure monitoring device.











geodatabase.




populated.



populated.



populated.











Referencing tools.




Referencing tools.





Referencing tools.




















Referencing tools.




Referencing tools.







tools.












device is located.






PressureMonitoringDevice Migration Table UPDM 2016 to UPDM 2019:


P_PressureMonitoringDevice





Controller

N/A



Name

N/A














ownedby Owner OWNER









length Length N/A




diameterunits Diameter units N/A









companypaidtelephone Company Paid

Telephone

COMPANYPAIDTELEPHONE

telephonenumber Telephone Number TELEPHONENUMBER

quantity Duration DURATION

yesno Permanent Indicator PERMANENTINDICATOR

recordingmethod Recording Method RECORDINGMETHOD


scada SCADA SCADA

temprating Temp Rating TEMPRATING

usagetype Usage Type USAGETYPE







gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A



cpoverride CP Over Ride N/A







Name

ENGROUTENAME





Name

CONTINROUTENAME







Name

N/A


Name

N/A


Name

N/A


Lamp

The subtype feature layer Lamp describes street lamps that are fueled by natural gas.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

9 0 Unknown An unknown is a gas Lamp whose

type is not known.

9 121 Gas Lamp A generic gas Lamp asset.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:















































ownedby (Short Integer)—The name of the organization with ownership of the lamp. In most




maintenance of the lamp. In most instances, this will be the name of your organization. Coded

Value Domain: Asset_Manager






installation.






pressure.



the center of the inflow lamp device orifice.


through the center of the outflow lamp device orifice.


lamp device.



inflow flow lamp device orifice.


outflow flow lamp device orifice.




lamp.












height (Double[16,5]) - The vertical distance from the ground surface to the highest point on the

gas lamp.

heightunits (Short Integer) - The unit of measurement for the value stored in the HEIGHT

attribute. Coded Value Domain: Pipeline_UnitsForHeight

yesno (Short Integer) - The yes/no Boolean value indicating whether the gas lamp is equipped

with a meter.


quantity (Double[16,5]) - The amount of natural gas consumed by the gas lamp during a typical

billing cycle.

usageunits (Short Integer) - The unit of measurement for the value stored in the USAGE

attribute. Coded Value Domain: Units_For_Volume

usagerate (Double[16,5]) - The rate of natural gas consumption by the gas lamp when it is in

use.

usagerateunits (Short Integer) – The unit of measurement for the value stored in the usagerate

attribute.

Coded Value Domain: Pipeline_UnitsForFlow

notes (Text[2000]) - The nonstructured information about the lamp.



legacyid (Text [38])–A unique identifier used to relate this record to its predecessor record from









geodatabase.




populated.



populated.



populated.











Referencing tools.





Referencing tools.




Referencing tools.




















Referencing tools.




Referencing tools.








tools.











device is located.






Lamp Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_GasLamp





Controller

N/A


subnetworkcontrollername Is Subnetwork

Controller Name

N/A




Configuration

N/A











ownedby Owner OWNER








DIAMETER Diameter N/A

Diameter2 Diameter 2 N/A

Diameterunits Diameter Units N/A

Wallthickness Wall Thickness N/A

Wallthickness2 Wall Thickness 2 N/A

length length N/A






No

MANUFACTURELOTNO



Model

MANUFACTUREMODEL

material Material N/A

height Height HEIGHT

heightunits Height Units HEIGHTUNITSOFMEASURE

yesno Metered METERED

quantity Usage GASUSAGE


usageunits Usage Units GASUSAGEUNITS

usagerate Usage Rate N/A

usagerateunits Usage Rate Units N/A







gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A









RouteID

ENGROUTEID


Name

ENGROUTENAME

engm Engineering

Measure

ENGM



RouteID

CONTINROUTEID


Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM



Location

REFLOCATION



Name

N/A

systemsubnetworkname Systen

Subnetwork Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Compressor

The subtype feature layer Compressor describes the device that can mechanically increase the

gas pressure in the pipe system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

10 0 Unknown An unknown is a Compressor


10 161 Electric Motor A electric motor compressor uses

electrically powered pistons to

compress the gas.

10 162 Reciprocating

Engine

A reciprocating engine compressor

uses internal combustion engine to

power pistons to compress the gas.

10 163 Turbine A turbine compressor uses a series

of rotating blades to compress the

gas.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:















































ownedby (Short Integer)—The name of the organization with ownership of the compressor. In




maintenance of the compressor. In most instances, this will be the name of your organization.







installation.






pressure.



the center of the inflow compressor orifice.


through the center of the outflow compressor orifice.


compressor.



inflow flow compressor orifice.


outflow flow compressor orifice.




compressor.


maxinletpressure (Double[16,5]) - The maximum pressure allowed at the inlet of the compressor unit. maxoutletpressure (Double[16,5]) - The maximum pressure allowed to exit the compressor unit.






barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification


pressureunits (Short Integer) - The units of measurement used for the maxinletpressure and maxoutletpressure attribute values. Coded Value Domain: Units_For_Pressure.

notes (Text[2000]) - The nonstructured information about the compressor.










geodatabase.




populated.




populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Compressor Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_CompressorUnits





Controller

N/A



Controller Name

N/A




Configuration

N/A










assetid FacilityID N/A














length Length N/A


maxinletpressure Max Inlet Pressure MAXINLETPRESSURE

maxoutletpressure Max Outlet

Pressure

MAXOUTLETPRESSURE





No

MANUFACTURELOTNO



Model

MANUFACTUREMODEL

pressureunits Pressure Units PRESSUREUNITS








gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A









RouteID

ENGROUTEID


Name

ENGROUTENAME

engm Engineering

Measure

ENGM


RouteID

CONTINROUTEID


Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM





N/A COMPRESSORSTATION_globalid


Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Wellhead Source Flange

The subtype feature layer Wellhead Source Flange describes the device on the wellhead that is

the subnetwork controller source for gathering and storage systems.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

11 0 Unknown An unknown is a Wellhead Source

Flange whose type is not known.

11 20 Flange A generic Wellhead Source Flange

asset. This is the flange which

connects the wellhead to the well.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:












































Value Domain: Pipeline_LifeCycle_Status_Combined



installation.






pressure.



the center of the inflow wellhead source flange orifice.



through the center of the outflow wellhead source flange orifice.


wellhead source flange.



inflow flow wellhead source flange orifice.


outflow flow wellhead source flange orifice.




wellhead source flange.






barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. Coded Value Domain: Pipeline_ASTM_Manufacturer manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification




notes (Text[2000]) - The nonstructured information about the wellhead source flange.









geodatabase.




populated.



populated.



populated.











Referencing tools.





Referencing tools.




Referencing tools.




















Referencing tools.




Referencing tools.








tools.











device is located.






Wellhead Source Flange Migration Table UPDM 2016 to UPDM 2019:

The UPDM 2016 model did not define Wellhead Source Flange as a separate feature class. This is a new feature layer for UPDM 2019.


Controllable Tee

The subtype feature layer Controllable Tee describes the fittings that can mechanically control

the flow of fluids or gases through the pipe system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

12 0 Unknown An unknown is a Controllable Tee


12 241 Controllable

Tee

A generic Controllable Tee asset.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:








































regulatorytype (Short Integer) - The value indicating the regulatory status of the controllable tee

feature. This is used by the Facility Reporting tools to differentiate between Distribution,

Transmission, Offshore Transmission, Gathering or Offshore Gathering pipe.




Coded Value Domain: yes_no

normalposition (Short) - The predominant position of the controllable tee. Coded Value Domain: Pipeline_ValvePosition




ownedby (Short Integer)—The name of the organization with ownership of the controllable tee.




maintenance of the controllable tee. In most instances, this will be the name of your

organization.







installation.






pressure.



the center of the inflow controllable tee orifice.


through the center of the outflow controllable tee orifice.


controllable tee.



inflow flow controllable tee orifice.


outflow flow controllable tee orifice.




controllable tee









material (Text[2]) - The predominant material used in the manufacture of the controllable tee. Coded Value Domain: Pipeline_PipeFittingMaterial

notes(Text[2000]) - The nonstructured information about the controllable tee.

legacyid (Text[38]) - A unique identifier used to relate this record to its predecessor record from


current Esri data model.








geodatabase.




populated.




populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Controllable Tee Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: ControllableFitting





Controller

N/A



Controller Name

N/A




Configuration

N/A








accessible Accessible N/A

normalposition Normal Position NORMALPOSITION



assetid FacilityID N/A








maopunits MAOP Units MAOPUNITSOFMEASURE




wallthickness Wallthickness N/A

wallthickness2 Wall Thickness2 N/A

length Length N/A









notes Comments N/A







gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A

N/A GASTRACEWEIGHT










Name

ENGROUTENAME




Name

CONTINROUTENAME








Name

N/A


Name

N/A


Name

N/A


Short Stop

The subtype feature layer Short Stop describes the fittings that can mechanically control the

flow of fluids or gases through the pipe system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

13 0 Unknown An unknown is a Short Stop whose

type is not known.

13 461 Short Stop A generic Short Stop asset.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:








































regulatorytype (Short Integer) - The value indicating the regulatory status of the short stop


Transmission, Offshore Transmission, Gathering or Offshore Gathering pipe.




Coded Value Domain: Pipeline_Accessible

normalposition (Short) - The predominant position of the short stop. Coded Value Domain: Pipeline_ValvePosition




ownedby (Short Integer)—The name of the organization with ownership of the short stop. In




maintenance of the short stop. In most instances, this will be the name of your organization.







installation.






pressure.




ground surface.



the center of the inflow short stop orifice.


through the center of the outflow short stop orifice.


short stop.



inflow flow short stop orifice.


outflow flow short stop orifice.





short stop.








material (Text[2]) - The predominant material used in the manufacture of the short stop. Coded Value Domain: Pipeline_ASTM_Material

notes (Text[2000]) - The nonstructured information about the short stop.












geodatabase.




populated.



populated.










populated.




Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Short Stop Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: ControllableFitting





Controller

N/A



Controller Name

N/A




Configuration

N/A








accessible Accessible N/A

normalposition Normal Position NORMALPOSITION



assetid assetid N/A


ownedby Owned By OWNER






maopunits MAOP Units maopunitsOFMEASURE

depth Depth N/A





wallthickness Wallthickness N/A

wallthickness2 Wallthickness 2 N/A

length Length N/A









notes Comments N/A







gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A










Name

ENGROUTENAME




Name

CONTINROUTENAME






N/A GASTRACEWEIGHT



Name

N/A


Name

N/A

isolationsubnetworkaname Isolation Subnetwork

Name

N/A


Anode

The subtype feature layer Anode describes the corrosive component that sacrifices its electrons

to protect the metal of the pipe system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

50 0 Unknown An unknown is an anode whose

type is not known.

50 281 Carbon-

Graphite

An anode comprised of the material

carbon-graphite.

50 282 Cast Iron An anode comprised of the material

cast iron.

50 283 Galvanic An anode comprised of the material

galvanic.

50 284 Graphite An anode comprised of the material

graphite.

50 285 Magnesium An anode comprised of the material

magnesium.

50 286 Magnesium

(High Grade B)


High Grade B Magnesium.

50 287 Magnesium

High Potential


high potential.

50 288 Mixed Metal

Oxide

An anode comprised of mixed

metal oxides.

50 289 Scrap Steel An anode comprised of scrap steel.

50 290 Zinc An anode comprised of the material

zinc.


Container: No

Attachments: Yes

Editor Tracking:







Attributes:


























of the terminal to which the subnetwork controller is associated.












regulatorytype (Short Integer) - The value indicating the regulatory status of the device feature.







locationdescription (Text[100]) - The textual description of the location of the anode.







barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. Coded Value Domain: Pipeline_ASTM_Manufacturer manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer.




material (Text[2]) - The predominant material used in the manufacture of the anode. Coded Value Domain: Pipeline_AnodeMaterialType quantity (Double[8,2]) - The number of anodes within the anode bed at the specific location. weight (Double[16,6]) - The measured mass of the anodes at the specific location. Coded Value Domain: Pipeline_CPAnodeWeight

notes (Text[2000]) - The non-structured information about the anode.









spatialaccuracy (Short Integer)- This short integer value provides an assessment of the spatial


geodatabase.




populated.



populated.



populated.












Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.











device is located.






Anode Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: CPAnode





Controller

N/A



Name

N/A












assetid assetid FACILITYID











quantity Quantity QUANTITY

weight Weight WEIGHT










gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A








Name

ENGROUTENAME




Name

CONTINROUTENAME





N/A CPTRACEWEIGHT



Name

N/A


Name

N/A


Name

N/A


Rectifier

The subtype feature layer Rectifier describes the device that generates the current for the

cathodic protection system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

51 0 Unknown An unknown is a rectifier whose

type is not known.

51 941 Rectifier A generic rectifier asset.

51 942 CP Rectifier-Ground

51 943 Other A rectifier which does not fit in the

other defined types.

51 944 Rectifier Bond

Container: No

Attachments: Yes

Editor Tracking:







Attributes:


























of the terminal to which the subnetwork controller is associated.



















serialnumber (Text [20])–The unique identifier labeled on the device.

locationdescription (Text[100]) - The textual description of the location of the anode.







barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. Coded Value Domain: Pipeline_ASTM_Manufacturer manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created.


manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification


amperage (Double[16,6]) - The measure of the electrical current generated by the rectifier. coolingmethod (Text[20]) - The system used to prevent the rectifier from overheating. yesmo (Short Integer) - The yes/no Boolean value indicating whether the rectifier includes an internal meter. Coded Value Domain: Yes_No

quantity (Long Integer) - The measurement of electric potential generated by the rectifier. Value is measured in volts.

notes (Text[2000]) - The non-structured information about the anode.









spatialaccuracy (Short Integer)- This short integer value provides an assessment of the spatial


geodatabase.




populated.



populated.




populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.











device is located.


Rectifier Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: CPRectifier





Controller

N/A



Name

N/A













serialnumber Serial Number SERIALNUMBER










amperage Amperage AMPERAGE

coolingmethod Cooling Method COOLINGMETHOD

internalmeter Internal Meter INTERNALMETER

rectifiertype Rectifier Type RECTIFIERTYPE

voltage Voltage VOLTAGE







gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A








Name

ENGROUTENAME




Name

CONTINROUTENAME





N/A CPTRACEWEIGHT



Name

N/A

pressure subnetwork name Pressure Subnetwork

Name

N/A


Name

N/A


Test Point

The subtype feature layer Test Point describes the read point location where the electric

potential can be measured for a cathodic protection system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

52 0 Unknown An unknown is a rectifier whose

type is not known.

52 981 Above Ground A rectifier located above the

ground surface.

52 982 Buried A rectifier located below the

ground surface.

52 983 On Post A rectifier located above the

ground surface and installed on a

post.

52 984 Pipeline

Marker

A rectifier located above the

ground surface and installed on a

pipeline marker.

52 985 Service Line A rectifier installed on a service

line.

Container: No

Attachments: Yes


Editor Tracking:







Attributes:













































locationdescription (Text[100]) - The textual description of the location of the test point. lifecyclestatus (Short Integer) - The text value indicating the life cycle state of the device. Coded






name (Text[20]) - The textual name used by utility staff to reference the test point.

quantity (Short Integer) - The number of wires associated with the test point.

note (Text[2000]) - The non-structured information about the test point.












geodatabase.




populated.



populated.



populated.











Referencing tools.





Referencing tools.




Referencing tools.




















Referencing tools.




Referencing tools.








tools.











device is located.






Test Point Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: CPTestPoint


assettype Asset Type TESTPOINTTYPE



Controller

N/A



Controller Name

N/A




Configuration

N/A










Description

LOCATIONDESCRIPTION






manufacturelotno Manufacture Lot No MANUFACTURELOTNO



name Test Point Name TESTPOINTNAME

quantity Wire Count WIRECOUNT








gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A


cp traceability CP Traceability N/A

cp override CP Override N/A







RouteID

ENGROUTEID


Name

ENGROUTENAME

engm Engineering

Measure

ENGM



Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM




N/A CPTRACEWEIGHT


Name

N/A


Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Pump

The subtype feature layer Pump describes the device that can mechanically increase the

pressure on the hazardous liquid to move it through the pipe system.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

18 0 Unknown An unknown is a Pump whose type

is not known.

18 401 Booster A booster pump provides additional

pressure to the flow of the

hazardous liquid

18 402 Primary A primary pump provides the

majority of the pressure to the flow

of the hazardous liquid

Container: No

Attachments: Yes

Editor Tracking:







Attributes:











isconnected (Short Integer) – The boolean true/false value indicating whether the device is






























This is used by the Facility Reporting tools to differentiate between Transmission, Offshore

Transmission, Gathering or Offshore Gathering pipe.





ownedby (Short Integer)—The name of the organization with ownership of the pump. In most




maintenance of the pump. In most instances, this will be the name of your organization. Coded

Value Domain: Asset_Manager






installation.






pressure.



the center of the inflow pump orifice.


through the center of the outflow pump orifice.


pump.



inflow flow pump orifice.


outflow flow pump orifice.




pump.


maxinletpressure (Double[16,5]) - The maximum pressure allowed at the inlet of the pump unit. maxoutletpressure (Double[16,5]) - The maximum pressure allowed to exit the pump unit.






barcode (Text [16])–The code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification


pressureunits (Short Integer) - The units of measurement used for the MAXINLETPRESSURE and MAXOUTLETPRESSURE attribute values. Coded Value Domain: Units_For_Pressure.

notes (Text[2000]) - The nonstructured information about the compressor.










geodatabase.




populated.




populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Pump Migration Table UPDM 2016 to UPDM 2019:

The UPDM 2016 model did not define Pump as a separate feature class. This is a new feature layer for UPDM 2018/UPDM 2019.


Regulator

The subtype feature layer Regulator describes the mechanical devices used in a pipe system for

the controlled reduction of pressure. Regulators are typically contained within a regulator

station or a town border station.


Relationships:

-Device__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

19 0 Unknown An unknown is a regulator whose type is

not known.

19 521 Regulator A generic regulator device.

19 522 Customer

Regulator

A regulator installed as part of a meter

set for a customer meter

Container: No

Attachments: Yes

Editor Tracking:







Attributes:


































updatedby (Text[255]) - The name of the system user responsible for the last modification to the device record in the geodatabase. This value is automatically populated by the Editor Tracking. globalid (GlobalID)- The system-wide unique identifier. This is the primary key value for relationships to child tables.







installdate (Date)–The date when the construction of the device feature was completed. inservicedate (Date) – The date when the device feature was put into production. ownedby (Short Integer)—The name of the organization with ownership of the regulator. In




maintenance of the regulator. In most instances, this will be the name of your organization.


assetid (Text[64]) - A layer-specific textual unique identifier. lifecyclestatus (Short Integer) - The text value indicating the life cycle state of the device. Coded


Coded Value Domain: Pipeline_RegulatorBodyType maopdesign (Double[16,5]) – The maximum allowable operating pressure as defined during design. Coded Value Domain: Pipeline_Pressure_Range



installation.





maopunits (Short Integer) – The unit of measure for defining the maximum allowable operating pressure. Coded Value Domain: Units_For_Pressure.


the center of the inflow regulator orifice.


through the center of the outflow regulator orifice.


regulator.



inflow flow regulator orifice.


outflow flow regulator orifice.




regulator.


maxinletpressure (Double[16,5]) - The manufacturer-specified maximum allowable incoming pressure. maxoutletpressure (Double[16,5]) - The manufacturer-specified maximum allowable outgoing pressure.






barcode (Text [16])–The ASTM F2897 code read from the bar code on the device. manufacturer (Text [2])–The organization who built the device. Coded Value Domain: Pipeline_ASTM_Manufacturer manufacturelotno (Long Integer)–The manufacturer lot number from which the device was created. manufacturedate (Date)–The date when the device was created by the manufacturer. manufacturecomponent (Text [2])–The manufacturer-specified, industry standard specification followed when the device feature was created. Coded Value Domain: Pipeline_ASTMMeterModel regulatorbodytype (Text[20]) - The style of the regulator. casingmaterial (Text[20]) - The material used for the construction of the regulator casing. Coded Value Domain: Pipeline_RegulatorCasingMaterial outletdiameter (Double[16,5]) - The edge to edge measured length of a straight line through the center of the regulator outlet. diaphragmdiameter (Double[16,5]) - The outer edge to outer edge nominal length of a straight line through the center of the regulator diaphragm. flowcapacity (Double[16,5]) – The volume based measurement of the flow of gas thru the regulator. flowcapacityunits (Short Integer) – The units of measure used for the volume of flow capacity. Coded Value Domain: Units_For_Volume









geodatabase.




populated.



populated.



populated.











Referencing tools.




Referencing tools.




Referencing tools.





















Referencing tools.




Referencing tools.







tools.












device is located.






Regulator Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Regulator





Controller

N/A


subnetworkcontrollernam

e

Subnetwork

Controller Name

N/A




Configuration

N/A










ownedby Owned By N/A









maxinletpressure Max Inlet Pressure MAXINLETPRESSURE


diameter2 Diameter2 N/A




maxoutletpressure Max Outet

Pressure

MAXOUTLETPRESSURE





No

MANUFACTURELOTNO



Model

MANUFACTUREMODEL

regulatorbodytype Regulator Body

Type

REGULATORBODYTYPE

casingmaterial Casing Material CASINGMATERIAL

outletdiameter Outlet Diameter OUTLETDIAMETER


diaphragmdiameter Diaphragm

Diameter

DIAPHRAGMNOMINALDIAMET

ER

flowcapacity Flow Capacity N/A

flowcapacityunits Flow Capacity

Units

N/A





Notes Comments N/A


gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A


cp traceability CP Traceability N/A

cpoverride CP Overrite N/A






RouteID

ENGROUTEID


Name

ENGROUTENAME


engm Engineering

Measure

ENGM


RouteID

CONTINROUTEID


Name

CONTINROUTENAME

continm Continuous

Measure

CONTINM

refmethod Reference

Method

REFMETHOD


Location

REFLOCATION


N/A REGULATORSTATION_globalid

N/A TOWNBORDERSTATION_globali

d

N/A RURALTAP_globalid


Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Subnetwork Name

N/A


Junctions Definition: The UPDMJunction feature class models those components of the pipe system that do not

have the ability to impede, filter, or measure the flow of the liquid or gas moving through the pipe

system.

UPDMJunction features can be either stand-alone features on the map or contained in gas assemblies.

For example, a coupling can be a single feature on the map, or it can be contained in an assembly such

as a compressor station or pump station.


The following are the general types of associations for junctions:

• A junction can be connected to the following:

o Line at the end, beginning, or middle vertex—For example, a plastic end cap can

connect to a Plastic PE line.

o Device—For example, a flange can be connected to a valve with a connectivity

association.

o Junction—For example, a flange can be connected to a coupling with a connectivity

association.

• A junction can be contained by the following:

o Assembly—For example, a pump can be contained by a pump station.

o Structure boundary—For example, a compressor can be contained in a station

structure or vault.

Junction

Bond Junction

Connection Point

Cooling System

Coupon Coupling Dehydration Equipment

Drip Electro Stop

End Cap Expansion Joint

Flange Line Heater

Plastic Fusion

Reducer Saddle Odorizer Screw Tank

Elbow

Tee

Transition Weld



This is the schema for the Junction feature class.












designtype Short Integer

installdate Date

inservicedate Date

assetid Text(64)



lifecyclestatus Short Integer Utility Network Attribute

maopdesign Double(16,5) Utility Network Attribute

maoptest Double(16,5) Utility Network Attribute

maoprecord Double(16,5) Utility Network Attribute


height Double(16,5)

length Double(16,5)


bacode Text(16)


manufacturerlotno Text(10)



material Text(2)

resistanceindicator Short Integer

liningtype Text(50)


capacity Double(16,5)

criticalindicator Short Integer

flowcapacity Double(16,5)

notes Text(2000)




wallthicknessunits Short Integer

flowcapacityunits Short Integer

heightunits Short Integer

heatingcapacityunits Short Integer



capacityunits Short Integer

installperson Text(50)

installmethod Text(30)

rooftype Text(50)

heatingfuel Text(20)

heatingcapacity Double(16,5)

odoranttype Text(30)

percentgraph Double(16,5)

bondjunctiontype Text(35)

gpsx Double(16,8)

gpsy Double(16,8)

gpsz Double(16,8)

legacyid Text(38)



















cptraceability Short Integer



wallthickness2 Double(16,5)

diameter2 Double(16,5)






Coupling

The subtype feature layer Coupling describes those inline assets used for connecting two pipe

segments of the same diameter and material.

GeometryType: Point with z- and m-values— enabled

Relationships:

-Junction__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

1 0 Unknown An unknown is a coupling whose type

is not known.

1 1 Plastic Coupling A coupling whose base material is

plastic.

1 2 Metal Coupling A coupling whose base material is

metal.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:


assetgroup (Long Integer) —The geodatabase subtype field. The subtype field models general


assettype (Short Integer) —The discriminator field with a subtype-specific coded domain.

associationstatus (Short Integer)—Indicates the type of utility network association with which

the junction feature participates.

Coded Value Domain: Pipeline_AssociationStatus

isconnected (Short Integer)—The true/false Boolean value indicating whether the junction is

connected to a subnetwork controller source.


creationdate (Date)—The date and time the junction record was originally created in the


creator (Text[255])—The name of the system user who originally created the junction record in


lastupdate (Date)—The date and time the junction record was last modified in the geodatabase.



the junction record in the geodatabase. This value is automatically populated by the Editor

Tracking.



regulatorytype (Short Integer)—The value indicating the regulatory status of the junction


Transmission, Offshore Transmission, Gathering, and Offshore Gathering.


installdate (Date)—The date the construction of the junction feature was completed.

inservicedate (Date)—The date the junction feature was put into production.


assetid (Text[64])—The layer-specific textual unique identifier.

ownedby (Short Integer)—The name of the organization with ownership of the junction. In most




maintenance of the junction. In most instances, this will be the name of your organization.


lifecyclestatus (Short Integer)—The text value indicating the life cycle state of the junction.

Coded Value Domain: Pipeline_LifeCycle_Status


design.



installation.



device feature is currently operating.



pressure.



through the inflow of the fitting orifice.

Coded Value Domains: Pipeline_Fitting_Diameter


through the center of the outflow fitting orifice.


diameterunits (Short Integer)—The unit of measure used to define the diameter of the fitting

feature.



length (Double[16,5]) - The field measured longitudinal length of the fitting. The purpose of this


lengthunits (Short Integer)—The unit of measure used to define the inline length of the junction

feature.



inflow flow fitting orifice.


outflow flow fitting orifice.






manufacturer (Text[2])—The organization that built the junction feature.


manufacturelotno (Long Integer)—The manufacturer lot number from which the junction

feature was created.

manufacturedate (Date)—The date the junction feature was created by the manufacturer.


followed when the junction feature was created.

Coded Value Domain: Pipeline_ASTMCoupling_Manufacture_Component

material (Text[2])—The primary material used in the manufacture of the junction feature. Coded

Value Domain: Pipeline_ASTM_Component_Material



geodatabase.





populated.



populated.



populated.

bondedinsulated (Short Integer) – A Boolean indicator of whether the fitting acts as a conductive

fitting (bonded) or an non-conductive fitting (insulated) in a cathodic protection system. Coded

Valve Domain: Bonded_Insulated.

cptraceability (Short Integer) – A Boolean indicator of whether the normal function of the fitting


cpoverride (Short Integer)- A Boolean indicator of a temporary state of whether the fitting is



management system information for this junction feature.


under which the junction feature was installed.


number under which a work order was generated to install the junction feature.





organizations wanting to maintain the junction features as event records with the ArcGIS













location on a route. This attribute is only used by organizations wanting to maintain the junction




located. This attribute is only used by organizations wanting to maintain the junction features as



engroutename (Text[100])—The unique name of the engineering network route where the

event is located. This attribute is only used by organizations wanting to maintain the junction




junction is located. This attribute is only used by organizations wanting to maintain the junction





wanting to maintain the junction features as event records with the ArcGIS Pipeline Referencing

tools.




tools.


value isautomatically created and maintained by the ArcGIS Pipeline Referencing tools.




This attribute is only used by organizations wanting to maintain the junction features as event


Referencing tools.



maintain the junction features as event records with the ArcGIS Pipeline Referencing tools. The





systemsubnetworkname (Text[2000])—The unique name given to the system tier subnetwork

feature with which the junction feature is associated.

pressuresubnetworkname (Text[2000])—The unique name given to the pressure tier subnetwork


isolationsubnetworkname(Text[2000])—The unique name given to the isolation tier subnetwork


cpsubnetworkname (Text[2000])—The unique name given to the cathodic protection tier

subnetwork feature with which the junction feature is associated.


Coupling Migration Table UPDM 2016 to UPDM 2019:


P_NonControllableFitting

assetgroup Asset Group SubtypeCD












ownedby Owner OWNER







length Length N/A














material Material Material


gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A

bondedindicator Bonded Indicator N/A


















Name

N/A


Name

N/A

isolationsubnework name Isolation Subnetwork

Name

N/A


N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE

installperson INSTALLPERSON

installmethod INSTALLMETHOD


Elbow

The subtype feature layer Elbow describes those inline assets used for connecting two pipe

segments with an offset angle of the same diameter and material.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

2 0 Unknown An unknown is an elbow whose type

is not known.

2 41 Metal Elbow An elbow whose base material is

metal.

2 42 Plastic Elbow An elbow whose base material is

plastic.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:




assettype (Short Integer)—The discriminator field with a subtype-specific coded domain.















Tracking.




















design.



installation.



junction feature is currently operating.



pressure.





diameter2 (Double[16,5])—The generalized edge-to-edge measured length of a straight line




feature.






feature.






wallthicknessunits (Short Integer)—The unit of measure used to define the thickness of the

outer wall of the fitting feature.






barcode (Text [16])—The ASTM F2897-15 code read from the bar code on the device.








Coded Value Domain: Pipeline_ASTM_Elbow_Manufacture_Component


Value Domain: Pipeline_ASTM_ Material



geodatabase.





populated.



populated.



populated.

















































tools.




tools.








Referencing tools.

















Elbow Migration Table UPDM 2016 to UPDM 2019:
















ownedby Owner OWNER







length Length N/A







wallthickness2 Wall Thockness 2 N/A








N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE

INSTALLPERSON INSTALLPERSON

INSTALLMETHOD INSTALLMETHOD


gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A

bondedinsulator Bonded Insulator N/A

cptraceability CP Traceabilty N/A












Name

ENGROUTENAME




Name

CONTINROUTENAME


N/A GASTRACEWEIGHT


Name

N/A


Name

N/A


Name

N/A


Name

N/A


End Cap

The subtype feature layer End Cap describes inline assets used for sealing the end of a pipe

segment.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

3 0 Unknown An unknown is an end cap whose type

is not known.

3 81 Metal End Cap An end cap whose base material is

metal.

3 82 Plastic End Cap An end cap whose base material is

plastic.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.







installdate (Date)–The date the construction of the junction feature was completed.



assetid (Text[64])—The layer-specific textual unique identifier.










design.



installation.






pressure.






feature.











feature.




rotation (Short Integer)—This value defines the angular degrees the point symbol should be




barcode (Text[16])–The ASTM F2897-15 code read from the bar code on the device.








Coded Value Domain: Pipeline_ASTM_End_Cap_Component


Value Domain: Pipeline_ASTM _Material



geodatabase.












populated.



populated.



populated.










































tools.




tools.








Referencing tools.








systemsubnetworkname (Text[2000]) The unique name given to the system tier subnetwork









End Cap Migration Table UPDM 2016 to UPDM 2019:
















ownedby Owner OWNER







length Length N/A















cpoverride Cp Override N/A


gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A





N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE


Installperson INSTALLPERSON







Name

ENGROUTENAME




Name

CONTINROUTENAME



Name

N/A


Name

N/A


Name

N/A



Expansion Joint

The subtype feature layer Expansion Joint describes inline assets used for connecting pipe

segments and to safely absorb pipe system expansion, contraction, and vibration.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

4 0 Unknown An unknown is an expansion

joint whose type is not known.

4 121 Expansion Joint A generic classification of

expansion joints.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.




















design.



installation.






pressure.









feature.













feature.









manufacturelotno (Long Integer) The manufacturer lot number from which the junction feature

was created.








geodatabase.












populated.



populated.



populated.







legacyid (Text[38])—A unique ID used to relate this record to its predecessor record from a

previous mapping or asset system. This provides continuity between the old system and the























engroutename (Text[100]) –The unique name of the engineering network route where the event

is located. This attribute is only used by organizations wanting to maintain the junction features

as event records with the ArcGIS Pipeline Referencing tools. The value is automatically









tools.



wanting to maintain the features as event records with the ArcGIS Pipeline Referencing tools.








Referencing tools.

















Expansion Joint Migration Table UPDM 2016 to UPDM 2019:
















ownedby Owner OWNER







length Length N/A







wallthicknessunits Wall Thickness Units N/A












gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A















N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE





isolationsubnework name Isolation Subnetwork Name N/A



Flange

The subtype feature layer Flange describes inline assets used for connecting pipe segments. A

flange has an internal or external rim to provide additional strength.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

5 0 Unknown An unknown is a flange whose type is

not known.

5 161 Metal Flange A flange whose primary material is

metallic.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.




















design.



installation.






pressure.









feature.













feature.


















geodatabase.




fitting (bonded) or an non-conductive fitting (insulated) in a cathodic protection system.

Coded Valve Domain: Bonded_Insulated.


is traceable in a cathodic protection zone.

Coded Value Domain: CP_Traceability


traceable in a cathodic protection zone.

Coded Valve Domain: CP_Traceability



populated.



populated.



populated.



















Referencing tools.

















Flange Migration Table UPDM 2016 to UPDM 2019:

















ownedby Owner OWNER










length Length N/A











cptraceability Cp Traceability N/A

cp override CP Override N/A

gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A











Name

ENGROUTENAME




Name

CONTINROUTENAME


N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE




Name

N/A


Name

N/A


Name

N/A



Reducer

The subtype feature layer Reducer describes inline assets used for connecting pipe segments of

different diameter.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

6 0 Unknown An unknown is a reducer whose type

is not known.

6 201 Metal reducer A reducer whose primary material is

metallic.

6 202 Plastic Reducer A reducer whose primary material is

plastic.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.







designtype (Short Integer) - The multidimension size of the junction.

Coded Value Domain: Pipeline_ReducerFittingSize














design.



installation.






pressure.









feature.













feature.














Coded Value Domain: Pipeline_ASTM_Reducer_Componentl

material (Text[2])—The primary material used in the manufacture of the junction feature.




pressure.



feature.




geodatabase.













populated.



populated.



populated.









tools.










Referencing tools.

















Reducer Migration Table UPDM 2016 to UPDM 2019:













designtype Fittings Size FITTINGSIZE




ownedby Owner OWNER













length Length N/A













gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A















N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE





Name

N/A


Name

N/A



Tee

The subtype feature layer Tee describes inline assets used for connecting three or four pipe

segments.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

7 0 Unknown An unknown is a tee whose type is

not known.

7 241 Metal 3-Way A tee whose primary material is

metal and connects 3 pipe

segments.

7 242 Metal 4-Way A tee whose primary material is

metal and connects 4 pipe

segments.

7 243 Plastic 3-Way A tee whose primary material is

plastic and connects 3 pipe

segments.

7 244 Plastic 4-Way A tee whose primary material is

plastic and connects 4 pipe

segments.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.







designtype (Short Integer)—The multidimension measurements of the junction feature.














design.



installation.






pressure.



through the center of the inflow of the junction orifice.



through the center of the outflow of the junction orifice.


diameterunits (Short Integer)—The unit of measure used to define the diameter of the junction

feature.










length (Double[16,5])—The measured inline length of the junction feature. This value is to be

used for load flow analysis.


feature.














Coded Value Domain: Pipeline_ASTM_Tee_Manufacture_Component















geodatabase.




populated.



populated.



populated.










































tools.




tools.








Referencing tools.

















Tee Migration Table UPDM 2016 to UPDM 2019:













designtype Fitting Size FITTINGSIZE

N/A Insulating Device INSULATEDINDICATOR




ownedby Owner OWNER














length Length N/A










gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A

bonded insulator Bonded Insulator N/A

















N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE

installperson Install Person INSTALLPERSON

installmethod Install Method INSTALLMETHOD


Name

N/A


Name

N/A


Name

N/A



Transition

The subtype feature layer Transition describes inline assets used for connecting pipe segments

of different materials.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

8 0 Unknown An unknown is a transition whose

type is not known.

8 281 Transition A generic transition fitting.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.







designtype (Short Integer)—The multidimension measurements of the junction feature.














design.



installation.






pressure.









feature.













feature.














Coded Value Domain: Pipeline_ASTM_Transition_Manufacture_Component













geodatabase.




populated.



populated.



populated.










































tools.




tools.








Referencing tools.

















Transition Migration Table UPDM 2016 to UPDM 2019:













designtype Fitting Size STYLE






ownedby Owner OWNER













length Length N/A












gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A















N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE




Name

N/A


Name

N/A


Name

N/A



Weld

The subtype feature layer Weld describes a method for connecting two pipe segments of

metallic material.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

9 0 Unknown An unknown is a weld whose type is

not known.

9 321 Weld A generic weld.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:








isconnected (Short Integer) The true/false Boolean value indicating whether the junction is



creationdate (Date) The date and time the junction record was originally created in the








Tracking.













design.



installation.






pressure.






feature.






installperson (Text[50])—The name of the person who welded the two segments of pipe

together.

installmethod (Text[30])—The method of welding used to connect the two pipe segments.













geodatabase.




populated.



populated.



populated.



















Referencing tools.

















Weld Migration Table UPDM 2016 to UPDM 2019:
















N/A Owner OWNER

N/A Asset ID FACILITYID










N/A Barcode BARCODE

N/A Manufacturer MANUFACTURER

N/A Manufacture Lot# MANUFACTURERLOTNO

N/A Manufacture Date MANUFACTUREDATE

N/A Manufacture Model MANUFACTUREMODEL







gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A











Name

ENGROUTENAME




Name

CONTINROUTENAME


N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE


Name

N/A


Name

N/A


Name

N/A



Screw

The subtype feature layer Screw describes an inline asset with screw threads for connecting two

pipe segments of metallic material.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

10 0 Unknown An unknown is a screw whose type is

not known.

10 361 Screw A generic screw fitting.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.













design.



installation.






pressure.









feature.













feature.






















together.










tools.




tools.







Referencing tools.










geodatabase.




populated.




populated.



populated.

assetunitcode (Text[38])–The foreign key value used to link this record to the utilities asset


workorderid (Text[38])–The work management system value used to identify the task number


projectnumber (Text[38])–The work management system value used to identify the project


legacyid (Text[38])–A unique identifier used to relate this record to its predecessor record from












Screw Migration Table UPDM 2016 to UPDM 2019:




























length Length N/A








ownedby Owner OWNER










Name

ENGROUTENAME





Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A





N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE




Name

N/A


Name

N/A


Name

N/A



Electro Stop

The subtype feature layer Electro Stop describes an inline asset that acts as an insulator of

electric current.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

11 0 Unknown An unknown is an electro stop whose

type is not known.

11 401 Electro Stop A generic electro stop fitting.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:







Coded Value Domain: Pipeline_AssocationStatus












Tracking.













design.



installation.






pressure.









feature.













feature.






















together.













tools.







Referencing tools.










geodatabase.




populated.




populated.



populated.



















Electro Stop Migration Table UPDM 2016 to UPDM 2019:



























wallthicknessunits Wallthicknessunits N/A

length Length N/A








ownedby Owner OWNER










Name

ENGROUTENAME




Name

CONTINROUTENAME




gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A





N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE

Installperson Install Person INSTALLPERSON



Name

N/A


Name

N/A


Name

N/A



Plastic Fusion

The subtype feature layer Plastic Fusion describes the location where two plastic pipes and/or

components are connected with an electro fusion device.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

12 0 Unknown An unknown is a plastic fusion whose

type is not known.

12 401 Plastic Fusion A generic plastic fusion fitting.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:







Coded Value Domain: Pipeline_AssocationStatus












Tracking.













design.



installation.






pressure.









feature.







installperson (Text[50])—The name of the person who fused the two segments of pipe together.


installmethod (Text[30])—The method of fusion used to connect the two pipe segments.










































tools.




tools.







Referencing tools.










geodatabase.





populated.

gpsy (Double[16,8])—The latitudinal coordinate of the feature when it was originally includedd


populated.



populated.



















Plastic Fusion Migration Table UPDM 2016 to UPDM 2019:
























ownedby Owner OWNER


















gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A





N/A GASTRACEWEIGHT


N/A BONDEDINDICATOR

N/A STYLE


Name

N/A


Name

N/A


Name

N/A



Saddle

The subtype feature layer Saddle describes junction assets used for connecting pipe segments.

Saddles perform a variety of purposes, such as tapping and structural strengthening.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

13 0 Unknown An unknown is a saddle whose

type is not known.

13 481 Metal Saddle A saddle whose primary material is

metallic.

13 482 Plastic Saddle A saddle whose primary material is

plastic.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:




assettype (Short Integer)—The discriminator field with a specific coded domain.




isconnected (Short Integer) The true/false Boolean value indicating whether the junction is











Tracking.













design.



installation.






pressure.









feature.




wallthickness2 (Double[16,5])—The manufacturer defined thickness of the exterior wall of the









feature.










Coded Value Domain: Pipeline_ASTMSaddleModel














fittingsize (Text[20])—The multidimension size of the junction.











installperson (Text[50])—The name of the person who fused the two segments of pipe together.

installmethod (Text[30])—The method of fusion used to connect the two pipe segments.

































tools.




tools.







Referencing tools.










geodatabase.





populated.



populated.



populated.



















Saddle Migration Table UPDM 2016 to UPDM 2019:




























length Length N/A








ownedby Owner OWNER






fittingsize Fitting Size STYLE






Name

ENGROUTENAME





Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A





N/A GASTRACEWEIGHT

N/A BONDEDINDICATOR

N/A STYLE




Name

N/A


Name

N/A


Name

N/A



Tank

The subtype feature layer Tank describes the facility in a transmission pipeline used as a storage

unit to relieve surges in flow or to receive and store liquid or gas for reinjection and continued

transportation through the pipeline.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

14 0 Unknown An unknown is a Tank whose type is

not known.

14 521 Tank A generic type of Tank.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:


assetgroup (Long Integer) – The geodatabase subtype field. The subtype field models general


assettype (Short Integer) – The discriminator field with a subtype specific coded domain.

associationstatus (Short Integer) – The indicator of the type of utility network association to

which the junction feature participates.


isconnected (Short Integer) – The Boolean true/false indicator of whether the junction is


Coded Value Domain: Pipeline_IsConnected.

creationdate (Date) – The date and time the junction record was originally created in the


creator (Text[255]) – The name of the system user who originally created the junction record in


lastupdate (Date) – The date and time the junction record was last modified in the geodatabase.


updatedby (Text[255]) – The name of the system user responsible for the last modification to


Tracking.

globalid (GlobalID) – The systemwide unique identifier. This is the primary key value for


lifecyclestatus (Short Integer) – The text value indicating the life cycle state of the junction.


installdate (Date) – The date when the construction of the junction feature was completed.

inservicedate (Date) – The date when the junction feature was put into production.


regulatorytype (Short Integer) – The value indicating the regulatory status of the junction


Transmission, Offshore Transmission, Gathering or Offshore Gathering.



design.



installation.






pressure.


diameter (Double[16,5]) – The generalized edge to edge measured length of a straight line

through the center of the tank.

Coded Value Domains: Pipeline_Fitting_Diameter.

diameterunits (Short Integer) - The unit of measure used to define the diameters of the junction

feature.


height (Double[16,5]) – The vertical distance from the base of the tank to the top of the roof of

the tank.

heightunits (Short Integer) – The unit of measure of the vertical distance of the tank.

manufacturer (Text [2]) – The organization who built the tank feature.

Coded Value Domain: Pipeline_Tank_Manufacturer

manufacturerlotno (Long Integer) – The manufacturer lot number from which the tank feature

was created.

manufacturedate (Date) – The date when the tank feature was created by the manufacturer.


manufacturecomponent (Text [2]) – The manufacturer-specified, industry standard specification

followed when the tank feature was created.

Coded Value Domain: Pipeline_Tank_Model

rotation (Short Integer) – This value defines the angular degrees that the point symbol should be




assetid (Text[64]) – A layer-specific textual unique identifier of the Tank unit.

capacity (Double[16,5]) – The maximum volume of gas or liquid that the tank can store.

capacityunits (Short Integer) – The unit of measure of the volume of the tank.

flowcapacity (Double[16,5]) – The maximum flow rate at which the gas or liquid can enter or

depart the tank.

flowcapacityunits (Short Integer) – The unit of measure of the flow rate.

rooftype (Text[50]) – The type of structure used to cover the top of the tank.

liningtype (Text[50]) – The type of lining used to cover the interior of the tank to prevent

leakage or corrosion.







locationdescription (Text [50]) – The textual description of the location where the tank is

located.











eventid (Text [38]) – The unique ID for each event record. This attribute is only used by




fromdate (Date) – The date the event became active on the route. This attribute is only used by




todate (Date) – The date the event was retired from the route. This attribute is only used by




locationerror(Text [100]) – The resultant message from the process of defining the event’s




engrouteid (Text [38]) –The unique ID of the engineering network route where the event is




engroutename (Text [100]) –The unique ID of the engineering network route where the event is




engm(Double[16,5]) –The measure location along the engineering network route where the





continrouteid (Text[38]) – The continuous network Route ID that is automatically created and



continroutename (Text[100]) – The continuous network name that is automatically created and





refmethod (Short Integer) – The method of referencing the offset feature. This can be




Referencing tools.

reflocation (Text [50]) – The location of the offsetting feature. This can be Coordinates,




refoffset(Text [50]) – The offset measure. This attribute is only used by organizations wanting to



spatialaccuracy (Short Integer) – This short integer value provides and assessment of the spatial


geodatabase.


gpsx(Double[16,8]) – The longitudinal coordinate of the feature when it was originally inserted

into the geodatabase. If using attribute rules capability, this value can be automatically

populated.

gpsy (Double[16,8]) – The latitudinal coordinate of the feature when it was originally inserted


populated.

gpsz (Double[16,8]) – The elevation coordinate of the feature when it was originally inserted


populated.








legacyid (Text [38])–A unique identifier used to relate this record to its predecessor record from



systemsubnetworkname (Text[2000]) – The unique name given to the system tier subnetwork

feature to which the junction feature is associated.

pressuresubnetworkname (Text[2000]) - The unique name given to the pressure tier subnetwork


isolationsubnetworkname(Text[2000]) - The unique name given to the isolation tier subnetwork


cpsubnetworkname (Text[2000]) - The unique name given to the cathodic protection tier

subnetwork feature to which the junction feature is associated.


Tank Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Tank





















height Height Height

heightunits Height Units Height Units



manufacturerlotno Manufacturer Lot No N/A



ownedby Owner OWNER

assetid Asset ID TANKNUMBER

capacity Capacity NOMINALCAPACITY

capacityunits Capacity Units N/A

flowcapacity Flow Capacity MAXPUMPINGRATE


rooftype Roof Type ROOFTYPE

liningtype Lining Type LININGTYPE










Name

ENGROUTENAME





Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A






Name

N/A


Name

N/A


Name

N/A



Line Heater

The subtype feature layer Line Heater describes the component in a pipeline that has the ability

to elevate the temperature of liquid/gas to prevent hydrate formation.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

15 0 Unknown An unknown is a Line Heater whose

type is not known.

15 561 Line Heater A generic line heater.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.













design.



installation.






pressure.



through the center of the junction orifice.

diameterunits (Short Integer) – The unit of measure used to define the diameters of the junction

feature.


length (Double [16,5]) – The measured inline length of the junction feature. This value is to be


lengthunits (Short Integer) – The unit of measurement used to define the inline length of the

junction feature.

Coded Value Domain: Units_For_Length.

manufacturer (Text [2]) – The organization who built the Line Heater feature.

Coded Value Domain: Pipeline_Line_Heater_Manufacturer

manufacturerlotno (Long Integer) – The manufacturer lot number from which the Line Heater



manufacturedate (Date) – The date when the Line Heater feature was created by the

manufacturer.


followed when the Line Heater feature was created.

Coded Value Domain: Pipeline_LineHeaterModel





assetid (Text[64]) – A layer-specific textual unique identifier.

heatingfuel (Text[20]) – The fuel used in the line heater to generate heat.

heatingcapacity (Double[16,5]) – The manufacturer rated maximum capacity to heat that the

line heater is capable of generating.

heatingcapacityunits (Short Integer) – The unit of measure of the heating capacity.

Coded Value Domain: Pipeline_Units_For_Heat























Referencing tools.








spatialaccuracy (Short Integer) – This short integer value provides an assessment of the spatial


geodatabase.




populated.



populated.



populated.

assetunitcode (Text [38]) – The foreign key value used to link this record to the utilities asset


workorderid (Text [38]) – The work management system value used to identify the task number



projectnumber (Text [38]) – The work management system value used to identify the project


legacyid (Text [38]) – A unique identifier used to relate this record to its predecessor record





pressuresubnetworkname (Text[2000]) – The unique name given to the pressure tier


isolationsubnetworkname(Text[2000]) – The unique name given to the isolation tier subnetwork


cpsubnetworkname (Text[2000]) – The unique name given to the cathodic protection tier



Line Heater Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_LineHeater





















length Length N/A




manufacturerlotno Manufacture Lot No N/A




ownedby Owner OWNER


heatingfuel Heating Fuel HEATINGFUEL

heatingcapacity Heating Capacity HEATINGCAPACITY

heatingcapacityunits Heating Capacity Units HEATINGCAPACITYUNITS









Name

ENGROUTENAME




Name

CONTINROUTENAME




gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A






Name

N/A


Name

N/A


Name

N/A



Cooling System

The subtype feature layer Cooling System describes the component in a pipeline that has the

ability to reduce the temperature of the liquid/gas commodity.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

16 0 Unknown An unknown is a Cooling System


16 601 Cooling System A generic Cooling System.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.













design.



installation.






pressure.





feature.





junction feature.


manufacturer (Text [2]) – The organization who built the Cooling System feature.

manufacturerlotno (Long Integer) – The manufacturer lot number from which the Cooling

System feature was created.

manufacturedate (Date) – The date when the Cooling System feature was created by the

manufacturer.



followed when the Cooling System feature was created.

Coded Value Domain: Pipeline_CoolingSysModel















feature.





junction feature.


















Referencing tools.










geodatabase.




populated.



populated.



populated.




Cooling System Migration Table UPDM 2016 to UPDM 2019:

The UPDM 2016 model did not define Cooling System as a separate feature class. This is a new feature layer for UPDM 2019.


Odorizer

The subtype feature layer Odorizer describes the component for injecting odorant into the gas

pipe system. US DOT regulation CFR 49 part 192.625 requires that gas pipelines contain enough

odorant so that the gas is readily detectable by a person with a normal sense of smell.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

17 0 Unknown An unknown is a Odorizer whose

type is not known.

17 25 Absorption

Bypass

Uses a side channel of pipe to inject

the odorant into the gas stream.

17 26 Injection Pump Injects liquid odorant into the gas

stream.

17 27 Pulse Uses a side tank to mix odorant

vapors with natural gas and inject

into gas stream.

17 28 Rural Tap

Odorizer

Odorizer that is part of a rural tap

assembly.

17 29 Wick A material which extends from the

container of odorant. It draws the

odorant from the container into the

gas stream.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.













design.



installation.






pressure.


manufacturer (Text [2]) – The organization who built the Odorizer feature.

Coded Value Domain: Pipeline_OdorizerManufacturer

manufacturerlotno (Long Integer) – The manufacturer lot number from which the Odorizer


manufacturedate (Date) – The date when the Odorizer feature was created by the

manufacturer.


followed when the Odorizer feature was created.

Coded Value Manufacturer: Pipeline_OdorizerModel

capacity (Double[16,5]) – The storage volume available to store odorant.

capacityunits (Short Integer) – The unit of measure for defining the volume of the odorant tank.


odoranttype (Text[30]) – The type of chemical used to provide odor to the gas stream.





feature.





junction feature.

























































Referencing tools.











geodatabase.




populated.



populated.



populated.













Odorizer Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Odorizer

















maopunits MAOP Units MAOPUNITOFMEASURE



length Length N/A








assetid Asset ID N/A

capacity Capacity STORAGECAPACITY


odoranttype Odorant Type ODORANTTYPE






Name

ENGROUTENAME


continrouteid Continuous Route ID continrouteid


Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A







Name

N/A


Name

N/A


Name

N/A



Coupon

The subtype feature layer Coupon describes the location where a sample of the pipe is cut from

the metal pipe to determine the extent of internal corrosion.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

18 0 Unknown An unknown is a Coupon whose

type is not known.

18 681 Coupon A generic Coupon.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.



manufacturer (Text [2]) – The organization of the extracted pipe feature.

manufacturerlotno (Long Integer) – The manufacturer lot number of the extracted pipe feature

was created.

manufacturedate (Date) – The date when the extracted pipe feature was created by the

manufacturer.



of the pipe feature created.

percentgraph (Double[16,5]) – The percent of graphitization.




feature.





junction feature.


wallthickness (Double[16,5]) – The thickness of the pipe wall as measured from the extracted

coupon.

wallthicknessunit (Short Integer) – The unit of measure used to define the thickness of the pipe

wall.

Coded Value Domain: UnitsForDiameter






















Referencing tools.










geodatabase.




populated.



populated.



populated.




Coupon Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Coupon














percentgraph Percent Graph PERCENTGRAPH



length Length N/A



wallthicknessunit Wall Thickness Unit N/A












Name

ENGROUTENAME




Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A


Name

N/A


Name

N/A


Name

N/A



Dehydration Equipment

The subtype feature layer Dehydration Equipment describes the component that is responsible

for inhibiting the formation of hydrates in the pipeline.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

19 0 Unknown An unknown is a Dehydration

Equipment whose type is not

known.

19 721 Glycol

Dehydration

A liquid which is injected into the

gas stream to remove water.

19 722 Methanol

Dehydration

A liquid which is injected into the

gas stream to remove water.

19 723 Solid

Absorption

The use of solid materials to extract

hydrates from the gas stream.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.













design.



installation.






pressure.





feature.





junction feature.


wallthickness (Double[16,5]) – The thickness of the pipe wall as measured from the extracted

coupon.

wallthicknessunit (Short Integer) – The unit of measure used to define the thickness of the pipe

wall.



manufacturer (Text [2]) – The organization responsible for the manufacture of the Dehydration

Equipment.

manufacturerlotno (Long Integer) – The manufacturer lot number of the Dehydration

Equipment.

manufacturedate (Date) – The date when the Dehydration Equipment was created by the

manufacturer.


of the Dehydration Equipment.

ownedby (Short Integer)—The name of the organization with ownership of the dehydration

equipment. In most instances, this will be the name of your organization.



maintenance of the dehydration equipment. In most instances, this will be the name of your

organization.

























Referencing tools.










geodatabase.




populated.



populated.



populated.






Dehydration Equipment Migration Table UPDM 2016 to UPDM 2019:


P_DehydrationEquipment











installdate Installation Date INSTALLATIONDATE

inservicedate Inservice Date N/A





maopunit MAOP Unit N/A


diameter units Diameter Units N/A

length Length N/A

lengthunits LengthUnits N/A








ownedby Owner OWNER




cptraceability CP traceability N/A







Name

ENGROUTENAME




Name

CONTINROUTENAME



gpsx GPS X GPSX


gpsy GPS Y GPSY

gpsz GPS Z N/A






Name

N/A


Name

N/A


Name

N/A



Drip

The subtype feature layer Drip describes the component in a gas pipeline that helps to separate

and collect water that has accumulated in the pipeline.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

20 0 Unknown An unknown is a Drip whose type is

not known.

20 761 Drip A generic Drip component.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.













design.



installation.






pressure.





feature.





junction feature.


manufacturer (Text [2]) – The organization responsible for the manufacture of the Drip.

manufacturerlotno (Long Integer) – The manufacturer lot number of the Drip.

manufacturedate (Date) – The date when the Drip was created by the manufacturer.



of the Drip.

locationdescription (Text([100]) A description of the location of the Drip.

ownedby (Short Integer)—The name of the organization with ownership of the drip. In most




maintenance of the drip. In most instances, this will be the name of your organization.


capacity (Double[16,5]) – The total volume of the drip vessel.

capacityunit (Short Integer) – The unit of measure used for the capacity of the drip vessel.
























Referencing tools.










geodatabase.




populated.



populated.



populated.








Drip Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Drip

















maopunit MAOP Unit N/A

Diameter Diameter N/A

Diameter Units Diameter Units N/A

Length Length N/A

Length Units Length Units N/A







ownedby Owner OWNER

capacity Capacity VESSELVOLUME












Name

ENGROUTENAME




Name

CONTINROUTENAME



gpsx GPS X GPSX


gpsy GPS Y GPSY

gpsz GPS Z N/A






Name

N/A


Name

N/A


Name

N/A


N/A INSPECTOR

N/A LASTPUMPDATE


Connection Point

The subtype feature layer Connection Point describes the location along a pipe segment where a

structure junction connects to a non-endpoint location along the pipe via a structural

attachment.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

21 0 Unknown An unknown is a Connection Point


21 801 Connection

Point

A generic Connection Point

component.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.










Connection Point Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Connection Point as a separate feature class. This is a new feature layer for UPDM 2019.


Wire Junction

The subtype feature layer Wire Junction describes the component where multiple wires meet

and interconnect.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

50 0 Unknown An unknown is a Wire Junction


50 901 Bond Junction Bond junction connects a wire to

a metallic asset

50 902 Test Lead Test Lead is a wire junction at a

test point

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.












manufacturer (Text [2]) – The organization responsible for the manufacture of the Bond

Junction.

manufacturerlotno (Long Integer) – The manufacturer lot number of the Bond Junction.

manufacturedate (Date) – The date when the Bond Junction was created by the manufacturer.


of the Bond Junction.

locationdescription (Text([100]) A description of the location of the Bond Junction.

criticalindicator (Short Integer) – The yes/no Boolean value indicating whether the bond junction

is considered critical.

























Referencing tools.










geodatabase.




populated.



populated.



populated.






Bond Junction Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_BondJunction


assettype Asset Type BONDJUNCTIONTYPE

















N/A Resistance Indicator RESISTANCEINDICATOR













Name

ENGROUTENAME




Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A






Name

N/A


Name

N/A



Name

N/A


N/A CPTRACEWEIGHT

N/A LASTPUMPDATE


Insulation Junction

The subtype feature layer Insulation Junction describes the component which stops the flow of

electricity through the cathodic protection zone.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

51 0 Unknown An unknown is a Insulation

Junction whose type is not

known.

51 901 Insulation

Junction

Insulation junction stops the flow

of electricity to a metallic asset

Container: No

Attachments: Yes

Editor Tracking:







Attributes:



















Tracking.












manufacturer (Text [2]) – The organization responsible for the manufacture of the Bond

Junction.

manufacturerlotno (Long Integer) – The manufacturer lot number of the Bond Junction.

manufacturedate (Date) – The date when the Bond Junction was created by the manufacturer.


of the Bond Junction.

locationdescription (Text([100]) A description of the location of the Bond Junction.

criticalindicator (Short Integer) – The yes/no Boolean value indicating whether the bond junction

is considered critical.

























Referencing tools.










geodatabase.




populated.



populated.



populated.






Bond Junction Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_BondJunction


assettype Asset Type BONDJUNCTIONTYPE

















N/A Resistance Indicator RESISTANCEINDICATOR













Name

ENGROUTENAME




Name

CONTINROUTENAME



gpsx GPS X GPSX

gpsy GPS Y GPSY

gpsz GPS Z N/A






Name

N/A


Name

N/A



Name

N/A


N/A CPTRACEWEIGHT

N/A LASTPUMPDATE


Structure Boundary Definition: The Structure Boundary polygon feature class models those physical facility structures which

contain pipe system components.

StructureBoundary polygon features contain pipe assemblies and/or pipe system components. For

example, a vault can be contain a regulator station assembly which can contain valves and regulators.


These are the general types of associations for structure boundaries:

• A structure boundary can contain…

o an assembly. For example a pipeline vault boundary can contain a pump station.

o a device. For example a pipeline station structure can contain a valve.

o a line. For example a pipeline processing facility can contain transmission station

pipe.

o a junction. For example a pipeline vault boundary can contain a coupling.

o a structure junction. For example a pipeline station structure can contain a pipe

hanger.

o a structure line. For example a pipeline processing facility can contain pipe casing.

o a structure boundary. For example a pipeline processing facility can contain a

station structure.

Pipeline Processing

Facility

Pipeline Station

Structure

Pipeline Vault

Boundary

StructureBoundary



This is the schema for the StructureBoundary feature class.





subnetworkname Text(2000) Required for Utility Network






installdate Date

inservicedate Date

assetid Text(64)

stationname Text(30)



lifecyclestatus Short Integer Network Attribute

notes Text(2000)


coverunits Short Integer

structureunits Short Integer

pipelineoperator Text (30)

structureheight Double(16,8)

structurelength Double(16,8)

structurewidth Double(16,8)

material Text(2)

coverdepth Double(16,8)

coverlength Double(16,8)

coverwidth Double(16,8)

ventedindicator Short Integer

contractor Text(50)

Pipelinestation Double(16,8)

legacyid Text(20)


Pipeline Station Structure

The subtype feature layer Pipeline Station Structure describes the above ground structure used

to house oil and gas facilities such as compressor stations, pump stations, town border stations

and regulator stations.

GeometryType: Polygon with Z and M enabled

Relationships:

-StructureBoundary__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

1 0 Unknown An unknown is a structure whose

type is not known.

1 1 Station

Structure

A generic structure facility.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:





Coded Value Domain: Pipeline_Structure_Boundary_Station_Structure


which the station structure feature participates.


subnetworkname (Text[2000]) – The name of the Utility Network managed subnetwork that the

station structure is associated too.

creationdate (Date) – The date and time the structure boundary record was originally created in


creator (Text[255]) – The name of the system user who originally created the structure

boundary record in the geodatabase. This value is automatically populated by the Editor

Tracking.

lastupdate (Date) – The date and time the structure boundary record was last modified in the



the structure boundary record in the geodatabase. This value is automatically populated by the

Editor Tracking.



installdate (Date) – The date when the construction of the structure boundary feature was

completed.

inservicedate (Date) – The date when the structure boundary feature was put into production.


stationname (Text[30]) – The name used to uniquely identify and reference this facility.


ownedby (Short Integer)—The name of the organization with ownership of the station structure.




maintenance of the station structure. In most instances, this will be the name of your

organization.


locationdescription (Text([100]) A description of the location of the station structure.

structureheight (Double[16,8]) – The vertical linear distance from ground level to the top of the

structure roof.

lifecyclestatus (Short Integer) – The text value indicating the life cycle state of the structure

boundary. Coded Value Domain: Pipeline_LifeCycle_Status

structurelength (Double[16,8]) – The horizontal linear distance at ground level along one edge of

the structure.

structurewidth (Double[16,8]) – The horizontal linear distance at ground level along the edge

perpendicular to the edge used for the structurelength measurement.

structureunits (Short Integer) – The units of measurement used to define the structure height,

length and width.

material (Text[2]) – The primary material used in the construction of the station structure

facility.

locationdescription (Text([100]) A description of the location of the station structure.

contractor (Text[50]) – The name of the company hired to construct the station structure.

pipelineoperator (Text[30]) – The name of the external organization that is providing liquid or

gas to the pipeline facility.

pipelinestation (Double[16,5]) – The value is the measurement indicating where the station

structure is located along the pipeline operator’s route. This column is only used when an

external system requires that the linear referencing data be stored as a columnar attribute

instead of embedded within the geometry.




geodatabase.






under which the structure boundary feature was installed.


number under which a work order was generated to install the structure boundary feature.


management system information for this structure boundary feature.


Pipeline Station Structure Migration Table UPDM 2016 to UPDM 2019:


P_StationStructure




subnetworkname Is Connected N/A









stationname Station Name N/A

structureheight Structure Height STRUCTUREHEIGHT


structurewidth Structure Width STRUCTUREWIDTH

structureunits Structure Units STRUCTUREUNITS



contractor Contractor CONTRACTOR

ownedby Owner OWNER



pipelineoperator Pipeline Operator PIPELINEOPERATOR

pipelinestation Pipeline Station PIPELINESTATION







Pipeline Vault Boundary

The subtype feature layer Pipeline Vault Boundary describes the below ground structure used to

house oil and gas facilities such as compressor stations, pump stations, town border stations and

regulator stations.


Relationships:

-P_UPDMJunction__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

2 0 Unknown An unknown is a vault whose type is

not known.

2 81 Vault A generic vault facility.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:






which the vault feature participates.



vault is associated too.





Tracking.





Editor Tracking.




completed.





ownedby (Short Integer)—The name of the organization with ownership of the vault. In most




maintenance of the vault. In most instances, this will be the name of your organization.


locationdescription (Text([100]) A description of the location of the Vault.


boundary. Coded Value Domain: Pipeline_LifeCycle_Status_Combined

structureheight (Double[16,8]) – The vertical linear distance from floor to the ceiling of the vault.

structurelength (Double[16,8]) – The horizontal linear distance at floor level along one edge of

the structure.

structurewidth (Double[16,8]) – The horizontal linear distance at floor level along the edge

perpendicular to the edge used for the STRUCTURElength measurement.

structureunits (Short Integer) – The units of measurement used to define the structure height,

length and width.

material (Text[2]) – The primary material used in the construction of the station structure

facility.

coverdepth (Double[16,8]) – The vertical distance below the ground to the roof of the vault.

coverlength (Double[16,8]) – The vertical linear distance measured along one edge of the roof of

the vault.

coverwidth (Double[16,8]) – The vertical linear distance measure along the roof edge

perpendicular to the roof edge used for the COVERlength measurement.

ventedindicator (Short Integer) – The yes/no Boolean value indicating whether the vault is

vented to the surface.


contractor (Text[50]) – The name of the company hired to construct the station structure.




pipelinestation (Double[16,5]) – The value is the measurement indicating where the station

structure is located along the pipeline operator’s route. This column is only used when an

external system requires that the linear referencing data be stored as a columnar attribute

instead of embedded within the geometry.



geodatabase.












Pipeline Vault Boundary Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: P_Vault




subnetworkname Is Connected N/A









stationname Station Name N/A

structureheight Structure Height STRUCTUREHEIGHT


structurewidth Structure Width STRUCTUREWIDTH

structureunits Structure Units STRUCTUREUNITS



contractor Contractor CONTRACTOR

ownedby Owner OWNER




pipelineoperator Pipeline Operator N/A

pipelinestation Pipeline Station N/A







Pipeline Processing Facility

The subtype feature layer Pipeline Processing Facility describes the above ground structure used

to process the raw commodity.


Relationships:

-StructureBoundary__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

3 0 Unknown An unknown is a structure whose

type is not known.

3 41 Processing

Facility

A generic processing facility.

Container: Yes

Attachments: Yes

Editor Tracking:







Attributes:






which the processing facility feature participates.



processing facility is associated too.





Tracking.





Editor Tracking.




completed.





ownedby (Short Integer)—The name of the organization with ownership of the processing

facility. In most instances, this will be the name of your organization.



maintenance of the processing facility. In most instances, this will be the name of your

organization.


locationdescription (Text([100]) A description of the location of the processing facility.


boundary. Coded Value Domain: Pipeline_LifeCycle_Status_Combined

contractor (Text[50]) – The name of the company hired to construct the processing facility.



pipelinestation (Double[16,5]) – The value is the measurement indicating where the processing

facility is located along the pipeline operator’s route. This column is only used when an external

system requires that the linear referencing data be stored as a columnar attribute instead of

embedded within the geometry.



geodatabase.












Pipeline Processing Facility Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline Processing Facility as a separate feature class. This is a new feature layer for UPDM 2019.


Structure Junction Definition: The Structure Junction point feature class models those physical components which are

attached to the pipe system but the transport commodity does not traverse thru the component.

StructureJunction point features connect to the pipe system thru a structural association. For example,

a pipe hanger can be associated to an UPDMJunction connection point, which connects to a pipe

segment.


These are the general types of associations for structure junctions:

• A structure junction can be associated to…

o a device. For example a pipeline pipe hanger can be connected to a valve with a

structural association.

o a junction. For example a pipeline pipe support can be connected to a weld point

with a structural assocation.

Pipeline Anchor

Pipeline End

Connection

Pipeline Muffler

Pipeline Pipe

Hanger

StructureJunction

Pipeline Pipe

Support

Pipeline Vault

Pipeline Valve Box



This is the schema for the StrutureJunction feature class.











installdate Date

assetid Text(64)




quantity Short Integer

weight Double(8,2)

barcode Text(16)





material Text(2)

notes Text(2000)


gpsx Double(16,8)

gpsy Double(16,8)

gpsz Double(16,8)

legacyid Text(20)


legacyid Text(38)




Pipeline Muffler

The subtype feature layer Pipeline Muffler describes the pipeline facility component used to

reduce the noise produced by a compressor or pump.


Relationships:

-StructureJunction__ATTACHREL


Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

1 0 Unknown An unknown is a muffler whose

type is not known.

1 1 Muffler A generic muffler component.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the muffler feature participates.



muffler is associated too.

creationdate (Date) – The date and time the structure junction record was originally created in


creator (Text[255]) – The name of the system user who originally created the structure junction


lastupdate (Date) – The date and time the structure junction record was last modified in the



the structure junction record in the geodatabase. This value is automatically populated by the

Editor Tracking.



installdate (Date) – The date when the muffler was installed.

ownedby (Short Integer)—The name of the organization with ownership of the pipeline muffler.




maintenance of the pipeline muffler. In most instances, this will be the name of your

organization.




junction. Coded Value Domain: Pipeline_LifeCycle_Status

barcode (Text[16]) – The alpha-numeric code read from the bar code on the muffler.

manufacturer (Text[2]) – The organization responsible for the construction of the muffler.

Coded Value Domain: Pipeline_Muffler_Manufacturer

manufacturerlotno (Long Integer) – The manufacturer lot number from which the muffler was

created.

manufacturedate (Date) – The date when the muffler was constructed by the manufacturer.

manufacturecomponent (Text[2]) – The manufacturer specified version or name of the muffler.

Coded Value Domain: Pipeline_Muffler_Model

material (Text[2]) – The primary material from which the anchor was manufactured.

Coded Value Domain: Pipeline_Muffler_Material


notes(Text[2000]) – General notes about the structure junction.



geodatabase.




populated.



populated.



populated






under which the structure junction feature was installed.


number under which a work order was generated to install the structure junction feature.


management system information for this structure junction feature.

locationdescription (Text([100]) A description of the location of the Muffler.


Pipeline Muffler Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline Muffler as a separate feature class. This is a new feature layer for UPDM 2019.


Pipeline Anchor

The subtype feature layer Pipeline Anchor describes the pipeline component used to secure the

pipeline to a specific location.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

2 0 Unknown An unknown is an anchor whose

type is not known.

2 41 Anchor A generic anchor component.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the anchor feature participates.



anchor is associated too.









Editor Tracking.



installdate (Date) – The date when the anchor was installed.

ownedby (Short Integer)—The name of the organization with ownership of the anchor. In most




maintenance of the anchor. In most instances, this will be the name of your organization.





quantity (Short Integer) – The number of anchor’s connected to the pipeline.

weight (Double[8,2]) – The total mass of the anchor.

barcode (Text[16]) – The alpha-numeric code read from the bar code on the anchor.

manufacturer (Text[2]) – The organization responsible for the construction of the anchor.

Coded Value Domain: Pipeline_Anchor_Manufacturer

manufacturerlotno (Long Integer) – The manufacturer lot number from which the anchor was

created.

manufacturedate (Date) – The date when the anchor was constructed by the manufacturer.

manufacturecomponent (Text[2]) – The manufacturer specified version or name of the anchor.

Coded Value Domain: Pipeline_Anchor_Model

material (Text[2]) – The primary material of the anchor.

Coded Value Domain: Pipeline Anchor_Material


notes (Text[2000]) – General notes about the structure junction.



geodatabase.




populated.



populated.




populated










locationdescription (Text([100]) A description of the location of the anchor.


Pipeline Anchor Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Anchor as a separate feature class. This is a new feature layer for UPDM 2019.


Pipeline Pipe Support

The subtype feature layer Pipeline Pipe Support describes the pipeline facility component used

to support a pipe segment.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

3 0 Unknown An unknown is a pipe support whose

type is not known.

3 81 Pipe Stand A support structure used to secure a

pipeline asset.

3 82 Roller A support structure used to uphold a

pipe segment but allow for lateral

movement via thermal

expansion/contraction.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the pipe support feature participates.



pipe support is associated too.









Editor Tracking.



installdate (Date) – The date when the pipe support was installed.



barcode (Text[16]) – The alpha-numeric code read from the bar code on the pipe support.

manufacturer (Text[2]) – The organization responsible for the construction of the pipe support.

Coded Value Domain: Pipeline_Pipe_Suport_Manufacturer


manufacturerlotno (Long Integer) – The manufacturer lot number from which the pipe support

was created.

manufacturedate (Date) – The date when the pipe support was constructed by the

manufacturer.

manufacturecomponent (Text[2]) – The manufacturer specified version or name of the pipe

support. Coded Value Domain: Pipeline_Pipe_Support_Model

ownedby (Short Integer)—The name of the organization with ownership of the pipe support. In




maintenance of the pipe support. In most instances, this will be the name of your organization.




locationdescription (Text([100]) A description of the location of the pipe support.



geodatabase.




populated.



populated.



populated


Pipeline Pipe Support Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline Pipe Support as a separate feature class. This is a new feature layer for UPDM 2019.


Pipeline Pipe Hanger

The subtype feature layer Pipeline Pipe Hanger describes the pipeline facility component used to

hang a pipe segment from an elevated location.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

4 0 Unknown An unknown is a pipe support whose

type is not known.

4 121 Constant Spring A support structure used provide a

constant tension.

4 122 Rigid A support structure used to restrict

the movement of the hung pipe

segment.

4 123 Variable Spring A support structure used to allow

limited movement in specified

directions.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the pipe hanger feature participates.



pipe hanger is associated too.









Editor Tracking.





barcode (Text[16]) – The alpha-numeric code read from the bar code on the pipe hanger.

manufacturer (Text[2]) – The organization responsible for the construction of the pipe hanger.

Coded Value Domain: Pipeline_Hanger_Manufacturer

manufacturerlotno (Long Integer) – The manufacturer lot number from which the pipe hanger

was created.


manufacturedate (Date) – The date when the pipe hanger was constructed by the manufacturer.

manufacturecomponent (Text[2]) – The manufacturer specified version or name of the pipe

hanger. Coded Value Domain: Pipeline_Hanger_Model

installdate (Date) – The date when the pipe hanger was installed.

ownedby (Short Integer)—The name of the organization with ownership of the pipe hanger. In




maintenance of the pipe hanger. In most instances, this will be the name of your organization.




locationdescription (Text([100]) A description of the location of the pipe hanger.



geodatabase.




populated.



populated.



populated





Pipeline Pipe Hanger Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline Pipe Hanger as a separate feature class. This is a new feature layer for UPDM 2019.


Pipeline End Connection

The subtype feature layer Pipeline End connection describes the type of connection at the end of

a pipe casing.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

5 0 Unknown An unknown is a end connection


5 161 End Seals The seal at the end of a pipe

casing to contain the pipe casing

fill.

5 162 Skid & Straps

5 163 Spacers An insert in to a pipe casing to

maintain spacing between the

pipe casing and the inserted

pipe.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the end connection feature participates.



end connection is associated too.









Editor Tracking.





barcode (Text[16]) – The alpha-numeric code read from the bar code on the end connection.

manufacturer (Text[2]) – The organization responsible for the construction of the end

connection. Coded Value Domain: Pipeline_End_Connection_Manufacturer

manufacturerlotno (Long Integer]) – The manufacturer lot number from which the end

connection was created.


manufacturedate (Date) – The date when the end connection was constructed by the

manufacturer.

manufacturecomponent (Text[2]) – The manufacturer specified version or name of the end

connection. Coded Value Domain: Pipeline_End_Connection_Model

material (Text[2]) – The primary material used in the manufacture of the end connection. Coded

Value Domain: Pipeline_End_Connection_Material

installdate (Date) – The date when the end connection was installed.

ownedby (Short Integer)—The name of the organization with ownership of the pipeline end

connection. In most instances, this will be the name of your organization.



maintenance of the end connection. In most instances, this will be the name of your

organization.




locationdescription (Text([100]) A description of the location of the end connection.



geodatabase.




populated.



populated.




populated











Pipeline End Connection Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline End Connection as a separate feature class. This is a new feature layer for UPDM 2019.


Pipeline Vault

The subtype feature layer Pipeline Vault describes the underground structure which stores a gas

facility.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

6 0 Unknown An unknown is vault whose type

is not known.

6 201 Vault A generic underground facility.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:









vault is associated too.









Editor Tracking.





installdate (Date) – The date when the vault was construction.

ownedby (Short Integer)—The name of the organization with ownership of the vault. In most





maintenance of the vault. In most instances, this will be the name of your organization.




locationdescription (Text([100]) A description of the location of the vault.



geodatabase.




populated.



populated.



populated











Pipeline Vault Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline Vault as a separate feature class. This is a new feature layer for UPDM 2019.


Pipeline Valve Box

The subtype feature layer Pipeline Valve Box describes the underground structure which stores a

gas valve.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

7 0 Unknown An unknown is vault whose type

is not known.

7 61 Curb Box A buried container on a gas

service line containing a shutoff

valve.

7 62 Curb Box with

Stationary Rod

A buried container on a gas

service line containing a shutoff

valve, and incudes a upward

extending rod.

7 63 Roadway A valve box specifically designed

for installation within a road

right-of-way.

7 64 Valve Box An underground container for

encasing a gas valve.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:









valve box is associated too.









Editor Tracking.





installdate (Date) – The date when the valve box was installed.

ownedby (Short Integer)—The name of the organization with ownership of the valve box. In





maintenance of the valve box. In most instances, this will be the name of your organization.




locationdescription (Text([100]) A description of the location of the valve box.



geodatabase.




populated.



populated.



populated











Pipeline Valve Box Migration Table UPDM 2016 to UPDM 2019: The UPDM 2016 model did not define Pipeline Valve Box as a separate feature class. This is a new feature layer for UPDM 2019.


Structure Line Definition: The Structure Line polyline feature class models those physical components which contain

the pipe system but the transport commodity does not traverse thru the component.

StructureLine polyline features a containers which can contain pipe system components such as pipe

segments, devices, or junctions. For example, a casing can contain a pipe segment.


These are the general types of associations for structure lines:

• A structure line can contain…

o a device. For example a pipeline casing can contain a valve.

o a junction. For example a pipeline casing can contain a coupling.

o a line. For example a pipeline casing can contain a pipe segment.

Pipeline Casing

StructureLine



This is the schema for the StrutureLine feature class.











filltype Short Integer

ventedindicator Short Integer

insertedindicator Short Integer

installdate Date

inservicedate Date

assetid Text(64)




casingdiameter Double(8,2)

measuredlength Double(16,6)

lengthsource Short Integer

material Text(2)

notes Text(2000)

coatingtype Text(30)




endconnection Text(15)

filldate Date

fillcapacity Long Integer

protectiontype Text(20)

reason Text(20)


legacyid Text(38)

wordorderid Text(38)









engfromm Double(16,5) ArcGIS Pipeline Referencing Attribute

engtorouteid Text(38) ArcGIS Pipeline Referencing Attribute

engtoroutename Text(100) ArcGIS Pipeline Referencing Attribute

engtom Double(16,5) ArcGIS Pipeline Referencing Attribute



contintom Double(16,5) ArcGIS Pipeline Referencing Attribute

fromrefmethod Short Integer ArcGIS Pipeline Referencing Attribute

fromreflocation Text(50) ArcGIS Pipeline Referencing Attribute

fromrefoffset Text(50) ArcGIS Pipeline Referencing Attribute

torefmethod Short Integer ArcGIS Pipeline Referencing Attribute

toreflocation Text(50) ArcGIS Pipeline Referencing Attribute

torefoffset Text(50) ArcGIS Pipeline Referencing Attribute




Pipeline Pipe Casing

The subtype feature layer Pipeline Pipe Casing describes the pipeline facility used to encase a

portion of a pipeline.


Relationships:



Asset Group

(Subtype Code)

Asset Type

(Code)

Asset Types

(Description)

Description

1 0 Unknown An unknown is a pipe casing


1 1 Casing A generic pipe casing.

Container: No

Attachments: Yes

Editor Tracking:







Attributes:






which the pipe casing feature participates.



pipe casing is associated too.

creationdate (Date) – The date and time the structure line record was originally created in the


creator (Text[255]) – The name of the system user who originally created the structure line


lastupdate (Date) – The date and time the structure line record was last modified in the



the structure line record in the geodatabase. This value is automatically populated by the Editor

Tracking.



lifecyclestatus (Short Integer) – The text value indicating the life cycle state of the structure line.


installdate (Date) – The date when the pipe casing was installed.

inservicedate (Date) – The date when the pipe casing was placed into service.

casingdiameter (Short Integer) – The generalized edge to edge nominal measured length of a

straight line through the center of the pipe casing.


diameterunits (Short Integer) - The unit of measure used to define the diameter of the pipe

casing feature.


coatingtype (Text[30]) – The type of material applied to the exterior of the pipe casing. Coded

Value Domain: Pipeline_Coating_Type

vendedindicator (Short Integer) – The yes/no boolean value indicating whether the pipe casing is

vented.


insertedindicator (Short Integer) – The yes/no Boolean value indicating whether the pipe casing

was formerly a retired pipeline and a new pipe segment whas been inserted into the retired

pipeline.


filldate (Date) – The date when the pipe casing was filled with material.

filltype (Short Integer) – The type of material used to fill the pipe casing.

fillcapacity (Long Integer) – The volume of maerial required to fill the interior of the pipe casing.

locationdescription (Text[100]) – The textural description of the location of the pipe casing.

protectiontype (Text[20]) – The type of cathodic protection used for the pipe casing.

reason (Text[20]) – The reason for the installation of the pipe casing to protect the pipe

segment.

endconnection (Text[15]) - The type of connection applied to the end of the pipe casing to seal

the pipe.

measuredlength (Double[16,6]) – The actual length of the pipe casing segment.

lengthunits (Short Integer) - The unit of measure used to define the length of the pipe casing

feature.


lengthsource (Short Integer) – The method used to determine the MEASUREDlength value.


spatialaccuracy (Short Integer) – This short integer value provides an assessment of the

geospatial location accuracy of the feature’s geometry when the feature is inserted into the

geodatabase.






under which the structure line feature was installed.


number under which a work order was generated to install the structure line feature.


management system information for this structure line feature.

notes(Text[2000]) - General notes about the structure line.

eventid (Text[38])—The unique ID for each structure line record. This attribute is only used by

organizations wanting to maintain the Pipe Casing features as event records with the ArcGIS



fromdate (Date)—The date the structure line became active on the route. This attribute is only

used by organizations wanting to maintain the Pipe Casing features as event records with the



todate (Date)—The date the structure line was retired from the route. This attribute is only used

by organizations wanting to maintain the Pipe Casing features as event records with the ArcGIS





Pipe Casing features as event records with the ArcGIS Pipeline Referencing tools. The value is






maintain the Pipe Casing features as event records with the ArcGIS Pipeline Referencing tools.



networks.



organizations wanting to maintain the Pipe Casing features as event records with the ArcGIS






the Pipe Casing features as event records with the ArcGIS Pipeline Referencing tools. The value

is automatically generated and populated by the ArcGIS Pipeline Referencing tools. engtorouteid

is not required if modeling in ArcGIS Pipeline Referencing (APR) as continuous networks.






networks.



wanting to maintain the Pipe Casing features as event records with the ArcGIS Pipeline


Referencing tools. engtom is not required if modeling in ArcGIS Pipeline Referencing (APR) as





Referencing tools.





Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the Pipe Casing features

as event records with the ArcGIS Pipeline Referencing tools.



This attribute is only used by organizations wanting to maintain the Pipe Casing features as











fromrefoffset(Text[50])—The offset measure. This attribute is only used by organizations



Torefmethod (Short Integer)—The method of referencing the offset feature. This can be










to maintain the Pipe Casing features as event records with the ArcGIS Pipeline Referencing tools.




location on a route. This attribute is only used by organizations wanting to maintain the Pipe

Casing features as event records with the ArcGIS Pipeline Referencing tools. The value is



Pipeline Pipe Casing Migration Table UPDM 2016 to UPDM 2019:

UPDM 2019 Attribute Alias UPDM 2016: PipeCasing












assetid assetid


casingdiameter Casing Diameter CASINGDIAMETER


coatingtype Coating Type COATINGTYPE

endconnection End Connection ENDCONNECTION

filldate Fill Date FILLDATE

filltype Fill Type FILLTYPE

fillcapacity Fill Capacity FILLCAPACITY


protectontype Protection Type PROTECTIONTYPE


reason Reason REASON

vendedindicator Vended Indicator VENTEDINDICATOR

insertedindicator Inserted Indicator INSERTEDINDICATOR









notes Notes COMMENTS




engrouteid Engineering RouteID ENGROUTENAME




Name

CONTINROUTENAME

continfromm Continuous From

Measure

CONTINFROMM


fromrefmethod From Reference

Method

FROMREFMETHOD


fromreflocation From Reference

Location

FROMREFLOCATION






locationerror Location Error LOCCATIONERROR


Inspections Inspections are repetitive activities that an organization performs as part of the operation of a pipe

system. Many of these inspections are required by U.S. DOT regulations. The feature classes and table

objects listed in this section help with the management of the information collected by field staff as part

of the inspection process.

Casing Inspection

CP Bond Inspection

CP Rectifier Inspection

CP Test Point Reading

Crossing Inspection

Electric Survey

Excavation Damage

Exposed Pipe Inspections

Gas Leak Inspection

Isolated Pipe Inspection

Inspection Notes

Leak Survey Area

Line Valve Inspection

Regulator Inspection

Inspection Range

Strainer Inspection

Relief Valve Inspection

Inspections

Valve Inspection

Station Visual Inspection


Casing Inspection

The table P_CasingInspection contains the results of cathodic inspections of metallic gas pipe casings. Metallic casings carrying gas pipes are also subject to corrosion and can participate in a cathodic protection system. A casing inspection represents the set of electrical field measurements and other information collected on the casing as well as on the gas pipe inside the casing. DOT Frequency: At least once each calendar year but with intervals not exceeding 15 months. Reference: DOT 192.465

GeometryType: None

Relationships:

-P_StructureLine_P_CasingInspection

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:

objectid (Integer)–The geodatabase generated and maintained unique identifier value.

inspectedby (Text[50])–The name of the gas operations field technician responsible for recording

the field measurement.

daterecorded (Date)–The date and time the gas operations field technician recorded the

information for this record.

carrierpipepson (Double[16,6])–The voltage reading for the pipe-to-soil on measurement for the

gas pipe inside the casing.

carrierpipepsoff (Double[16,6])–The voltage reading for the pipe-to-soil off measurement for the

gas pipe inside the casing.

casingpipepson (Double[16,6])–The voltage reading for the pipe-to-soil on measurement for the

gas pipe casing.

casingpipepsoff (Double[16,6])–The voltage reading for the pipe-to-soil off measurement for the

gas pipe casing.

shorted (Short Integer)–The yes/no Boolean value indicating whether there was an electrical

short.


instrument (Text[30])–The instrument used to acquire the measurements.

maintenancerequired (Text[255])–The description of any follow-up maintenance activities

required at this casing.

maintenanceperformed (Text[255])–The description of any maintenance actions taken by the

field technician during the read process.

globalid (Global ID)–The system-side unique identifier.

structureline_globalid (GUID)–The structureline feature class globalid value of the record with

which the field measurement is associated.

creationdate (Date) - The date and time when the inspection was originally created in the



creator (Text[255]) - The name of the system user who originally created the inspection record


lastupdate (Date) - The date and time when the inspection record was last modified in the



inspection record in the geodatabase. This value is automatically populated by the Editor

Tracking.


CP Bond Inspection

The table P_CPBondInspection contains the results of the inspection of cathodic protection bonds. This record contains the measurements obtained at interference bond locations. DOT Frequency: Critical bonds are to be inspected 6 times per calendar year but with intervals not exceeding 2½ months. All others are once per calendar year but with intervals not exceeding 15 months. Reference: DOT 192.465

GeometryType: None

Relationships:

-P_UPDMJunction_P_CPBondInspection

-P_UPDMLine_P_CPBondInspection

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:




dateinspected (Date)–The date and time the gas operations field technician recorded the


bondedpson (Double[8,5])–The voltage reading for the pipe-to-soil on measurement while

bonded to the foreign structure.

disbondedpson (Double[8,5])–The voltage reading for the pipe-to-soil on measurement while

not bonded to the foreign structure.

foreignstructuredisbondedpson (Double[8,5])–The voltage reading from the foreign structure for

the pipe-to-soil on measurement while not bonded.

dcamps (Double[8,5])–The amperage reading taken at the interference bond.



required at this interference bond.



globalid (Global ID)–The systemwide unique identifier.

updmjunction_globalid (Guid)–The UPDMJunction feature class, subtype Bond Junction globalid

value of the record with which the field measurement is associated.

updmline_globalid (Guid)–The UPDMLine feature class, subtype Bond Wire globalid value of the

record with which the field measurement is associated.

creationdate (Date) - The date and time when the inspection was originally created in the


creator (Text[255]) - The name of the system user who originally created the inspection record



lastupdate (Date) - The date and time when the inspection record was last modified in the



inspection record in the geodatabase. This value is automatically populated by the Editor

Tracking.


CP Rectifier Inspection

The table P_CPRectifierInspection contains the results of the inspection of a cathodic protection rectifier. Regulations require that each rectifier be inspected periodically to ensure it is operating properly. DOT Frequency: Six times per calendar year but with intervals not exceeding two and one-half months.

Reference: DOT 192.465

GeometryType: None

Relationships:

-UPDMDevice_P_CPRectifierInspection

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


inspectedby (Text[50])–The name of the operations field technician responsible for recording the

field measurement.

dateinspected (Date)–The date and time the operations field technician recorded the


pson (Double[8,5])–The voltage reading for the pipe-to-soil on measurement.

psoff (Double[8,5])–The voltage reading for the pipe-to-soil off measurement.

dcvoltagefound (Double[8,5])–The DC voltage reading of the rectifier as initially found at the

device.

dcampsfound (Double[8,5])–The DC amperage reading of the rectifier as initially found at the

device.

statusasfound (Text[5])–The operating status of the rectifier as initially found by the field

technician at the device.

Coded Value Domain: On/OffStatus

dcvoltageleft (Double[8,5])–The DC voltage reading of the rectifier as left by the field technician

at the device.

dcampsleft (Double[8,5])–The DC amperage reading of the rectifier as left by the field technician

at the device.

statusasleft (Text[5])–The operating status of the rectifier as left by the technician at the device.

Coded Value Domain: On/OffStatus

taptype (Text[15)–The type of tapping mechanism on the rectifier, for example, Fine/Coarse or

Variable.

tapsetting (Text[15])–The current tap position setting of the rectifier.



required at this rectifier.





updmdevice_globalid (Guid)–The UPDMDevice feature class, subtype Rectifier, globalid value of

the record with which the field inspection is associated.

creator (Text[255])–The name of the system user who originally created the object record in the


creationdate (Date)–The date and time the object record was originally created in the


updatedby (Text[255])–The name of the system user responsible for the last modification to the


lastupdate (Date)–The date and time the object record was last modified in the geodatabase.



CP Test Point Reading

The table P_CPTestPointReading represents the set of electrical field measurements and other information collected at a specific test point location along the pipeline.

DOT Frequency: Each pipeline that is under cathodic protection must be tested at least once each calendar year but with intervals not exceeding 15 months. Reference: DOT 192.465

GeometryType: None

Relationships:

-UPDMDevice_P_CPTestPointReading

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:




dateinspected (Date)–The date and time the operations field technician recorded

the information for this record.


psoff (Double[8,5])–The voltage reading for the pipe-to-soil off measurement.

soilresistivity (Double[8,5])–The resistivity of the soil measured in ohm-centimeter.

shorted (Short Integer)–The yes/no Boolean value indicating whether there is an electrical short

at the test station.



reasonforfailedreading (Text[30])–If applicable, the reason determined by the field technician

should the measurement indicate that the facility is not properly protected. Examples include a

missing, broken, or disconnected electrical lead wire.

correctiveactiontaken (Text[30])–If applicable, the corrective or repair action taken by the field

technician to restore the cathodic protection.


required at this test station.




updmdevice_globalid (Guid)–The CPTestPoint feature class globalid value of the record with





Crossing Inspection

The inspection performed at the locations identified by the features in the LineCrossing feature

class.

GeometryType: None

Relationships:

-PipeCrossing_P_CrossingInspection

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


inspector (Text[50])–The name of the operations field technician who performed the inspection.

lastinspectiondate (Date)–The date the last inspection was performed.

nextinspectiondate (Date)–The date the next inspection is due to be performed.

locationdescription (Text[150])–The textual description of the location of the crossing.

notes (Text[255])–The textual documentation of the inspection.


pipecrossing_globalid (Guid)–The PipeCrossing feature class globalid value of the record with











Electric Survey

The inspection performed on above ground metallic pipes to monitor rate of corrosion.

GeometryType: Polyline with z-and m-values enabled

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


surveydate (Date)–The date the survey what performed.

surveyduedate (Date)–The date the next survey is due to be performed.

surveyfrequency (Short Integer)–The frequency at which surveys are performed.

voltage (Double[8,4])–The measured voltage.

amperage (Double[8,4])–The measured amperage.











Excavation Damage

The polyline feature class P_ExcavationDamage represents the location where a component of

the pipe system has been damaged by the actions of an external entity. This feature class stores

the information, photos, and sketches captured as part of the reporting process to document

the incident.

GeometryType: Polyline with z-and m-values enabled

Relationships: No

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:


datedamaged (Date)–The date the incident causing the damage occurred.

responsiblepartyname (Text[50])–The name of the company or person responsible for causing

the damage to the pipe system.

resppartycontactname (Text[50])–The point of contact at the company responsible for causing

the damage to the pipe system.

responsiblepartyaddress (Text[50])–The street address of the company or person responsible for

causing the damage to the pipe system.

responsiblepartycity (Text[50])–The city name of the responsible company’s business location or

person’s residence location.

responsiblepartystate (Text[2])–The U.S. postal code abbreviation of the responsible company’s business location or person’s residence location.

Coded Value Domain: Pipeline_Region

responsiblepartyphone (Text[20])–The telephone number of the responsible company’s business

or person’s primary contact phone.

responsiblepartytype (Text[30])–The categorical group in which the responsible party would be

classified. Valid values are Home Owner, Other Utility, Company, Contractor, Local Government,

State Government, Federal Government, and Other.

Coded Value Domain: Pipeline_ExcavDamRespPartyType

incidentlocationaddress (Text[50])–The approximate street address of where the damage

occurred to the gas system.

incidentlocationcity (Text[50])–The name of the city where the damage occurred to the gas

system.

incidentlocationstate (Text[2])–The U.S. postal code abbreviation of the state where the damage

occurred to the gas system.

Coded Value Domain: Pipeline_Region

damagetype (Text[25])–The type of damage to the gas system.

Coded Value Domain: Pipeline_ExcavDamDamageType

damagedfacilitytype (Text[30])–The type of gas component damaged by the excavation event.

Coded Value Domain: Pipeline_LeakFacilityType

equipcausingdamage (Text[20])–The type of equipment responsible for the excavation damage.


Coded Value Domain: Pipeline_ExcavEquipCausingDamage

worktype (Text[30])–The type of work that was being performed when the excavation damage

occurred.

Coded Value Domain: Pipeline_ExcavDamWorkType

rootcause (Text[30])–The underlying cause of the excavation damage.

Coded Value Domain: Pipeline_ExcavDamRootCause

policereport (Short Integer)–A yes/no Boolean attribute indicating whether a police report was

filed as part of the excavation damage incident.


remarks (Text[250])–A text comment attribute to allow for additional information to be

recorded.




geodatabase.




populated.



populated.

eventid (Text[38])–The unique ID for each excavation damage record. This value is automatically

generated and populated by the ArcGIS Pipeline Referencing tools. This attribute is only used by

organizations wanting to maintain the P_ExcavationDamage features as event records with the


fromdate (Date)–The date the excavation damage event became active on the route. This value

is automatically generated and populated by the ArcGIS Pipeline Referencing tools. This

attribute is only used by organizations wanting to maintain the P_ExcavationDamage features as


todate (Date)–The date the excavation damage was retired from the route. This value is

automatically generated and populated by the ArcGIS Pipeline Referencing tools. This attribute


is only used by organizations wanting to maintain the P_ExcavationDamage features as event


engrouteid (Text[38])–The unique ID of the engineering network route where the beginning of

the linear event is located. This value is automatically generated and populated by the ArcGIS

Pipeline Referencing tools. This attribute is only used by organizations wanting to maintain the

P_ExcavationDamage features as event records with the ArcGIS Pipeline Referencing tools.

engroutename (Text[100])—The engineering network route name where the beginning of the

linear event is located. This value is automatically created and maintained by the ArcGIS Pipeline

Referencing tools. This attribute is only used by organizations wanting to maintain the


engfromm (Double[16,5])–The measure location along the engineering network engrouteid

specified route where the beginning of the linear event is located. This value is automatically


organizations wanting to maintain the P_ExcavationDamage features as event records with the


engtorouteid (Text[38])–The unique ID of the engineering network route where the completion

of the linear event is located. This value is automatically generated and populated by the ArcGIS

Pipeline Referencing tools. engtorouteid is not required if modeling in ArcGIS Pipeline

Referencing (ALRP) as continuous networks. This attribute is only used by organizations wanting

to maintain the P_ExcavationDamage features as event records with the ArcGIS Pipeline

Referencing tools.

engtoroutename (Text[100])—The engineering network route name where the completion of

the linear event is located. This value is automatically created and maintained by the ArcGIS



engtom (Double[16,5])–The measure location along the engtorouteid specified route where the

completion of the linear event is located. This value is automatically generated and populated by

the ArcGIS Pipeline Referencing tools. This attribute is only used by organizations wanting to

maintain the P_ExcavationDamage features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_ExcavationDamage features as event records with the ArcGIS





wanting to maintain the P_ExcavationDamage features as event records with the ArcGIS


continfromm (Double[16,5])—The continuous network beginning measure along the derived


tools. This attribute is only used by organizations wanting to maintain the P_ExcavationDamage


contintom (Double[16,5])—The continuous network ending measure along the derived route ID.

This value is automatically created and maintained by the ArcGIS Pipeline Referencing tools. This

attribute is only used by organizations wanting to maintain the P_ExcavationDamage features as


fromrefmethod (Short Integer)–The method of referencing the offset feature. This can be


This attribute is only used by organizations wanting to maintain the P_ExcavationDamage



fromrefoffset (Text[50])–The offset measure. This attribute is only used by organizations wanting



fromreflocation (Text[50])–The location of the offsetting feature. This can be Coordinates,




torefmethod (Short Integer)–The method of referencing the offset feature. This can be


This attribute is only used by organizations wanting to maintain the P_ExcavationDamage



torefoffset (Text[50])–The offset measure. This attribute is only used by organizations wanting




toreflocation (Text[50])–The location of the offsetting feature. This can be Coordinates,




locationerror(Text[100])–The resultant message from the process of defining the event’s


P_ExcavationDamage features as event records with the ArcGIS Pipeline Referencing tools. The











Exposed Pipe Inspection

The polyline feature class P_ExposedPipeInspect represents an exposed pipe inspection. An exposed pipe inspection is done during construction or maintenance activity. This is a field data collection activity commonly performed by the utility’s operations staff. Once the pipe is exposed, it is inspected for safe operation. Some inspections are required by DOT regulations, such as internal and external corrosion. In addition, Distribution Integrity Management (DIM) requires the collection of additional information during normal operations to gain critical knowledge of the system.

GeometryType: Polyline with z- and m-values enabled

Relationships:

-UPDMDevice_P_ExpPipeInspection

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:


inspectionnumber (Text[20])–The inspection management system-generated unique ID.

inspectiondate (Date)–The date the exposed pipe inspection was performed.

inspectedby (Text[50])–The name of the field technician who performed the inspection.

lengthexposed (Double[16,5])–The length of pipe that is exposed.

pipedepth (Double[16,5])–The depth of the pipe below the ground surface.

pittingdepth (Double[16,5])–The inspection measured depth of identified pitting.

soiltype (Text[20])–The type of soil in which the pipe is situated.

Coded Value Domain: Pipeline_SoilType.

coatingcondition (Text[25])–The description of the coating condition.

Coded Value Domain: Pipeline_CoatingCondition.

corrosioncondition (Text[25])–The inspection-determined condition of identified corrosion.

Coded Value Domain: Pipeline_CorrosionCondition

corrosionextent (Text[20])–The inspection-determined extent of corrosion.

Coded Value Domain: Pipeline_CorrosionExtent

pipecondition (Text[20])–The inspection-determined condition of the pipe. This includes plastic

pipes where cracking is possible.

Coded Value Domain: Pipeline_PipeCondition

jointtrench (Short Integer)–The yes/no Boolean value indicating whether the exposed pipe was

installed in a joint trench with other utilities.


trenchencroachment (Short Integer)–The yes/no Boolean value indicating whether third-party

utilities are in close proximity to the gas line.


repairorderrequired (Short Integer)–The yes/no Boolean value indicating whether a repair order

is required.


comments (Text[255])–The user or inspection comments.



pipeexposure_globalid (Guid)–The PipeExposure feature class globalid value of the record with

which the field inspection is associated.



geodatabase.


eventid (Text[38])–The unique ID for each exposed pipe inspection record. This value is


is only used by organizations wanting to maintain the P_ExposedPipeInspect features as event


fromdate (Date)–The date the exposed pipe inspection event became active on the route. This

value is automatically generated and populated by the ArcGIS Pipeline Referencing tools. This

attribute is only used by organizations wanting to maintain the P_ExposedPipeInspect features


todate (Date)–The date the exposed pipe inspection was retired from the route. This value is


is only used by organizations wanting to maintain the P_ExposedPipeInspect features as event





P_ExposedPipeInspect features as event records with the ArcGIS Pipeline Referencing tools.


linear event is located. The route name is automatically created and maintained by the ArcGIS


P_ExposedPipeInspect features as event records with the ArcGIS Pipeline Referencing tools.




organizations wanting to maintain the P_ExposedPipeInspect features as event records with the







to maintain the P_ExposedPipeInspect features as event records with the ArcGIS Pipeline

Referencing tools.


the linear event is located. The route name is automatically created and maintained by the

ArcGIS Pipeline Referencing tools. This attribute is only used by organizations wanting to

maintain the P_ExposedPipeInspect features as event records with the ArcGIS Pipeline

Referencing tools.

engtom(Double[16,5])–The measure location along the engtorouteid specified route where the




Referencing tools.



wanting to maintain the P_ExposedPipeInspect features as event records with the ArcGIS




wanting to maintain the P_ExposedPipeInspect features as event records with the ArcGIS




tools. This attribute is only used by organizations wanting to maintain the P_ExposedPipeInspect




attribute is only used by organizations wanting to maintain the P_ExposedPipeInspect features




This attribute is only used by organizations wanting to maintain the P_ExposedPipeInspect




fromrefoffset(Text[50])–The offset measure. This attribute is only used by organizations wanting

to maintain the P_ExposedPipeInspect features as event records with the ArcGIS Pipeline


fromreflocation(Text[50])–The location of the offsetting feature. This can be Coordinates,






This attribute is only used by organizations wanting to maintain the P_ExposedPipeInspect



torefoffset(Text[50])–The offset measure. This attribute is only used by organizations wanting to









P_ExposedPipeInspection features as event records with the ArcGIS Pipeline Referencing tools.











Gas Leak Inspection

The table P_GasLeakInspection describes a Class 2 or Class 3 leak that may be inspected multiple times over the life of the leak. For full audit capabilities, each leak inspection must be stored. This is a field data collection activity commonly performed by a gas utility’s operations staff. The field leak inspection investigation process will result is a remeasurement of the amount of gas escaping from the gas system.

GeometryType: None

Relationships:

-GasLeak_LeakInspection

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:


dateinspected (Date)–The date and time the gas operations field technician recorded the


inspectedby (Text[50])–The name of the gas operations field technician who was the initial

responder to the report of a gas leak, and who compiled the information for this record.

surfacetype (Text[20])–The type of surface covering the identified gas leak location.


gasin (Text[25])–The categorical description of where the gas leak is located.

Coded Value Domain: Pipeline_LeakInspectGasIn

probablesource (Text[25])–The field technician’s determination of the most likely pipe system

asset source of the gas leak.


leakclass (Short Integer)–The DOT classification of the type of gas leak.

Coded Value Domain: Pipeline_LeakClass

methoddetected (Text[20])–The method used by the gas field technician to identify the location

and concentration of leaking gas.

Coded Value Domain: Pipeline_LeakMethodDetected

gasmeasurement (Double[10,4])–The highest concentration of methane gas recorded by the gas

field technician while performing the leak inspection.

gasmeasurementunits (Short Integer) – The unit of measure used to determine the amount of

natural gas escaping from the leak.

Coded Value Domain: Pipeline_MeasurementUnits

comments (Text[255])–Any additional comments the gas field technician provides about the

reported leak.



gasleak_globalid (Guid)–The GasLeak feature class globalid value of the leak feature that was

inspected.










Isolated Pipe Inspection

The table P_IsolatedPipeInspection contains the inspections of isolated cathodically protected sections of pipe. This record contains the measurements obtained for separately protected, short sections of mains or services. DOT Frequency: These pipelines are generally surveyed on a sampling basis. At least 10 percent of these protected structures, distributed over the entire system, must be surveyed each calendar year, with a different 10 percent checked each subsequent year, so that the entire system is tested in each 10-year period. Reference: DOT 192.465

GeometryType: None

Relationships:

-UPDMLine_P_IsolatedPipeInspection

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:


inspectedby (Text[50])–The name of the field technician responsible for recording the field

measurement.

dateinspected (Date)–The date and time the field technician recorded the information for this

record.


shorted (Short Integer)–The yes/no Boolean value indicating whether there is an electrical short

at the test station.




required at this interference bond.




updmline_globalid (Guid)–The UPDMLine feature class globalid value of the record with which

the field inspection is associated.










Inspection Note

The point feature class P_InspectionNote describes where additional information can be

captured during an inspection that is not necessarily related to the inspection.


Relationships: No

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:


inspectiondate (Date)–The date the inspection was performed.

inspector (Text[30])–The name of the field technician who performed the inspection.

notetype (Text[30])–The type of inspection being performed when the note was captured.

comments (Text[255])–Any additional comments the field technician provides.


eventid (Text[38])–The unique ID for each inspection note event record. This value is


is only used by organizations wanting to maintain the P_InspectionNote features as event


fromdate (Date)–The date the inspection note became active on the route. This value is




todate (Date)–The date the inspection note was retired from the route. This value is




engrouteid (Text[38])–The unique ID of the engineering network route where the inspection

note is located. This value is automatically generated and populated by the ArcGIS Pipeline


P_InspectionNote features as event records with the ArcGIS Pipeline Referencing tools.

engroutename (Text[100])—The continuous network name that is automatically created and


wanting to maintain the P_InspectionNote features as event records with the ArcGIS Pipeline

Referencing tools.

engm (Double[16,5])–The measure location along the route where the inspection note is



tools. This attribute is only used by organizations wanting to maintain the P_InspectionNote





Referencing tools.




Referencing tools.



attribute is only used by organizations wanting to maintain the P_InspectionNote features as


refmethod (Short Integer)–The method of referencing the offset feature. This can be


This value is populated by the ArcGIS Pipeline Referencing tools. This attribute is only used by

organizations wanting to maintain the P_InspectionNote features as event records with the


refoffset(Text[50])–The offset measure. This value is populated by the ArcGIS Pipeline



reflocation (Text[50])–The location of the offsetting feature. This can be a Coordinate,

Feature/EventID, and/or IntersectionID. This value is populated by the ArcGIS Pipeline










Inspection Range

The polyline feature class P_InspectionRange describes the extent of patrolled pipeline. Multiple

types of inspections can be performed during a single patrol event. The results of these

inspections are tied to the inspection range by a relationship class. This allows a user to access

all information gathered during the patrol of an inspection range.


Relationships:

-InspRange_AnomalyGroup

-InspRange_PipeExposure

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:


status (Text[15])–The operational status of the inspection range record.

Coded Value Domain: Object Status

comments (Text[255])–Any additional comments about the inspection range.

inspectionstartdate (Date)–The date and time the inspection of the inspection range was

initiated.

inspectionenddate (Date)–The date and time the inspection of the inspection range was

completed.

inspectionrangename (Text[50])–The unique name assigned to the inspection range.

inspectiontype (Text[30])–The type of inspection performed within the inspection range.

Coded Value Domain: Inspection Range Type


eventid (Text[38])–The unique ID for each inspection range record. This value is automatically


organizations wanting to maintain the P_InspectionRange features as event records with the


fromdate (Date)–The date the inspection range became active on the route. This value is


is only used by organizations wanting to maintain the P_InspectionRange features as event


todate (Date)–The date the inspection range was retired from the route. This value is


is only used by organizations wanting to maintain the P_InspectionRange features as event





P_InspectionRange features as event records with the ArcGIS Pipeline Referencing tools.


linear event is located. The event is automatically created and maintained by the ArcGIS Pipeline







organizations wanting to maintain the P_InspectionRange features as event records with the






to maintain the P_InspectionRange features as event records with the ArcGIS Pipeline

Referencing tools.

engtoroutename (Text[100])—The engineering network route name where the beginning of the







maintain the P_InspectionRange features as event records with the ArcGIS Pipeline Referencing

tools.



wanting to maintain the P_InspectionRange features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_InspectionRange features as event records with the ArcGIS Pipeline

Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_InspectionRange



continfromm (Double[16,5])—The continuous network ending measure along the derived route


This attribute is only used by organizations wanting to maintain the P_InspectionRange features








to maintain the P_InspectionRange features as event records with the ArcGIS Pipeline




















P_InspectionRange features as event records with the ArcGIS Pipeline Referencing tools. The





Leak Survey Area

The polygon feature class P_LeakSurveyArea is for capturing the information associated with

compliance with federal regulations. The following are a sampling of federal regulations:

• Federal regulation Title 49 CFR 192.723 Distribution systems: Leakage surveys—

Requires that a leakage survey with leak detector be performed on the entire gas

system at least once every 5 calendar years at intervals not exceeding 63 months.

• Federal regulation title 49 CFR 192.706 Transmission lines: Leakage surveys—Requires

that surveys be conducted at intervals not exceeding 15 months for class 1 and 2

locations. Class 3 locations are not to exceed 7.5 months, and class 4 locations are not to

exceed 4.5 months.

• Federal regulation Title 49 CFR 192.481 Atmospheric corrosion control: Monitoring—

Requires that an atmospheric survey be performed on the entire gas system at least

once every 3 calendar years at intervals not exceeding 39 months.

• Federal regulation Title 49 CFR 192.723 Distribution system: Leakage surveys—Requires

that a leakage survey be conducted in business districts at intervals not exceeding 15

months but at least once every calendar year.

Keeping track of where and when a portion of a gas system has last been surveyed can be

managed with polygons. Each polygon tracks a type of leak survey, who performed the survey,

and when the polygonal area was last surveyed for leaks.

Geometry Type: Polygon

Relationships: No

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

surveytype (Text[30])—The type of leak survey to be performed within the spatial extent of the polygon. Coded Value Domain: Pipeline_LeakSurveyType mapgridname (Text[20])–The name of the map grid. surveystatus (Text[15])–The current status of the leak survey inspection for a grid. Valid values are Assigned, In Progress, and Completed. Coded Value Domain: Pipeline_LeakSurveyStatus assignedcrewleader (Text[50])–The system user name of the technician or lead technician who has been assigned to perform the scheduled leak survey inspection of the grid. surveyedby (Text[50])–The technician who performed the completed survey of the grid. startdate (Date)—The date the leak survey inspection was initiated by field staff. enddate (Date)–The date the area survey of the grid was completed. duedate (Date) —The date the leak survey area is next due for inspection. DUEDATE is calculated by adding the interval value (that is, every 60 months for area surveys) to the enddate. compdate (Date) —The compliance date is the calculated date when the leak survey is out of compliance. The compliance date is calculated by adding the INTERVAL value plus the grace period to the enddate (that is, every 63 months for area surveys). belowgradeleaks (Short Integer) –The number of leaks identified during the leak survey inspection of the grid area. surveymethod (Text[30]) –The method used to perform the leak survey inspection. Coded Value Domain: Pipeline_LeakSurveyMethod footagemains (Double[16,5]) –The calculated footage of the total active mains within the map grid. numberservices (Long Integer) –The calculated number of active services within the map grid. duration (Double)—The time required by field staff to complete the assigned leak survey. comments (Text[1000])—Additional descriptors about the leak survey.

interval (Short Integer)–The frequency as measured in months between surveys. Some state regulatory bodies require a shorter survey frequency interval than the federally mandated 63 months. Coded Value Domain: Pipeline_LeakSurveyFrequency


assignedhelper1 (Text[50]) – The system user name of the technician who has been assigned to perform the scheduled leak survey inspection of the grid. assignedhelper2 (Text[50]) – The system user name of the technician who has been assigned to perform the scheduled leak survey inspection of the grid. assignedhelper3 (Text[50]) - The system user name of the technician who has been assigned to perform the scheduled leak survey inspection of the grid. remainingfootagemains (Double[16,5]) – The calculated footage of the total remaining active mains within the map grid. remainingservices (Long Integer) – The calculated number of remaining active services within the map grid.

globalid (Global ID)–The systemwide unique identifier. creator (Text[255])–The name of the system user who originally created the object record in the









Line Valve Inspection

The table P_LineValveInspection describes where a line valve inspection was performed in a

Regulator or Town Border Station.

Geometry: None

Relationships:

-UPDMAssembly_P_LineValveInspect

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

manufacturer (Text[50])–The name of the manufacturer of the line valve. Coded Value Domain: Pipeline_ValveManufacturer manufacturecomponent (Text[30])–The manufacturer name/number for the line valve. Coded Value Domain: Pipeline_ValveModel valvetype (Short Integer)–The type of line valve. Coded Value Domain: Pipeline_ValveControllableType figureno (Text[5])–The figure number of the line valve. quantity (Long Integer)–The number of line valves installed. valvediameter (Double)–The size (in inches) of the line valve. Coded Value Domain: Pipeline_ValveDiameter lineconnection (Text[20])–The type of connection the line valve has to the station. Coded Value Domain: Pipeline_LineValveConnection pressure (Long Integer)–The pressure rating of the line valve. pressureunits (Short Integer) – The unit of measure for the pressure of the line valve. Coded Value Domain: Units_For_Pressure valveposition (Short Integer)–The position of the line valve. Coded Value Domain: Pipeline_ValvePosition comments (Text[500])–The documentation of any other details about the line valve. updmassembly_globalid (Guid)–The foreign key value linking the inspection record to the regulator station containing the line valve that was inspected. creator (Text[255])–The name of the system user who originally created the object record in the







This value is automatically populated by the Editor Tracking


Regulator Inspection

The table P_RegulatorInspect describes the annual inspection required for all regulator stations,

border stations, and customer meter sets or stations with a capacity of over 4001 cfh at ½”

differential and other specified stations. The inspection is to make sure that all necessary

equipment is installed and working properly, that the design of the station is as it should be, and

that there are no dangerous or hazardous conditions present. Each station must be examined

annually. This inspection is specifically for the regulators in a regulator station.

Geometry Type: None

Relationships:

-UPDMDevice_P_RegulatorInspect

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

regulatormanufacturer (Text[50])–The manufacturer of the regulator. Coded Value Domain: Pipeline_RegulatorManufacturer regulatormodel (Text[30])–The model name/number of the regulator. Coded Value Domain: Pipeline_RegulatorModel regulatortype (Text[30])–Indicates whether the regulator is operating as a monitor or a controller in the regulator station. Coded Value Domain: Pipeline_RegulatorType regulatordiameter (Double[8,4])–The size, in inches, of the orifice diameter of the regulator. Coded Value Domain: Pipeline_LineDiameterUnknown regulatorconnection (Text[15])–The type of connection on the regulator. Coded Value Domain: Pipeline_PipeConnectionType pressurerating (Integer)–The pressure rating at which the regulator station is qualified. pressureratingunits (Short Integer) – The unit of measurement used to define pressure. Coded Value Domain: Units_For_Pressure pilotmake (Text[20])–The make/type of the pilot. pilotconnectiontype (Text[10])–The type of connection used for the pilot. Coded Value Domain: Pipeline_PilotConnectionType flow (Text[15])–The note stating whether this regulator is the upstream or downstream regulator. Coded Value Domain: Pipeline_Flow intermediatepressure (Long Integer)–The determined and entered intermediate pressure for working monitor applications. outletpressure (Long Integer)–The determined and entered outlet set pressures. If the outlet pressure can get higher than the MAOP downstream, determine that proper safety devices are used. maxinletpressure (Integer)–The determined and entered maximum inlet pressure. minoutletpressure (Integer)–The determined and entered minimum inlet pressure.

internalinspection (Short Integer)–The text column indicating whether internal inspection is to be performed. Coded Value Domain: Yes_No


innervalve (Short Integer)–The text column indicating whether the regulator’s inner valve passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus innervalvediameter (Double[8,4])–The measured internal diameter of the inspected inner valve. Coded Value Domain: Pipeline_LineDiameterUnknown internallockup (Text[15])–The text column indicating whether the lockup passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus internalsetpressure (Short Integer)–The attribute indicating whether the internal set pressure passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus internaldiaphragmposition (Short Integer)–The attribute indicating whether the internal diaphragm passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus internalventposition (Short Integer)–The attribute indicating whether the internal vent position passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus internalpilots (Short Integer)–The attribute indicating whether the internal pilots passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus internalcontrollinesclear (Short Integer)–The attribute indicating whether the internal control lines passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus internalvalvessecured (Short Integer)–The attribute indicating whether the internal valves were secured and thereby passed or failed inspection. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus comments (Text[500])–Any comments or issues as a result of the regulator inspection. globalid (Global ID)–The systemwide unique identifier. updmdevice_globalid (Guid)–The foreign key value linking the inspections record to the regulator being inspected. creator (Text[255])–The name of the system user who originally created the object record in the





Relief Valve Inspection

The set pressure of all separated relief devices (except rupture disks) shall be tested in place any

time the meter set is turned on, changed out, or field tested. Verify the relief capacity using

calculations or flow charts to determine that they have enough capacity to limit the downstream

pressure to the MAOP plus allowable buildup. When calculations are made to verify relief

capacity, keep documentation current showing calculations for audit purposes.

Geometry type: None

Relationships:

-UPDAssemblyDevice_P_ReliefValveInspect

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

manufacturer (Text[50])–The manufacturer of the relief or shutoff valve. Coded Value Domain: Pipeline_ValveManufacturer manufacturecomponent (Text[30])–The manufacturer name/number of the valve. Coded Value Domain: Pipeline_ValveModel valvetype (Text[15])–The type of relief or shutoff valve. internaltoregulator (Short Integer)–The yes/no Boolean value indicating whether the valve is internal to the regulator. Coded Value Domain: Yes_No tokenrelief (Short Integer)–The yes/no Boolean value indicating whether the device uses a token for relief. Coded Value Domain: Yes_No properplacement (Short Integer)–The yes/no Boolean value indicating whether the shutoff device is in the proper place in the setting. Coded Value Domain: Yes_No pressurerating (Short Integer)–The yes/no Boolean value indicating whether the pressure rating is high enough to withstand the maximum pressure to which it will ever be subject. Coded Value Domain: Yes_No innersize (Long Integer)–The diameter of the inner valve. flowcritical (Short Integer)–The yes/no Boolean value indicating whether a loss of service would be critical to the pipe system if the device shuts off the flow. Coded Value Domain: Yes_No safeprotected (Short Integer)–The yes/no Boolean value indicating whether the relief valve itself is in a safe location and has proper protection around it. Coded Value Domain: Yes_No stackcovers (Short Integer)–The yes/no Boolean value indicating whether the relief stack is free of and protected against obstructions. Coded Value Domain: Yes_No setpointpressure (Long Integer)–The proper set point pressure reached when the relief valve(s) will begin to open in case of excessive pressure buildup. devicereaction (Short Integer)–The test to ensure the regulator can pass at maximum pressure conditions without over pressuring the downstream piping or the customer’s equipment in case of failure of the regulator. Test the shutoff valve to the point that it actually shuts off. Coded Value Domain: Pipeline_PassFailStatus


capacitymaop (Integer)–The calculated relief valve maximum allowable operating pressure. updmassembly_globalid (Guid)–The foreign key value linking the inspection record to the pipeline facility containing the valve that was inspected. creator (Text[255])–The name of the system user who originally created the object record in the









Station Visual Inspection

The table P_StationVisualInsp describes the condition of a compressor, pump, regulator, or town

border station that must be visually verified. If a check results in Fail, follow-up activities are

scheduled to remedy the deficiency.

Geometry Type: None

Relationships:

-UPDAssembly_P_StatVisInspect

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

trashweeds (Short Integer)–The check for presence of trash and weeds. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus atmoscorrosion (Short Integer)–The check for presence of atmospheric corrosion. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus paintcondition (Short Integer)–The check for paint condition of the station. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus detectableleaks (Short Integer)–The check for any detectable leaks. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus damagetofacilities (Short Integer)–The check for any damage to the facilities. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus enclosurecondition (Short Integer)–The check for the condition of the station enclosure. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus bolts (Short Integer)–The check for bolts where applicable. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus supportpipingrigid (Short Integer)–The check to ensure the support piping is rigid. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus stationguards (Short Integer)–The check for the condition of the station guards. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus valveboxcondition (Short Integer)–The check for the condition of the valve box. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus warningsignsinplace (Short Integer)–The check to ensure the warning signs are in place. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus globalid (Global ID)–The systemwide unique identifier.

updmassembly_globalid (Guid)–The foreign key value linking the inspection record to the pipeline facility containing the valve that was inspected.


Strainer Inspection

The table P_StrainerInspect describes the equipment inspection performed on the strainers

contained in compressors, pumps, regulators, and town border stations. Inspect the strainer

screens for damage or erosion and clean or replace as necessary. The inspection should occur at

least once each calendar year and at intervals not exceeding 15 months.

Geometry type: None

Relationships:

-UPDMAssembly_P_StrainerInspect

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

strainermanufacturer (Text[50])–The name of the manufacturer of the strainer or filter. Coded Value Domain: Pipeline_StrainerManufacturer strainermodel (Text[30])–The manufacturer name/number of the type of strainer or filter. Coded Value Domain: Pipeline_StrainerModel controllinemanufacturer (Text[50])–The name of the manufacturer of the control line. Coded Value Domain: Pipeline_ControllineManufacturer controllinemodel (Text[30])–The manufacturer name/number of the type of control line. Coded Value Domain: Pipeline_ControllineModel devicetype (Text[15])–The type of device. Coded Value Domain: Pipeline_StrainerDeviceType differentialpressure (Text[15])–The status of the filter cartridges or screens for indication of excessive differential pressure. The default value is Not Inspected. Coded Value Domain: Pipeline_PassFailStatus leaks (Short Integer)–The yes/no Boolean value indicating whether leaks were found during the inspection. Coded Value Domain: Yes_No comments (Text[150])– Any comments or issues as a result of the strainer inspection. globalid (Global ID)–The systemwide unique identifier. updmassembly_globalid (Guid)–The foreign key value linking the inspection record to the strainer that was inspected. creator (Text[255])–The name of the system user who originally created the object record in the









Valve Inspection

The table P_ValveInspection describes the U.S. DOT required inspection of valves. Each

operating location must inspect and perform necessary maintenance on all valves that are

installed in the system to permit sectionalizing or emergency shutoff. Keep a record of all valve

inspections by each location. Each valve must be examined at least once each calendar year and

at intervals not exceeding 15 months.

Geometry Type: None

Relationships:

-UPDMDevice_P_ValveInspect

Subtypes: None

Attachments: Yes

Editor Tracking:







Attributes:

inspectedby (Text[50])–The name of the person who serviced the valves. dateinspected (Date)–The date the valves were serviced. inspectednumber (Text[20])–The unique ID generated by an asset management system to uniquely identify the inspection. systemtype (Short Integer)–The type of system where the valve is installed. The default value is Distribution. Coded Value Domain: Pipeline_Regulatory_Type atmoscorrosion (Short Integer)–The yes/no Boolean value indicating whether atmospheric corrosion was present. Coded Value Domain: Yes_No requirepaint (Short Integer)–The yes/no Boolean value indicating whether the valve requires painting. Coded Value Domain: Yes_No goodcondition (Short Integer)–The yes/no Boolean value indicating whether the valve is working properly and in good condition. Coded Value Domain: Yes_No requirelubrication (Short Integer)–The yes/no Boolean value indicating whether the valve requires lubrication. Coded Value Domain: Yes_No lubricated (Short Integer)–The yes/no Boolean value indicating whether the valve was lubricated. Coded Value Domain: Yes_No tagged (Short Integer)–The yes/no Boolean value indicating whether the valve was tagged properly. Coded Value Domain: Yes_No operating (Short Integer)–The yes/no Boolean value indicating whether the valve is operating correctly. Coded Value Domain: Yes_No secured (Short Integer)–The yes/no Boolean value indicating whether the valve is secured from unauthorized access. Coded Value Domain: Yes_No accessible (Short Integer)–The yes/no Boolean value indicating whether the valve is accessible. Coded Value Domain: Yes_No


signs (Short Integer)–The yes/no Boolean value indicating whether signs are present and current. Coded Value Domain: Yes_No valveboxcond (Short Integer)–The yes/no Boolean value indicating whether the valve box is in good condition. Coded Value Domain: Yes_No protectfromdamage (Short Integer)–The yes/no Boolean value indicating whether the valves are protected from accidental damage by vehicular traffic. Coded Value Domain: Yes_No reviewedby (Text[50])–The name of the supervisor or designated person who reviewed the valve maintenance record. revieweddate (Date)–The date the valve maintenance record was reviewed. comments (Text[500])–Any pertinent information. globalid (Global ID)–The systemwide unique identifier. UPDMDevice_globalid (Guid])–The foreign key value linking the inspection record to the valve that was inspected.










ArcGIS Pipeline Referencing The ArcGIS Pipeline Referencing (APR) system is a set of tools provided by Esri to create and maintain

the spatial relationship between event features such as those listed in the “Integrity” section of this

document and the linear referenced routes upon which they are located.

Historically, most pipeline operators have used linear referencing to reference the location of event data

such as anomalies or issues identified during a pigging run. This is especially the case for historical

pipeline event information created pre-GPS era and before the engineering industry leveraged GPS into

its practices. APR is unique in that it offers the ability to continue management of this location

information with the industry practices established prior to the widespread adoption of GPS for data

collection. And it supports the new methods for locating pipeline data in the GIS that is more relevant to

the GPS era.

The feature classes and table objects listed in this section are to help with the management of the

information required to maintain the ArcGIS Pipeline Referencing system. If the ArcGIS Pipeline

Referencing tools are not planned to be used to manage any of the UPDM featureclasses, than the

featureclasses listed in this section can be removed from the geodatabase.

Calibration Point

ArcGIS Pipeline Referencing

Centerline Centerline_Sequence Continuous Network

Engineering Network Redline


Calibration Point

The point featureclass P_Calibration_Point stores points representing locations along a pipeline

centerline route where the route measure is explicitly defined.

GeometryType: Point with Z enabled (m is disabled)

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


measure (Double[12,4])–The measure value to be stored on routes in a linear referencing

system (LRS) network. This value is assigned by the ArcGIS Pipeline Referencing tools.

fromdate (Date)–The date when the calibration point became active. This value is assigned by


todate (Date)–The date when the calibration point is retired. This value is assigned by the ArcGIS


routeid (Text [38])–The unique identifier for the target route. This value is assigned by the


networkid (Short Integer)–The unique identifier of the LRS network. This value is assigned by the


globalid (Global ID)–The systemwide unique identifier. This is the primary key value for

relationships to associated components.

creator (Text[255])–The name of the system user who originally created the feature record in


creationdate (Date)–The date and time the feature record was originally created in the



feature record in the geodatabase. This value is automatically populated by the Editor Tracking.

lastupdate (Date)–The date and time the feature record was last modified in the geodatabase.



Centerline

The polyline feature class P_Centerline provides a single source of geometry for all linear

referencing system networks. Every record represents a single range of the pipe system with

continuous stationing along the pipe centerline. Centerlines typically go from start of the pipe to

the end of the pipe, or an equation point where the stationing is reset.

Starting at ArcGIS release 10.7.1 it is possible to replace the Centerline featureclass with the

PipelineLine featureclass of the Utility Network.

GeometryType: Polyline with Z enabled (m is disabled)

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


centerlineid (GUID)–The unique ID for the centerline geometry. This value is assigned by the













Centerline Sequence

The table P_Centerline_Sequence is a cross-reference table to define the many-to-many

relationship between centerlines and routes. One centerline feature can participate in many

routes and a route is typically made up of more than one centerlines. This table is only required

if the ArcGIS Linear Referencing for Pipeline Tools are being utilized.

GeometryType: Table

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


fromdate (Date)–The date when the centerline sequence record was placed into operation. This

value is assigned by the ArcGIS Pipeline Referencing tools.

todate (Date)–The date when the centerline sequence record was retired from operation. This


routeid (Text [38])–The unique ID for the route. This value is assigned by the ArcGIS Pipeline

Referencing tools.

centerlineid (GUID)–The unique ID for the centerline geometry. This value is assigned by the


networkid (Short Integer)–The unique ID for the ALRP network in which each route participates.










Continuous Network

The polyline feature class P_ContinuousNetwork is for storing pipeline routes defined using the

Continuous Measure method of managing linear referencing information. If the Continuous

Measure method for managing linear referencing information is not used, then this feature class

is not required for the ArcGIS Pipeline Referencing tools.

GeometryType: Polyline with Z and M enabled

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:



Referencing tools.

routename (Text [100])–The user defined name for the route. This is an optional value.
















Engineering Network

The polyline feature class P_EngineeringNetwork is for storing pipeline routes defined using the

Engineering Stationing Measure method of managing linear referencing information. If the

Engineering Stationing method for managing linear referencing information is not used, then

this feature class is not required for the ArcGIS Pipeline Referencing tools.

GeometryType: Polyline with Z and M enabled

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:



Referencing tools.


lineid (TEXT [38])–The unique ID for a collection of contiguous route segments. This is often

referred to as a line loop in the pipeline industry. This value is assigned by the ArcGIS Pipeline

Referencing tools.

linename (Text [100])–The user-defined name for the line loop. This is an optional value.

orderid (Long Integer)–The sequence number of the route segment within a line loop. This value

is assigned by the ArcGIS Pipeline Referencing tools.









creationdate (Date)–The date and time the feture record was originally created in the







Redline

The polyline feature class P_Redline is for storing desired modifications to the linear referencing

network. The redline feature can be thought of as a placeholder for a future route editing

operation. It is used as a markup feature so that LRS event editors don't have to be LRS route

editors. This feature class is a core schema component for the ArcGIS Pipeline Referencing tools.

GeometryType: Polyline (Z is disabled) (M is disabled)

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


effectivedate (Date) – Date the reoute changes becomes effective. This date will be applied to

events affected by the change.

networkid (Short Integer)–The unique ID for the ALRP network in which each route participates.


Referencing tools.

activitytype (Short Integer) – Type of change being made, for example, Realign Route, Extend

Route, and so on.


frommeasure (Double[38,8])–The measure location along the engineering network ROUTEID

specified route where the start of the linear event is located. This value is automatically


tomeasure (Double[38,8])–The measure location along the ROUTEID specified route where the

completion of the linear event is located. This value is automatically generated and populated

by the ArcGIS Pipeline Referencing tools.



creator (Text [50])–The name of the system user who originally created the feature record in the


creationdate (Date)–The date and time when the feature record was originally created in the


lastupdate (Date)–The date and time when the feature record was last modified in the


updatedby (Text [50])–The name of the system user responsible for the last modification to the



Maintenance Maintenance is the activity an organization undertakes to keep the pipe system in production. In the

process of maintaining the system, additional information is often discovered or captured. The feature

classes listed in this section represent those layers that are not considered part of the organization’s

inspection program but are part of the organization’s maintenance program.

Gas Leaks

Maintenance

Identified Issue Leak Repair Squeeze Off Coupon


Coupon

The point feature class P_Coupon describes the location where a sample of the pipe is cut from

the metal pipe to determine the extent of internal corrosion. A coupon is typically extracted as

part of an exposed pipe inspection.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:

percentofgraph (Double[8,5])–The percent of graphitization.

wallthickness (Double[16,6])–The thickness of the pipe wall as measured from the extracted

coupon.

creator (Text [50])–The name of the system user who originally created the feature record in the








globalid (Global ID)–The global unique identifier of the coupon record.


Gas Leaks

The point feature class P_GasLeaks describes the identified location where natural gas is escaping the contained system. This is a field data collection activity commonly performed by a gas utility’s operations staff. The field investigation process will result in the verification of the presence of leaking gas. This is typically a singular location where the concentration of recorded methane is the greatest. Related information such as follow-up LeakInspections, Leak Sniff points, and the eventual Leak Repair are also commonly collected as part of the leak management process. The purpose of this feature class is to track the core leak data over the life cycle of the leak.

GeometryType: Point with M and Z-values enabled

Relationships:

-P_GasLeak_GasLeakInspection

-P_LeakRepair_GasLeak

Subtypes: Yes (LeakCause)

Subtype Code Subtype Description

0 Unknown

1 Incorrect Operations

2 Material or Welds

3 Manufacturing

4 Construction

5 Equipment

6 Natural Forces

7 Corrosion

8 Other Outside Force

Damage

9 Excavation Damage

10 Other


Attachments: Yes

Editor Tracking:







Attributes:


leakcause (Long Integer) - The official reported cause of the gas leak. The list of possible causes

is consistent with U.S. DOT annual report classifications.

leakcausetype (Text[50]) – The subptye specific cause of the gas leak.

Coded Value Domain: Subtype specific.

leakstatus (Text[15]) - The current status of the leak. The default value is Active.

Coded Value Domain: Pipeline_LeakClosedStatus

timereported (Date) – The date and time when the gas leak was reported to the gas company.

timedispatched (Date) – The date and time when gas company staff were dispatched to the

location of the gas leak.

timearrived (Date) – The date and time when gas company staff arrived at the location of the gas

leak.

timemadesafe (Date) – The date and time when gas company staff were able to make the gas

leak safe.

address (Text[100])–The house number, street name, and city name closest to the location

where the leak was reported, for example, 123 E. Main St, Apple Valley.

locationdescription (Text[250])–Additional information to aid a gas field technician in identifying

the location where the original leak was determined to have occurred.

gasin (Text[25]) – The location where the leaking gas was discovered.

Coded Value Domain: Pipeline_LeakInspectGasIn

originalleakclass (Short Integer)–The classification by the gas field technician of the type of leak.


methoddetected (Text[20])–The method used by the gas field technician to identify the location

and concentration of leaking gas.

Coded Value Domain: Pipeline_LeakMethodDetected

gasmeasurement (Double[10,4]) - The highest concentration of methane gas recorded by the

gas field technician while investigating the reported leak.


gasmeasurementunits (Short Integer) – The units of measurement used to determine the

volume of leaking gas.

Coded Value Domain: Pipeline_MeasurementUnits

surfacetype (Text[20])–The type of ground surface at the location determined by the gas field

technician.


probablesource (Text[25]) – The pipeline asset which is most likely to have been the source of

the leaking gas.


revisedleakclass (Short Integer)–The classification approved by the gas operations supervisor as

to the type of leak.


revisedleakdate (Date)–The date and time the gas supervisor revised the leak class.

revisedleaksupervisor (Text[50])–The name of the gas supervisor who approved the revision of

the leak class.

reportableincident (Short Integer)–The yes/no Boolean value indicating whether the reported

leak meets the DOT 191.3 requirement as a reportable incident.


dotreportedindicator (Short Integer)–The yes/no Boolean value indicating whether the reported

leak has been reported to the U.S. DOT.


federallandindicator (Short Integer)–The yes/no Boolean value indicating whether the reported

leak was on federal government land.


duedate (Date) —The date the gas leak is next due for inspection. duedate is calculated by adding the frequency value to the timemadesafe. compdate (Date) —The compliance date is the calculated date when the gas leak is out of

compliance. The compliance date is calculated by adding the frequency value plus the grace

period to the timemadesafe.


frequency (Short Integer) – The duration as measured in days when the gas leak is required to

be inspected next.

eventid (Text[38])–The unique ID for each gas leak event record. This value is automatically


fromdate (Date)–The date the gas leak event became active on the route. This value is


todate (Date)–The date the gas leak event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the gas leak is


tools.

engm (Double)–The measure location along the route where the gas leak is located. This value is




wanting to maintain the P_GasLeaks features as event records with the ArcGIS Pipeline

Referencing tools.




Referencing tools.




Referencing tools.






organizations wanting to maintain the P_GasLeaks features as event records with the ArcGIS






P_GasLeaks features as event records with the ArcGIS Pipeline Referencing tools.



P_GasLeaks features as event records with the ArcGIS Pipeline Referencing tools.



Referencing tools.

creator (Text [255])–The name of the system user who originally created the feature record in










Identified Issue

The point feature class P_IdentifiedIssue describes pipe system anomalies that were identified

by the field technician. Some examples of identified issues are corrosion, damaged meter, and

dead vegetation.

GeometryType: Point

Relationships: No

Subtypes: No

Attachments: Yes

Editor Tracking:







Attributes:


issue (Text[50])–The type of issue identified by the field technician.

Coded Value Domain: Pipeline_IdentifiedIssue

datereported (Date)–The date the field technician identified the issue.

reportedby (Text[50])–The name of the field technician who identified the issue.

comments (Text[255])–Additional information provided by the field technician about the

identified issue.



geodatabase.




populated.



populated.


eventid (Text[38])–The unique ID for each identified issue event record. This value is


fromdate (Date)–The date the identified issue event became active on the route. This value is


todate (Date)–The date the identified issue event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the identified

issue is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.




wanting to maintain the P_IdentifiedIssue features as event records with the ArcGIS Pipeline

Referencing tools.

engm (Double)–The measure location along the route where the identified issue is located. This





Referencing tools.




Referencing tools.






organizations wanting to maintain the P_IdentifiedIssue features as event records with the





P_IdentifiedIssue features as event records with the ArcGIS Pipeline Referencing tools.



P_IdentifiedIssue features as event records with the ArcGIS Pipeline Referencing tools.



Referencing tools.




Leak Repair

The line feature class P_LeakRepair describes the extent of pipe that an organization has decided to “fix” in response to an identified leak. This often results in the replacement of a section of pipe. Therefore, this record is modeled as a line feature to allow for the extent of repair to be captured.

GeometryType: Polyline with m and z-values enabled

Relationships:

-Leak_P _LeakRepair

Subtypes: No

Attachments: Yes

Editor Tracking:







Attributes:


leakrepairtype (Text[30])–The type of repair made to resolve the leak. The default value is

Permanent.

Coded Value Domain: Pipeline_LeakRepairType

repairedby (Text[50])–The name of the field technician who was responsible for the repair to the

pipe system and compiled the information for this record.

daterepaired (Date)–The date and time the leak repair was completed.

damagetype (Text[30])–The type of damage to the pipe system asset that resulted in the leak.

Coded Value Domain: Pipeline_ExcavDamageType

leaklocation (Text[30])–The location in the pipe system of the origination of the leak.

Coded Value Domain: Pipeline_LeakLocation

workperformed (Text[30])–The type of work performed to repair the identified leak.

Coded Value Domain: Pipeline_LeakWorkPerformed

soilatpipedepth (Text[20])–The type of predominant soil at the depth of the buried asset.

Coded Value Domain: Pipeline_SoilType

surfacetype (Text[20])–The predominant surface type at the location where the leak repair

occurred.


measuredlength (Double[16,5])–The length of pipe repaired. This is only applicable to leaks that

occurred on pipe segments.

GasLeak_globalid (Guid) – The globalid value of the GasLeak for which the leak repair was

performed.



geodatabase.




eventid (Text[38])–The unique ID for each pipe segment record. This attribute is only used by

organizations wanting to maintain the P_LeakRepairs features as event records with the ArcGIS



fromdate (Date)–The date the linear event became active on the route. This attribute is only

used by organizations wanting to maintain the P_LeakRepairs features as event records with the



todate (Date)–The date the linear event was retired from the route. This attribute is only used

by organizations wanting to maintain the P_LeakRepairs features as event records with the





P_LeakRepairs features as event records with the ArcGIS Pipeline Referencing tools. The value is


engfromm (Double)–The measure location along the engineering network engrouteid specified


organizations wanting to maintain the P_LeakRepairs features as event records with the ArcGIS





the P_LeakRepairs features as event records with the ArcGIS Pipeline Referencing tools. The



networks.

engroutename (Text[100])—The continuous network name that is automatically created and


wanting to maintain the P_LeakRepairs features as event records with the ArcGIS Pipeline

Referencing tools.

engtom (Double)–The measure location along the engrouteid or engtorouteid specified route





Referencing tools.




Referencing tools.




Referencing tools.

continfromm (Double)—The continuous network beginning measure along the derived route ID.


attribute is only used by organizations wanting to maintain the P_LeakRepairs features as event


contintom (Double)—The continuous network ending measure along the derived route ID. This


attribute is only used by organizations wanting to maintain the P_LeakRepairs features as event




This attribute is only used by organizations wanting to maintain the P_LeakRepairs features as




to maintain the P_LeakRepairs features as event records with the ArcGIS Pipeline Referencing




maintain the P_LeakRepairs features as event records with the ArcGIS Pipeline Referencing




This attribute is only used by organizations wanting to maintain the P_LeakRepairs features as













P_LeakRepairs features as event records with the ArcGIS Pipeline Referencing tools. The value is











Squeeze Off

The point feature class P_SqueezeOff describes the location where a squeeze off tool was

applied to a polyethylene pipe (Plastic PE). Squeeze off tools are used in operation and

emergency situations where the flow through the pipe needs to be temporarily restricted. The

purpose of tracking where squeeze offs have been performed on the plastic pipe is to ensure

that a single location on the pipe is not subject to the repeated material stress.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:





squeezeoffdate (Date)–The date the squeeze off operation occurred.

symbolrotation (Double[8,4])–The numerical value indicating the number of degrees the

compressor station should be rotated in a map display. This is typically done to have the symbol

match the orientation of the associated pipe segments.



geodatabase.

Coded Domain: Pipeline_Spatial Accuracy


in the geodatabase.


the geodatabase.

eventid (Text[38])–The unique ID for each squeeze off event record. This value is automatically


fromdate (Date)–The date the squeeze off event became active on the route. This value is


todate (Date)–The date the squeeze off event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the squeeze off is


tools.



wanting to maintain the P_SqueezeOff features as event records with the ArcGIS Pipeline

Referencing tools.


engm (Double)–The measure location along the route where the squeeze off is located. This





Referencing tools.




Referencing tools.






organizations wanting to maintain the P_SqueezeOff features as event records with the ArcGIS





P_SqueezeOff features as event records with the ArcGIS Pipeline Referencing tools.



P_SqueezeOff features as event records with the ArcGIS Pipeline Referencing tools.



Referencing tools.





Environment Utility and pipeline companies are committed to ensuring that they do not adversely impact air, water,

land quality, wildlife, aquatic species, plant life, and sensitive habitats. Knowing about the world around

them is key to informing utility and pipeline activities at every stage of a pipe network’s life cycle. The

feature classes in this section provide information about the environment in the vicinity of the pipe

system.

Drinking Water

Environment

Ecological Area Elevation High Populated Area

Navigable Waterway

Other Populated Area

Outside Area

Structure Footprint

Structure Point


Drinking Water

The polygonal feature class P_DrinkingWater describes U.S. drinking water resources, as defined

at 49 CFR 195.6, that constitute a hazardous liquids pipeline high consequence area (HCA). CFR

195.6 defines a drinking water resource area as those locations where a community water

system or a nontransient, noncommunity water system obtains its drinking water and does not

have an adequate alternative drinking water source.

GeometryType: Polygon

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


drinkingwatername (Text[50])–The name of the drinking water resource.

drinkingwatertype (Text[50])–The text value indicating the drinking water resource’s

classification. Valid values are water intake, source water protection area, or sole source aquifer

recharge area.

status (Short Integer)–The text value indicating the state of the drinking water resource and

whether it qualifies as an HCA.

Coded Value Domain: Pipeline_ObjectStatus_Integrity

discoverydate (Date)–The date the drinking water resource was identified.

source (Text[50])–The entity and data product name from which knowledge of the drinking

water resource became known.

description (Text[255])–The textual description of the location of the drinking water resource.









globalid (Global ID)–The systemwide unique identifier. This is the primary key for relationships

to system components.


Ecological Area

The polygonal feature class P_EcologicalArea describes U.S. locations, as defined at 49 CFR

195.6, that constitute a hazardous liquids pipeline high consequence area (HCA) by reason of

being an ecological area. CFR 195.6 defines an ecological area as an area that is unusually

sensitive to environmental damage from a hazardous liquid pipeline release. Types of ecological

areas include areas containing a critically imperiled species or ecological community, a

multispecies assemblage area, and a migratory water bird concentration area.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


areaname (Text[50])–The name of the ecological area.

ecologicalareatype (Text[50])–The text value indicating the classification of the location

pursuant to 49 CFR 195.6(b).

status (Text[20])–The text value indicating the status of the ecological area for HCA purposes.


discoverydate (Date)–The date the ecological area was identified.

source (Text[50])–The entity and data product name from which knowledge of the ecological

area became known.

description (Text[255])–The textual description of the location of the ecological area.












Elevation

The point feature class P_Elevation describes surface height information at a discrete location.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


featureelevation (Double[12,4])–The measured vertical distance to the top of a physical object

from a common reference such as mean sea level.

groundelevation (Double[12,4])–The measured vertical distance of the surface from a common

reference such as mean sea level.

waterelevation (Double[12,4])–The measured vertical distance of the surface or top of the water

body from a common reference such as mean sea level.

measurementunits (Short Integer) – The units of measure used for determining elevation.


measurementdate (Date)–The date the measurements were captured.

eventid (Text[38])–The unique ID for each elevation event record. This value is automatically


fromdate (Date)–The date the elevation event became active on the route. This value is


todate (Date)–The date the elevation event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the elevation is


tools.

engroutename (Text[100])—The engineering network route name where the point event is

located. This event route name is automatically created and maintained by the ArcGIS Pipeline


P_Elevation features as event records with the ArcGIS Pipeline Referencing tools.

engm (Double)–The measure location along the engineering network route where the elevation

is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.




wanting to maintain the P_Elevation features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100])—The continuous network route name where the point event is



P_Elevation features as event records with the ArcGIS Pipeline Referencing tools.

continm (Double—The continuous network measure along the continrouteid route. This value is

automatically created and maintained by the ArcGIS Pipeline Referencing tools.



This attribute is only used by organizations wanting to maintain the P_Elevation features as



reflocation (Text[50])–The location of the offsetting feature. This can be Coordinates,


maintain the P_Elevation features as event records with the ArcGIS Pipeline Referencing tools.


refoffset(Text[50])–The offset measure. This attribute is only used by organizations wanting to

maintain the P_Elevation features as event records with the ArcGIS Pipeline Referencing tools.




Referencing tools.










High Populated Area

The polygonal feature class P_HighPopulatedArea describes U.S. locations, as defined at 49 CFR

195.450, that constitute a hazardous liquids pipeline high consequence area (HCA) by reason of

being highly populated. CFR 195.450 defines a highly populated area as a Census Bureau

delineated urbanized area that has 50,000 or more people and a population density of at least

1,000 people per square mile.


Relationships: N/A

Subtypes: No

Attachments: Yes

Editor Tracking:







Attributes:


areaname (Text[50])–The name of the populated area.

areatype (Text[50])–The type of highly populated area.

status (Text[20])–The entity and data product name from which knowledge of the highly

populated area became known.


discoverydate (Date)–The date the highly populated area was defined.

source (Text[50])–The entity and data product name from which knowledge of the highly


description (Text[255])–The textual description of the location of the highly populated area.










Navigable Waterway

The polygonal feature class P_NavigableWaterway describes U.S. locations, as defined at 49 CFR

195.450, that constitute a hazardous liquids pipeline high consequence area (HCA). CFR 195.450

defines a navigable waterway as a water body with a substantial likelihood of commercial

navigation.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


waterwayname (Text[50])–The name of the commercially navigable waterway.

waterwaytype (Text[30])–The text value indicating the classification of the waterway.

status (Text[20])–The text value indicating the state of qualification as a commercially navigable

waterway for HCA purposes.

Coded Value Domain: ObjectStatus_Integrity

discoverydate (Date)–The date the commercially navigable waterway was identified.

source (Text[50])–The entity and data product name from which knowledge of the navigable

waterway became known.

description (Text[255])–The textual description of the location of the navigable waterway.












Other Populated Area

The polygonal feature class P_OtherPopulatedArea describes U.S. locations, as defined by 49

CFR 195.450, that constitute other populated area hazardous liquids pipeline high consequence

area (HCA). CFR 195.450 defines “other populated area” as a Census Bureau-delineated area

that contains a concentrated population such as an incorporated or unincorporated city, town,

village or other designated residential or commercial area.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


populatedareaname (Text[50])–The Census Bureau-defined name for the populated area.

type (Text[50])–The type of other populated area.

status (Text[20])–The text value indicating the state of qualification of the other populated area

for HCA purposes.


occupantcount (Short Integer)–The Census Bureau-defined count of the occupants within the

populated area.

discoverydate (Date)–The date the other populated area was defined.

source (Text[50])–The entity and data product name from which knowledge of the other


description (Text[255])–The textual description of the location of the other populated area.












Outside Area

The polygonal feature class P_OutsideArea describes U.S. locations, as defined by 49 CFR

192.903, that constitute an identified site for gas transmission pipeline high consequence area

(HCA) determination purposes. CFR 195.903 defines an “outside area” as an area or open

structure that is occupied by 20 or more persons at least 50 days in any 12-month period.

Examples include beaches, playgrounds, recreational facilities, camping grounds, outdoor

theaters, and stadiums.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes


status (Text[20])–The text value indicating whether the location currently qualifies as an outside

area for HCA purposes.


identifiedsite (Short Integer)–The yes/no Boolean value indicating whether the outside area

represents an identified site.


identifiedsitetype (Text[30])–The categorical type of outside area for the identified type.

Coded Value Domain: Pipeline_IdentifiedSiteOutside

daysperweek (Short Integer)–The number of days per week the outside area is occupied.

Range Domain: Pipeline_DaysPerWeek_Integrity

weeksperyear (Short Integer)– The number of weeks per year when the outside area is

occupied.

Range Domain: Pipeline_WeeksPerYear_Integrity

impairedmobility (Short Integer)–The yes/no Boolean value indicating whether the outside area

qualifies as an area with persons of impaired mobility.


gatheringplace (Short Integer)–The yes/no Boolean value indicating whether the outside area is

considered a gathering place.


discoverydate (Date)–The date the outside area was identified.

source (Text[50])–The entity and data product name from which knowledge of the outside area

became known.

description (Text[255])–The textual description of the location of the outside area.






Structure Footprint

The polygonal feature class P_StructureFootprint describes U.S. locations, as defined by 49 CFR

192.903, that constitute a human occupied building for gas transmission pipeline high

consequence area (HCA) determination purposes. This feature class can also be used to

determine building counts near the pipeline for DOT pipe classification as defined under 49 CFR

192.5. This polygonal representation of the structure provides an outline of the structure’s two-

dimensional footprint.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


structurename (Text[50])–The commonly known name of the structure.

structuretype (Text[30])–The categorical type of human occupied structure.

Coded Value Domain: Pipeline_StructureType

structurestatus (Text[20])–The text value indicating whether the location currently qualifies as a

structure for HCA purposes.

Coded Value Domain: Pipeline_ObjectStatus

humanoccupancy (Short Integer)–The yes/no Boolean value indicating whether the structure is

suitable for human occupancy.


daysperweek (Short Integer)–The number of days per week that the structure is occupied.

Range Domain: Pipeline_DayPerWeek

limitedmobility (Short Integer)–The yes/no Boolean value indicating whether the structure

contains persons with limited ability to evacuate in emergency situations.


limitedmobilityreason (Text[50])–The reason why the persons in the structure have limited

mobility.

Coded Value Domain: Pipeline_StructureLimitedMobility

impairedmobility (Short Integer)–The yes/no Boolean value indicating whether the structure

contains persons with impaired ability to evacuate in emergency situations.


gatheringplace (Short Integer)–The yes/no Boolean value indicating whether the structure is



discoverydate (Date)–The date the structure was identified.

source (Text[50])–The entity and data product name from which knowledge of the structure

became known.

occupantcount (Short Integer)–The number of persons typically in the structure.


numberofstories (Short Integer)–The number of aboveground levels of the structure.

numberofunits (Short Integer)–The number of individual human-occupied units in the structure.

weeksperyear (Short Integer)–The number of weeks per year that the structure is occupied.

Range Domain: Pipeline_WeeksPerYear

description (Text[255])–The textual description of the location of the structure.

identifiedsite (Short Integer)–The yes/no Boolean value indicating whether the structure is

identified as a high consequence area.


identifiedsitetype (Text[50])–The categorical type of identified site.





geodatabase.











Structure Point

The point feature class P_StructurePoint describes U.S. locations, as defined by 49 CFR 192.903,

that constitute a human-occupied building for gas transmission pipeline high consequence area

(HCA) determination purposes. This feature class can also be used to determine building counts

near the pipeline for DOT pipe classification as defined by 49 CFR 192.5. This point

representation of the structure defines the location of the building closest to the pipeline.

GeometryType: Point features

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


structurename (Text[50])–The commonly known name of the structure.

structuretype (Text[30])–The categorical type of human-occupied structure.

Coded Value Domain: Pipeline_StructureType

structurestatus (Text[20])–The text value indicating whether the location currently qualifies as a

structure for HCA purposes.


humanoccupancy (Short Integer)–The yes/no Boolean value indicating whether the structure is

suitable for human occupancy.


daysperweek (Short Integer)–The number of days per week that the structure is occupied.

Range Domain: Pipeline_DayPerWeek

limitedmobility (Short Integer)–The yes/no Boolean value indicating whether the structure

contains persons with limited ability to evacuate in emergency situations.


limitedmobilityreason (Text[50])–The reason why the persons in the structure have limited

mobility.

Coded Value Domain: Pipeline_StructureLimitedMobility

impairedmobility (Short Integer)–The yes/no Boolean value indicating whether the structure

contains persons with impaired ability to evacuate in emergency situations.


gatheringplace (Short Integer)–The yes/no Boolean value indicating whether the structure is



discoverydate (Date)–The date the structure was identified.

source (Text[50])–The entity and data product name from which knowledge of the structure

became known.

occupantcount (Short Integer)–The number of persons typically in the structure.


numberofstories (Short Integer)–The number of aboveground levels of the structure.

numberofunits (Short Integer)–The number of individual human-occupied units in the structure.

weeksperyear (Short Integer)–The number of weeks per year that the structure is occupied.

Range Domain: Pipeline_WeeksPerYear

description (Text[255])–The textual description of the location of the structure.

identifiedsite (Short Integer)–The yes/no Boolean value indicating whether the structure is

identified as a high consequence area.


identifiedsitetype (Text[50])–The categorical type of identified site.



geodatabase.


gpsx(Double)—The longitudinal coordinate of the feature when it was originally included in the

geodatabase.

gpsy (Double)—The latitudinal coordinate of the feature when it was originally included in the

geodatabase.



eventid (Text[38])–The unique ID for each structure point event record. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the structure

point is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.

fromdate (Date)–The date the structure point event became active on the route. This value is


todate (Date)–The date the structure point event was retired from the route. This value is





Referencing tools.

engrouteid (Text[38])–The unique ID of the engineering network route where the structure


Referencing tools.

engm (Double)–The measure location along the route where the structure point is located. This




wanting to maintain the P_StructurePoint features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_StructurePoint features as event records with the ArcGIS Pipeline

Referencing tools.






organizations wanting to maintain the P_StructurePoint features as event records with the





P_StructurePoint features as event records with the ArcGIS Pipeline Referencing tools.



P_StructurePoint features as event records with the ArcGIS Pipeline Referencing tools.




Inline Inspection Inline inspection (ILI) employing smart pigs is used to assess the integrity of pipelines from the inside of

the pipe. The data recorded by the smart pig is retrieved for analysis and reporting and is a critical

component of ongoing pipeline integrity programs. Some of this information is required by federal and

state regulations. Other data is needed to understand the state of the gas system. The information

defined in this section will help manage the inline inspection data to ensure the relativity and integrity

of the pipeline.

ILI Ground Reference

Markers

Inline Inspection

ILI Inspection

Range

ILI Survey

Group

ILI Survey

Readings

Inline

Inspection


ILI Ground Ref Markers

The point feature class P_ILIGroundRefMarkers describes reference markers in the pipeline

system as detected from inline inspection (ILI) runs of a pigging device.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


markertype (Text[50])–The text value indicating the type of marker detected. Valid values are

AGR Timer Box, AGR Valve, Monument, Crossing, and Other.

Coded Value Domain: Pipeline_ILISurveyMarkerType

altreference (Text[50])–The alternative reference of the feature detected from inline inspection.

chainagesource (Text[50])–The source of the chainage distance recorded from inline inspection.

location (Text[50])–The textual description of the feature location detected from inline

inspection.

offset (Double)–The perpendicular linear distance of the marker from the pipeline.

offsetunits (Text[50])–The unit of measure for offset.


referencenumber (Text[50])–The reference number assigned to the feature detected from inline

inspection.

rundistance (Double[12,4])–The run distance of the feature detected by the pigging device.

description (Text[255])–The textual description of the feature detected from inline inspection.

inspectionrange_globalid (Guid)–The inspection range feature class column containing the

matching primary key value for relationships to associated components.


eventid (Text[38])–The unique ID for each inline inspection ground reference marker event

record. This value is automatically generated and populated by the ArcGIS Pipeline Referencing

tools.

fromdate (Date)–The date the inline inspection ground reference marker event became active

on the route. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.


todate (Date)–The date the inline inspection ground reference marker event was retired from

the route. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.

engrouteid (Text[38])–The unique ID of the engineering network route where the inline

inspection ground reference marker is located. This value is automatically generated and

populated by the ArcGIS Pipeline Referencing tools.



wanting to maintain the P_ILIGroundRefMarkers features as event records with the ArcGIS


engm (Double)–The measure location along the engineering route where the inline inspection

ground reference marker is located. This value is automatically generated and populated by the






continroutename (Text[100])—he continuous network name that is automatically created and









organizations wanting to maintain the P_ILIGroundRefMarkers features as event records with




P_ILIGroundRefMarkers features as event records with the ArcGIS Pipeline Referencing tools.





P_ILIGroundRefMarkers features as event records with the ArcGIS Pipeline Referencing tools.



Referencing tools.










ILI Inspection Range

The polyline feature class P_ILIInspectionRange describes the length or range of inline inspection

(ILI) performed on a pipe segment. ILI of a transmission pipeline may be broken into sections

(P_InlineInspections) due to the length of the pipeline and where the pigging device can be

inserted and retrieved.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


startodo (Double[16,5])–The odometer reading on the pigging device at the start of the ILI run.

endodo (Double[16,5])–The odometer reading on the pigging device at the end of the ILI run.

sequence (Long Integer)–The numeric order that determines the sequence of multiple ILI run

ranges that constitute an entire ILI run for a given pipeline.

comments (Text[255])–Additional description of the ILI run.

inlineinspectionid (Guid)–The inline inspection feature class column containing the matching

primary key value for relationships to associated components.

inspectionyear (Short Integer)–The year the ILI run occurred.

corrosionmetallosscheck (Short Integer)–The yes/no Boolean value indicating whether metal

loss due to corrosion is checked.


dentdeformationcheck (Short Integer)–The yes/no Boolean value indicating whether formation

of dents is checked.


cracklongseamdefectcheck (Short Integer)–The yes/no Boolean value indicating whether a crack

or long seam defect is checked.


otherinspectioncheck (Short Integer)–The yes/no Boolean value indicating whether another

inspection is also performed along with ILI.


otherinspectiontype (Text[50])–The description of inspection type if OTHER INSPECTION CHECK

is performed.


eventid (Text[38])–The unique ID for each ILI inspection range record. This value is automatically

generated and populated by the ArcGIS Pipeline Referencing tools


fromdate (Date)–The date the ILI inspection range event became active on the route. This value


todate (Date)–The date the ILI inspection range was retired from the route. This value is






linear event is located. The event route name is automatically created and maintained by the


maintain the P_ILIInspectionRange features as event records with the ArcGIS Pipeline

Referencing tools.


route where the beginning of the linear event is located. This value is automatically generated





Referencing (ALRP) as continuous networks.


the linear event is located. The event route name is automatically created and maintained by



Referencing tools.

engtom (Double)–The measure location along the engtorouteid specified route where the





wanting to maintain the P_ILIInspectionRange features as event records with the ArcGIS Pipeline

Referencing tools.




wanting to maintain the P_ILIInspectionRange features as event records with the ArcGIS Pipeline

Referencing tools.

continfromm (Double)—The continuous network beginning measure along the derived route ID.


attribute is only used by organizations wanting to maintain the P_ILIInspectionRange features as


contintom (Double)—The continuous network ending measure along the derived route ID. This


attribute is only used by organizations wanting to maintain the P_ILIInspectionRange features as




This attribute is only used by organizations wanting to maintain the P_ILIInspectionRange




to maintain the P_ILIInspectionRange features as event records with the ArcGIS Pipeline








This attribute is only used by organizations wanting to maintain the P_ILIInspectionRange













P_ILIInspectionRange features as event records with the ArcGIS Pipeline Referencing tools. The



ILI Survey Group

The point feature class P_ILISurveyGroup represents a set of anomalies in the pipeline system as detected from inline inspection runs of a pigging device. The group or cluster is identified by a particular cluster rule. Each cluster represents a location on the pipeline with a specified length and width. The purpose behind the ILISurveyGroup feature class is to allow analysis of clustered anomalies

(of similar types) discovered during an inline pig run. The relationship between ILISurveyGroup

and ILISurveyReadings models that an anomaly point can be a member of a cluster of like

anomalies.


Relationships:

-P_ILISurvGroup_P_ILISurveyReading

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


ilisurveygrouptype (Text[30])–The text value indicating the type of cluster of ILI readings. Valid

values are Metal Loss, Crack, Mechanical Damage, Material Defect, and ILI Other.

Coded Value Domain: Pipeline_ILISurveyType

anomalycount (Long Integer)–The numeric count of anomalies in the cluster.

reldistance (Double[12,5])–The relative distance of the feature detected from the ILI run.

rundistance (Double[12,5])–The run distance recorded by the pigging device for the feature

detected from inline inspection.

safetyfactor (Double[12,5])–The pressure safety factor as designated for the ILI run.

maxdepthpercent (Double[12,4])–The maximum depth as a percentage of the wall thickness for

the cluster of anomaly point features.

maxdepth (Double[12,5])–The maximum depth of the cluster of anomaly point features.

maxdepthunits (Text[50])–The unit of measure for depth.


grouplength (Double[12,5])–The length of the cluster of anomaly point features.

groupwidth (Double[12,5])–The width of the cluster of anomaly point features.

grouparea (Double[12,5])–The area of the cluster of anomaly point features.

bprcalculatedaveragE (Double[12,5])–The mean back pressure ratio calculated for a set of

anomaly point features.

bprpigaverage (Double[12,5])–The mean back pressure ratio as determined by the pigging

device for a set of anomaly point features.

bprvarianceaverage (Double[12,5])–The mean variance between calculated back pressure ratio

and pig back pressure ratio for a set of anomaly point features recorded by an inline pig run.

rprcalculatedaverage (Double[12,5])–The calculated mean rupture pressure ratio for a set of



rprpigaverage (Double[12,5])–The mean rupture pressure ratio as determined by the pigging

device for a set of anomaly point features.

rprvarianceaverage (Double[12,5])–The mean variance between calculated rupture pressure

ratio and pig rupture pressure ratio for a set of anomaly point features recorded by an inline pig

run.

widthaverage (Double[12,5])–The average width of the cluster of anomaly point features.

lengthaverage (Double[12,5])–The average length of the cluster of anomaly point features.

depthaverage (Double[12,5])–The average depth of the cluster of anomaly point features.

maxdiameteraverage (Double[12,5])–The maximum average diameter of the cluster of anomaly

point features.

mindiameteraverage (Double[12,5])–The minimum average diameter of the cluster of anomaly

point features.

orientationaverage (Double[12,5])–The mean angular position of the cluster of anomaly point

features.

r85burstpressure (Double[12,5])–The burst pressure ratio determined using the R85 method.

eventid (Text[38])–The unique ID for each inline inspection survey group event record. This


fromdate (Date)–The date the inline inspection survey group event became active on the route.

This value is automatically generated and populated by the ArcGIS Pipeline Referencing tools.

todate (Date)–The date the inline inspection survey group event was retired from the route. This



inspection survey group is located. This value is automatically generated and populated by the


engroutename (Text[100])—The engineering network route name that is automatically created


organizations wanting to maintain the P_ILISurveyGroup features as event records with the



engm (Double)–The measure location along the engineering route where the inline inspection

survey group is located. This value is automatically generated and populated by the ArcGIS




wanting to maintain the P_ILISurveyGroup features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_ILISurveyGroup features as event records with the ArcGIS Pipeline

Referencing tools.





This attribute is only used by organizations wanting to maintain the P_ILISurveyGroup features




maintain the P_ILISurveyGroup features as event records with the ArcGIS Pipeline Referencing




maintain the P_ILISurveyGroup features as event records with the ArcGIS Pipeline Referencing




Referencing tools.






ILI Survey Readings

The point feature class P_ILISurveyReadings describes anomalies in the pipeline system as

detected from inline inspection runs of a pigging device. Typical anomalies include corrosion,

geometric distortions, and material defects such as gouges or dents.


Relationships:

-ILISurvGroup_P_ILISurveyReading

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


surveytype (Text[30])–The text value indicating the type of anomaly detected by the ILI run.

Valid values are Metal Loss, Crack, Mechanical Damage, Material Defect, and ILI Other.

Coded Value Domain: Pipeline_ILISurveyType

featurecode (Long Integer)–The feature code designation for the ILI reading.

reldistance (Double[12,5])–The relative distance of the feature detected from the ILI run.

rundistance (Double[12,5])–The run distance recorded by the pigging device for the feature

detected from inline inspection.

defectororientation (Long Integer)–The angular position of the anomaly feature reading.

depth (Double[12,5])–The depth of the anomaly feature reading.

depthunits (Text[20])–The unit of measure for depth.


length (Double)–The length of the anomaly feature reading.

lengthunits (Short Integer) – The unit of measurement for the length of the anomaly.


longseamorientation (Long Integer)–The angular position of the longitudinal seam detected by

the pigging device.

wallthickness (Double[12,5])–The wall thickness of the pipe at the anomaly feature reading.

width (Double)–The width of the anomaly feature reading.

widthunits (Short Integer) – The unit of measurement of the width of the anomaly.


deepestpointdegrees (Long Integer)–The angular position of the deepest point at the anomaly

feature reading.

clusterno (Long Integer)–The numeric count of the anomaly features.


clusterrpr (Double[12,5])–The rupture pressure ratio at the anomaly features.

pigrpr (Double[12,5])–The rupture pressure ratio as determined by the pigging device.

remainingwt (Double[12,5])–The pipe wall thickness remaining at the anomaly feature reading.

intextindicator (Text[10])–The text value indicating if the anomaly position is internal or

external. Valid values are internal, external, or unknown.

Coded Value Domain: Pipeline_ILISurveyExtIndicator

usagmdistance (Double[12,5])–The distance from current anomaly to the nearest AGM

upstream on the pipeline.

usagmreference (Text[50])–The reference identifier of the nearest AGM to the anomaly

upstream on the pipeline.

dsagmdistance (Double[12,5])–The distance from the current anomaly to the nearest AGM

downstream on the pipeline.

dsagmreference (Text[50])–The reference identifier of the nearest AGM to the anomaly

downstream on the pipeline.

erf (Double[12,5])–The pipe estimated repair factor (ERF) at the anomaly.

bpr (Double[12,5])–The pipe back pressure ratio at the anomaly.

longitude (Double[12,8])–The longitude reading at the anomaly.

latitude (Double[12,8])–The latitude reading at the anomaly.

ilisurveygroup_globalid (Guid)–The ILI survey group feature class column containing the


inspectionrange_globalid (Guid)–The inspection range feature class column containing the



eventid (Text[38])–The unique ID for each inline inspection survey reading event record. This



fromdate (Date)–The date the inline inspection survey reading event became active on the

route. This value is automatically generated and populated by the ArcGIS Pipeline Referencing

tools.

todate (Date)–The date the inline inspection survey reading event was retired from the route.

This value is automatically generated and populated by the ArcGIS Pipeline Referencing tools.


inspection survey reading is located. This value is automatically generated and populated by the


engroutename (Text[100])—The engineering route name that is automatically created and


wanting to maintain the P_ILISurveyReadings features as event records with the ArcGIS Pipeline

Referencing tools.

engm (Double)–The measure location along the route where the inline inspection survey

reading is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.




Referencing tools.




Referencing tools.





This attribute is only used by organizations wanting to maintain the P_ILISurveyReadings




maintain the P_ILISurveyReadings features as event records with the ArcGIS Pipeline





maintain the P_ILISurveyReadings features as event records with the ArcGIS Pipeline




Referencing tools.










Inline Inspection

The polyline feature class P_InlineInspection describes the length or range of a single inline

inspection event on a pipe segment. Multiple inline inspections can be grouped together as

inline inspection ranges.


Relationships: No

Subtypes: No

Attachments: Yes

Editor Tracking:







Attributes:


startdate (Date)–The start date of the ILI run.

enddate (Date)–The end date of the ILI run.

ilivendor (Text[50])–The survey vendor performing the ILI run.

tooltype (Text[50])–The type of pigging device used for the ILI run.

startodo (Double[16,5])–The odometer reading on the pigging device at the start of the ILI run.

endodo (Double[16,5])–The odometer reading on the pigging device at the end of the ILI run.

comments (Text[255])–Additional description of the ILI run.

eventid (Text[38])–The unique ID for each inline inspection record. This value is automatically


fromdate (Date)–The date the inline inspection event became active on the route. This value is


todate (Date)–The date the inline inspection was retired from the route. This value is





engroutename (Text[100])—The engineering route name where the beginning of the linear

event is located. The event route name is automatically created and maintained by the ArcGIS


P_InlineInspection features as event records with the ArcGIS Pipeline Referencing tools.









engtoroutename (Text[100])—The engineering route name where the completion of the linear

event is located. The event route name is automatically created and maintained by the ArcGIS


P_InlineInspection features as event records with the ArcGIS Pipeline Referencing tools.






wanting to maintain the P_InlineInspection features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_InlineInspection features as event records with the ArcGIS Pipeline

Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_InlineInspection




attribute is only used by organizations wanting to maintain the P_InlineInspection features as




This attribute is only used by organizations wanting to maintain the P_InlineInspection features




to maintain the P_InlineInspection features as event records with the ArcGIS Pipeline





maintain the P_InlineInspection features as event records with the ArcGIS Pipeline Referencing




This attribute is only used by organizations wanting to maintain the P_InlineInspection features












P_InlineInspection features as event records with the ArcGIS Pipeline Referencing tools. The












Integrity Once a gas or oil pipe system has been constructed and put into production, it is the organization’s

responsibility to maintain the system as a safe and reliable transportation system. Ensuring that a pipe

system is safe and reliable requires a significant amount of data. Some of this information is required by

federal and state regulations. Other data is needed to understand the state of the pipe system. The

information defined in this section is to manage the data collected to ensure that the production pipe

system is safe and reliable.

Anomaly

Integrity

Anomaly Group

Centerline Accuracy

Consequence Segment

Could Affect Segment

DA Survey Readings

DOT Class Elevation HCA Segment High Consequence Area

MAOP Calculated Range

Operating Pressure Range

Pipe Crossing Pipe Exposure Test Pressure Range


Anomaly

The point feature class P_Anomaly describes deficiencies in the pipeline system as detected from inline inspection runs of a pigging device. Typical anomalies include corrosion, geometric distortions, and material defects such as gouges or dents. GeometryType: Point with z- and m-values enabled

Relationships:

-AnomalyGroup_P_Anomaly

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


inspectiondate (Date)–The date of inspection.

anomalytype (Text[50])–The text value indicating the type of an anomaly. Valid values are

external corrosion, internal corrosion, dent, or gouge.

Coded Value Domain: Pipeline_AnomalyType

anomalystatus (Text[20])–The text value indicating the status of an anomaly. Valid values are

previously excavated, proposed, postponed, pending review, in progress, scheduled, and

unknown.

Coded Value Domain: Pipeline_AnomalyStatus

priority (Text[10])–The text value indicating the priority of an anomaly. Valid values are

immediate, scheduled, monitored, and unknown.

Coded Value Domain: Pipeline_AnomalyPriority

severity (Text[20])–The text value indicating the severity of an anomaly. Valid values are high,

medium, and low.

Coded Value Domain:Pipeline_ AnomalySeverity

dateclosed (Date)–The date of closing an anomaly.

location (Text[255])–The textual description of the location of an anomaly.

depth (Double[8,3])–The depth to an anomaly from ground surface.

length (Double[8,3])–The length of an anomaly.

width (Double[8,3])–The width of an anomaly.

maximumdiameter (Double[8,3])–The maximum diameter of the pipe segment at an anomaly.

minimumdiameter (Double[8,3])–The minimum diameter of the pipe segment at an anomaly.

orientation (Text[5])–The angular position of an anomaly on a pipe cross section.

ovality (Double[8,3])–The measure of the ovality of the pipe segment at an anomaly.


recommendedremediation (Text[40])–The text value indicating the recommended remediation

for an anomaly. Valid values are composite sleeve, coupling reinforcement, full encirclement

weld, pipe cutout, saddle sleeve, welded sleeve, and unknown.

Coded Value Domain: Pipeline_AnomalyRemediation

rprcalculated (Double[12,3])–The calculated rupture pressure ratio.

rprpig (Double[12,3])–The rupture pressure ratio recorded by an inline pig run.

rprvariance (Double[12,3])–The variance between calculated rupture pressure ratios and

rupture pressure ratios recorded by an inline pig run.

depthofcovermin (Double[12,3])–The minimum depth of cover recommended.

depthofcovermax (Double[12,3])–The maximum depth of cover recommended.

bprcalculated (Double[12,3])–The calculated back pressure ratio.

bprpig (Double[12,3])–The back pressure ratio recorded by an inline pig run.

bprvariance (Double[12,3])–The variance between calculated back pressure ratios and pig back

pressure ratios recorded by an inline pig run.

anomalygroup_globalid (Guid)–The foreign key value used to relate an anomaly record to the

related anomaly group.

eventid (Text[38])–The unique ID for each event record. This value is automatically generated


fromdate (Date)–The date the event became active on the route. This value is automatically


todate (Date)–The date the event was retired from the route. This value is automatically




Referencing tools.

engrouteid (Text[38])–The unique ID of the engineering network route where the event is


tools.


engroutename (Text[100])—The engineering network route name that is automatically created


organizations wanting to maintain the P_Anomaly features as event records with the ArcGIS


engm (Double[16,5])–The measure location along the engineering route where the event is


tools.



wanting to maintain the P_Anomaly features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_Anomaly features as event records with the ArcGIS Pipeline

Referencing tools.





This attribute is only used by organizations wanting to maintain the P_Anomaly features as




maintain the P_Anomaly features as event records with the ArcGIS Pipeline Referencing tools.




maintain the P_Anomaly features as event records with the ArcGIS Pipeline Referencing tools.





Anomaly Group

The point feature class P_AnomalyGroup represents a set of anomalies in the pipeline system as detected from inline inspection runs of a pigging device. The record contains mean (average) values for a set of anomaly point features. The purpose of the AnomalyGroup feature class is to allow analysis of clustered anomalies (of

similar types) discovered during an inline pig run. The relationship between Anomaly and

AnomalyGroup models that an anomaly point can be a member of a cluster of like anomalies.

GeometryType: Point with m- value enabled

Relationships:

-P_AnomalyGroup_Anomaly

-P_InspRange_AnomalyGroup

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


status (Text[15])–The text value indicating the life cycle state of the object. Valid values are

conceptual, proposed, active, inactive, and unknown.


bprcalculatedaverage (Double[12,5])–The mean back pressure ratio as calculated for a set of


bprpigaverage (Double[12,5])–The mean back pressure ratio for a set of anomaly point features

recorded by an inline pig run.

bprvarianceaverage (Double[12,5])–The mean variance between calculated back pressure ratios

and pig back pressure ratios recorded for a set of anomaly point features.

depthaverage (Double[8,4])–The mean depth for a set of anomaly point features from ground

surface.

lengthaverage (Double[8,4])–The mean length of a set of anomaly point features.

widthaverage (Double[8,4])–The mean width of a set of anomaly point features.

maxdiameteraverage (Double[8,4])–The mean maximum diameter of the pipe segment at a set

of anomaly point features.

mindiameteraverage (Double[8,4])–The mean minimum diameter of the pipe segment at a set

of anomaly point features.

orientationaverage (Text[5])–The mean angular position of a set of anomaly point features on a

pipe cross section.

rprcalculateaverage (Double[8,4])–The mean rupture pressure ratio for a set of anomaly point

features

rprpigaverage (Double[8,4])–The mean rupture pressure ratio for a set of anomaly point

features recorded by an inline pig run.

rprvarianceaverage (Double[8,4])–The mean variance between calculated rupture pressure

ratios and pig rupture pressure ratios recorded for a set of anomaly point features.


inspectionrange_globalid (Guid)–The foreign key value used to relate an anomaly group record

to the related inspection range.

eventid (Text[38])–The unique ID for each anomaly group event record. This value is


fromdate (Date)–The date the anomaly group event became active on the route. This value is


todate (Date)–The date the anomaly group event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the anomaly

group is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_AnomalyGroup features as event records with the ArcGIS Pipeline

Referencing tools.

engm (Double[16,5])–The measure location along the engineering route where the anomaly

group is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.




Referencing tools.




Referencing tools.





This attribute is only used by organizations wanting to maintain the P_AnomalyGroup features





maintain the P_AnomalyGroup features as event records with the ArcGIS Pipeline Referencing




maintain the P_AnomalyGroup features as event records with the ArcGIS Pipeline Referencing




Referencing tools.












Centerline Accuracy

The polyline feature class P_CenterlineAccuracy describes the spatial accuracy of the location of

the centerline of the transmission pipe in relation to its actual location on the earth. This is

proposed required information for the National Pipeline Mapping System (NPMS).


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


spatialaccuracy (Short Integer) – An estimation of the spatial accuracy of the placement of the

transmission pipe centerline.


eventid (Text[38])–The unique ID for each consequence segment record. This value is

automatically generated and populated by the ArcGIS Pipeline Referencing tools

fromdate (Date)–The date the consequence segment event became active on the route. This


todate (Date)–The date the consequence segment was retired from the route. This value is








P_CenterlineAccuracy features as event records with the ArcGIS Pipeline Referencing tools.









the linear event is located. The event will be automatically created and maintained by the


maintain the P_CenterlineAccuracy features as event records with the ArcGIS Pipeline

Referencing tools.







wanting to maintain the P_CenterlineAccuracy features as event records with the ArcGIS




wanting to maintain the P_CenterlineAccuracy features as event records with the ArcGIS




tools. This attribute is only used by organizations wanting to maintain the P_CenterlineAccuracy




attribute is only used by organizations wanting to maintain the P_CenterlineAccuracy features as




This attribute is only used by organizations wanting to maintain the P_CenterlineAccuracy




to maintain the P_CenterlineAccuracy features as event records with the ArcGIS Pipeline








This attribute is only used by organizations wanting to maintain the P_CenterlineAccuracy













P_CenterlineAccuracy features as event records with the ArcGIS Pipeline Referencing tools. The











Consequence Segment

The polyline feature class P_ConsequenceSegment describes the segments derived from an HCA

calculation or assignment.


Relationships: no

Subtypes: Yes (Method)

Subtype

Code

Subtype Description

0 Installed (Default)

1 Calculated

2 Approved

Attachments: No

Editor Tracking:







Attributes:





habitablebuildingcount (Long Integer)–The number of structures intended for human occupancy

that created the individual HCA segment.

calculatedlength (Double[8,4])–The length of an individual consequence segment.

datecalculated (Date)–The date and time the consequence segment was originally calculated.

maop (Double[12,3])–The maximum allowable operating pressure used for the consequence

segment calculation.

pir (Double[12,3])–The potential impact radius of the consequence segment from the HCA

calculation.

pirfactor (Double)–A tolerance factor to account for variation in spatial data accuracy of the

features used to determine whether a segment is HCA.

type (Text[40])–The type of HCA on the pipe segment. Valid values are class 3 or 4 designation,

identified site, sliding circle, sliding circle and class designation, sliding circle and identified site,

engineering assessment, and unknown.

Coded Value Domain: Pipeline_HCAProvenance

consequencearea_globalid (Guid)–The foreign key value used to relate a consequence segment

record to the associated consequence area.

method (Long Integer)–The feature class subtype that defines the technique used to describe

the consequence segment. Valid subtypes are installed, calculated, and approved.

outsidediameter (Double)–The edge-to-edge measured length of a straight line through the

center of the pipe segment.

consequenceareatype (Text[30])–The U.S. federal classification of whether the consequent is

classified as a high consequence segment or a medium consequence segment.

Coded Value Domain: Pipeline_ConsequenceAreaType


regulatorytype (Short Integer)–The text value indicating whether the consequence segment is

considered a Distribution, Transmission, or Gathering pipe.


eventid (Text[38])–The unique ID for each consequence segment record. This value is


fromdate (Date)–The date the consequence segment event became active on the route. This


todate (Date)–The date the consequence segment was retired from the route. This value is








maintain the P_ConsequenceSegment features as event records with the ArcGIS Pipeline

Referencing tools.


route where the beginning of the linear event is located. This value is automatically generated










Referencing tools.







wanting to maintain the P_ConsequenceSegment features as event records with the ArcGIS




wanting to maintain the P_ConsequenceSegment features as event records with the ArcGIS




tools. This attribute is only used by organizations wanting to maintain the

P_ConsequenceSegment features as event records with the ArcGIS Pipeline Referencing tools.



attribute is only used by organizations wanting to maintain the P_ConsequenceSegment features




This attribute is only used by organizations wanting to maintain the P_ConsequenceSegment




to maintain the P_ConsequenceSegment features as event records with the ArcGIS Pipeline








This attribute is only used by organizations wanting to maintain the P_ConsequenceSegment













P_ConsequenceSegment features as event records with the ArcGIS Pipeline Referencing tools.












Could Affect Segment

The polyline feature class P_CouldAffectSegment is intended to store the results of liquids HCA

analysis. The P_CouldAffectSegment features represent pipeline segments that could affect a

high consequence area.


Relationships: no

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:





intersectiontype (Text[50])–The text value indicating the type of intersection with an HCA that

determined the could affect segment. Valid values are direct, indirect, and potential.

Coded Value Domain: Pipeline_CouldAffectIntersection

couldaffectsegmenttype (Text[50])–The text value indicating the type of HCA that determined

the could affect segment. Valid values are high population, other population, ecological area,

drinking water, and navigable waterway.

Coded Value Domain: Pipeline_CouldAffectType

eventid (Text[38])–The unique ID for each could affect segment record. This value is


fromdate (Date)–The date the could affect segment event became active on the route. This


todate (Date)–The date the could affect segment was retired from the route. This value is








maintain the P_CouldAffectSegment features as event records with the ArcGIS Pipeline

Referencing tools.













Referencing tools.






wanting to maintain the P_CouldAffectSegment features as event records with the ArcGIS




wanting to maintain the P_CouldAffectSegment features as event records with the ArcGIS





P_CouldAffectSegment features as event records with the ArcGIS Pipeline Referencing tools.



attribute is only used by organizations wanting to maintain the P_CouldAffectSegment features




This attribute is only used by organizations wanting to maintain the P_CouldAffectSegment




to maintain the P_CouldAffectSegment features as event records with the ArcGIS Pipeline









This attribute is only used by organizations wanting to maintain the P_CouldAffectSegment












P_CouldAffectSegment features as event records with the ArcGIS Pipeline Referencing tools. The












DA Survey Readings

The point feature class P_DASurveyReadings is intended to store survey readings collected from

a direct assessment (DA).


Relationships: no

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


datype (Text[50])–The text value indicating the type of direct assessment performed. Valid

values are close interval potential survey, direct current voltage gradient, pipeline current

mapper, pearson survey, and alternate current voltage gradient.

Coded Value Domain: Pipeline_DASurveyType

inspectiondate (Date)–The date and time of the DA inspection.

pson (Double[12,6])–The value number indicating PS on.

psoff (Double[12,6])–The value number indicating PS off.

staticon (Double[12,6])–The value number indicating Static on.

staticoff (Double[12,6])–The value number indicating Static off.

dcpotentialvolts (Double[8,4])–The value number indicating direct current (DC) potential

voltage.

acpotentialvolts (Double[8,4])–The value number indicating alternating current (AC) potential

voltage.

pcmcurrent (Double[12,6])–The value number indicating PCM current.

irpercent (Double[12,6])–The value number indicating IR percent.

eventid (Text[38])–The unique ID for each DA survey reading event record. This value is


fromdate (Date)–The date the DA survey reading event became active on the route. This value is


todate (Date)–The date the DA survey reading event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the DA survey

reading is located. This value is automatically generated and populated by the ArcGIS Pipeline

Referencing tools.





P_DASurveyReadings features as event records with the ArcGIS Pipeline Referencing tools.

engm (Double[16,5])–The measure location along the route where the DA survey reading is


tools.



wanting to maintain the P_DASurveyReadings features as event records with the ArcGIS Pipeline

Referencing tools.



wanting to maintain the P_DASurveyReadings features as event records with the ArcGIS Pipeline

Referencing tools.





This attribute is only used by organizations wanting to maintain the P_DASurveyReadings




maintain the P_DASurveyReadings features as event records with the ArcGIS Pipeline




maintain the P_DASurveyReadings features as event records with the ArcGIS Pipeline




Referencing tools.


Document Point

The point feature class P_DocumentPoint is intended to store points that are used to link one or

more external documents to a location. P_DocumentPoint features can be used to annotate

(with supporting documents) features that are not explicitly defined in the geodatabase.


Relationships: No

Subtypes: No

Attachments: Yes

Editor Tracking:







Attributes:


documenttype (Text[30])–The text value indicating the type of document. Valid values are

Adobe Acrobat (.pdf), AutoCAD drawing (.dwg), bitmap (.bmp), GIF (.gif), HTML (.htm), JPEG

(.jpg), Microsoft Excel (.xls), Microsoft Word (.doc), text (.txt), TIFF (.tif), and MicroStation

drawing (.dgn).

Coded Value Domain: Pipeline_DocumentType

documentdescription (Text[255])–The textual description of the document.

eventid (Text[38])–The unique ID for each document point event record. This value is


fromdate (Date)–The date the document point event became active on the route. This value is


todate (Date)–The date the document point event was retired from the route. This value is


engrouteid (Text[38])–The unique ID of the engineering network route where the document


Referencing tools.




P_DocumentPoint features as event records with the ArcGIS Pipeline Referencing tools.

engm (Double[16,5])–The measure location along the engineering network route where the

document point is located. This value is automatically generated and populated by the ArcGIS




wanting to maintain the P_DocumentPoint features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100])—The continuous network name where the point event is located.

This event route name is automatically created and maintained by the ArcGIS Pipeline



P_DocumentPoint features as event records with the ArcGIS Pipeline Referencing tools.





This attribute is only used by organizations wanting to maintain the P_DocumentPoint features




maintain the P_DocumentPoint features as event records with the ArcGIS Pipeline Referencing




maintain the P_DocumentPoint features as event records with the ArcGIS Pipeline Referencing




Referencing tools.












DOT Class

The polyline feature class P_DOTClass describes the segments indicating the calculated or

assigned Department of Transportation Office of Pipeline Safety class designations. This is an

important designation of the pipe segment that defines and determines how this is treated and

maintained for operational as well as regulatory practice.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


classtype (Short Integer)–The type of DOT class determined on the pipe segment. Valid values

are Class 1, Class 2, Class 3, and Class 4.

Coded Value Domain: Pipeline_DOTClassType

classsource (Text[20])–The text value indicating the source of DOT class determined. Valid

values are calculated, manual, unknown (verified), and unknown.

Coded Value Domain: Pipeline_DOTClassSource

classlength (Double[16,4])–The length of an individual DOT segment.

corridorwidth (Double[12,4])–The corridor width of an individual DOT segment.

datecalculated (Date)–The date and time the DOT segment was originally calculated.

eventid (Text[38])–The unique ID for each DOT class record. This value is automatically


fromdate (Date)–The date the DOT class event became active on the route. This value is


todate (Date)–The date the DOT class was retired from the route. This value is automatically





engroutename (Text[100])—The engineering network name where the beginning of the linear

event is located. This event route name is automatically created and maintained by the ArcGIS


P_DOTClass features as event records with the ArcGIS Pipeline Referencing tools.









engtoroutename (Text[100])—The engineering network name where the completion of the

linear event is located. This event route name is automatically created and maintained by the


maintain the P_DOTClass features as event records with the ArcGIS Pipeline Referencing tools.






wanting to maintain the P_DOTClass features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100])—The continuous network name where the linear event is located.



P_DOTClass features as event records with the ArcGIS Pipeline Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_DOTClass features




attribute is only used by organizations wanting to maintain the P_DOTClass features as event




This attribute is only used by organizations wanting to maintain the P_DOTClass features as




to maintain the P_DOTClass features as event records with the ArcGIS Pipeline Referencing









This attribute is only used by organizations wanting to maintain the P_DOTClass features as












P_DOTClass features as event records with the ArcGIS Pipeline Referencing tools. The value is













High Consequence Area

The polygon feature class P_HighConsequenceArea describes the extent of the HCA for the pipe

segment.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:





hcatype (Text[25])–The text value indicating the type of high consequence area. Valid values are

20 or more persons, DOT Class 3, DOT Class 4, and limited mobility.

Coded Value Domain: Pipeline_HCAAreaType

consequenceclass (Text[10])–The text value indicating the class type designation of HCA. Valid

values are 1, 2, 3, and 4.

Coded Value Domain: Pipeline_DOTClassType

comments (Text[255])–The nonstructured information about the HCA.











MAOP Calculated Range

The polyline feature class P_MAOPCalcRange describes the length or range of an MAOP

calculation for the pipe system.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


pressureestablishedby (Text[50])–The text value indicating the method of establishing MAOP.

Valid values are design, certificate, grandfather, special permit, pressure type, other, unknown,

operator assigned, and historical.

Coded Value Domain: Pipeline_MAOPPressureEstabBy

documentmaturityindex (Text[50])–The text value rating the quality of documentation

supporting the MAOP. Valid values are high, medium, and low.

Coded Value Domain: Pipeline_DocumentMaturityIndex

maopdesign (Double[12,4])–The maximum allowable operating pressure as defined during

design.

maoptest (Double[12,4])–The tested maximum allowable operating pressure during installation.

maoprecord (Double[12,4])–The maximum allowable operating pressure under which the pipe

segment is currently operating.

maopunitofmeasure (Short Integer)–The unit of measure for defining MAOP.


eventid (Text[38])–The unique ID for each MAOP calculation range record. This value is


fromdate (Date)–The date the MAOP calculation range event became active on the route. This


todate (Date)–The date the MAOP calculation range was retired from the route. This value is








maintain the P_MAOPCalcRange features as event records with the ArcGIS Pipeline Referencing

tools.









engroutename (Text[100])—The engineering network route name where the completion of the




tools.






wanting to maintain the P_MAOPCalcRange features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100])—The continuous network name where the linear event is located.



P_MAOPCalcRange features as event records with the ArcGIS Pipeline Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_MAOPCalcRange




attribute is only used by organizations wanting to maintain the P_MAOPCalcRange features as





This attribute is only used by organizations wanting to maintain the P_MAOPCalcRange features




to maintain the P_MAOPCalcRange features as event records with the ArcGIS Pipeline








This attribute is only used by organizations wanting to maintain the P_MAOPCalcRange features












P_MAOPCalcRange features as event records with the ArcGIS Pipeline Referencing tools. The









Operating Pressure Range

The polyline feature class P_OperatingPressureRange describes the length or range of operating

pressure for the pipe system.


Relationships: no

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


pressuretype (Text[50])–The text value indicating the type of operating pressure. Valid values

are design, certificate, grandfather, special permit, pressure type, other, unknown, operator

assigned, and historical.

Coded Value Domain: Pipeline_MAOPPressureEstabBy

pressurevalue (Double[12,4])–The value of operating pressure.

unitofmeasure (Short Integer)–The unit of measure defining the operating pressure.


dateassigned (Date)–The date and time the pressure value was assigned to the pipe system.

eventid (Text[38])–The unique ID for each operating pressure range record. This value is


fromdate (Date)–The date the operating pressure range event became active on the route. This


todate (Date)–The date the operating pressure range was retired from the route. This value is








maintain the P_OperatingPressureRange features as event records with the ArcGIS Pipeline

Referencing tools.




engtorouteid (Text 38])–The unique ID of the engineering network route where the completion






the linear event is located. This event route name is automatically created and maintained by



Referencing tools.






wanting to maintain the P_OperatingPressureRange features as event records with the ArcGIS


continroutename (Text[100])—The continuous network route name where the linear event is



P_OperatingPressureRange features as event records with the ArcGIS Pipeline Referencing tools.







attribute is only used by organizations wanting to maintain the P_OperatingPressureRange




This attribute is only used by organizations wanting to maintain the P_OperatingPressureRange




to maintain the P_OperatingPressureRange features as event records with the ArcGIS Pipeline









This attribute is only used by organizations wanting to maintain the P_OperatingPressureRange
























Pipe Crossing

The polyline feature class P_PipeCrossing describes the length of pipe segment that is

intersected by another feature such as a road, river, and so on. Every pipeline company must

track these types of features for right-of-way purposes, ownership purposes, and DOT and FERC

safety regulations.

GeometryType: Polyline with M and Z values enabled

Relationships:

-PipeCrossing_P_CrossingInspect

Subtypes: Yes (CrossingType)

Subtype Code Subtype Description

0 Unknown

1 Pipe Utility (Default)

2 Wire Utility

3 Transportation

4 Topographic

Attachments: No

Editor Tracking:







Attributes:




Coded Value Domain: Pipeline_Object Status

crossingtype (Long Integer)–The subtype indicating the category of a crossing as pipe utility,

topographic, transportation, or wired utility.

crossingfeaturetype (Text[50])–The text value indicating the specific feature type of the crossing.

Coded Value Domain: Subtype specific domains

crossinglocation (Text[10])–The text value indicating the location of the crossing relative to the

pipeline.

Coded Value Domain: Pipeline_PipeCrossingLocation

lineclearance (Double[8,3])–The value indicating the clearance between the crossing and

pipeline.

easementwidth (Double[8,3])–The value indicating the width of the easement of the crossing.

depthofpipe (Double[8,3])–The value indicating the depth of the pipeline at the crossing

intersection.

depthunits (Short Integer) – The unit of measurement used to determine the depth.


depthofcrossingfeature (Double[8,3])–The value indicating the depth of the crossing at the

pipeline intersection.

comments (Text[1000])–The nonstructured information about the crossing.



geodatabase.


eventid (Text[38])–The unique ID for each pipe crossing record. This value is automatically



fromdate (Date)–The date the pipe crossing event became active on the route. This value is


todate (Date)–The date the pipe crossing was retired from the route. This value is automatically








maintain the P_PipeCrossing features as event records with the ArcGIS Pipeline Referencing

tools.








engroutename (Text[100])—The engineering network route name where the completion of the




tools.






wanting to maintain the P_PipeCrossing features as event records with the ArcGIS Pipeline

Referencing tools.





P_PipeCrossing features as event records with the ArcGIS Pipeline Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_PipeCrossing




attribute is only used by organizations wanting to maintain the P_PipeCrossing features as event




This attribute is only used by organizations wanting to maintain the P_PipeCrossing features as




to maintain the P_PipeCrossing features as event records with the ArcGIS Pipeline Referencing








This attribute is only used by organizations wanting to maintain the P_PipeCrossing features as













P_PipeCrossing features as event records with the ArcGIS Pipeline Referencing tools. The value is












Pipe Exposure

The polyline feature class P_PipeExposure describes the length or range of the pipe system that

is exposed to the atmosphere.


Relationships:

-P_InspRange_PipeExposure

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


lengthexposed (Double[12,4])–The length of pipe exposed to the atmosphere.

lengthunits (Short Integer) – The units of measure used for determined the length of pipe

exposed.


locationdescription (Text[50])–The textual description of the location where the regulator

station is located.

inspectionrange_globalid (Global ID)–The inspection range feature class column containing the


eventid (Text[38])–The unique ID for each pipe exposure record. This value is automatically


fromdate (Date)–The date the pipe exposure event became active on the route. This value is


todate (Date)–The date the pipe exposure event was retired from the route. This value is








maintain the P_PipeExposure features as event records with the ArcGIS Pipeline Referencing

tools.













tools.






wanting to maintain the P_PipeExposure features as event records with the ArcGIS Pipeline

Referencing tools.


located. The event route name is automatically created and maintained by the ArcGIS Pipeline


P_PipeExposure features as event records with the ArcGIS Pipeline Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_PipeExposure




attribute is only used by organizations wanting to maintain the P_PipeExposure features as




This attribute is only used by organizations wanting to maintain the P_PipeExposure features as




to maintain the P_PipeExposure features as event records with the ArcGIS Pipeline Referencing





















P_PipeExposure features as event records with the ArcGIS Pipeline Referencing tools. The value













Pipeline Marker

The point feature class P_PipelineMarker an above ground structure used to indicate the

location of the buried pipe system.


Relationships:

-None

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:





installationdate (Date)—The date the installation of the marker was completed.

markercondition (Text[30]) – The general observed condition of the pipeline marker.

owner (Text[50]) – The name of the organization responsible for the pipeline marker.

dateinspected (Date) The date of the last inspection of the pipeline marker.

insepctedby (Text[50]) – The name of the person who performed the last inspection.

nextinspectiondate (Date) – The date when the next inspection is scheduled to be completed.

inspectionduedate (Date) – The date when the next inspection id required to be completed.

Inspectionfrequency (Short Integer) – The interval measured in months required for inspections.


number under which the work order was issued to install the pipeline marker.


project number under which the work order was issued to install the pipeline marker.

assetunitcode (Text[38])—The foreign key value used to link this record to the asset’s corresponding record in the asset management system.

rotation (Short Integer)—The numerical value indicating the number of degrees the compressor

station should be rotated in a map display. This is typically done to have the symbol match the





geodatabase.





populated.



populated.

eventid (Text[38])–The unique ID for each pipe exposure record. This value is automatically


fromdate (Date)–The date the pipe exposure event became active on the route. This value is


todate (Date)–The date the pipe exposure event was retired from the route. This value is









tools.












tools.







wanting to maintain the P_PipeExposure features as event records with the ArcGIS Pipeline

Referencing tools.




P_PipeExposure features as event records with the ArcGIS Pipeline Referencing tools.



tools. This attribute is only used by organizations wanting to maintain the P_PipeExposure




attribute is only used by organizations wanting to maintain the P_PipeExposure features as








to maintain the P_PipeExposure features as event records with the ArcGIS Pipeline Referencing





















P_PipeExposure features as event records with the ArcGIS Pipeline Referencing tools. The value













Test Pressure Range

The polyline feature class P_TestPressureRange describes the length or range of pressure test

performed on the pipe system.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


pressuretest (Double)–The pressure used for the test.

mindesignpressure (Double)–The minimum design pressure of the pressure test for the pipe

segment.

minadjustedpressure (Double)–The minimum adjusted pressure of the pressure test for the pipe

segment.

unitofmeasure (Text[50])–The unit of measure defining test pressure.


pretest (Short Integer)–The text value indicating whether a pretest was performed. Valid values

are yes and no.


testdate (Date)–The date and time the test was performed.

testmedium (Text[25])–The medium used for the pressure test. Valid values are air, gas,

nitrogen, inert gas, water, and other.

Coded Value Domain: Pipeline_PressureTestMedium

testname (Text[50])–The name of the test.

testtype (Text[25])–The type of pressure test performed. Valid values are strength, spike, yield,

uprating, and other.

Coded Value Domain: Pipeline_PressureTestType

eventid (Text[38])–The unique ID for each test pressure range record. This value is automatically


fromdate (Date)–The date the test pressure range event became active on the route. This value


todate (Date)–The date the test pressure range event was retired from the route. This value is









maintain the P_TestPressureRange features as event records with the ArcGIS Pipeline

Referencing tools.












Referencing tools.






wanting to maintain the P_TestPressureRange features as event records with the ArcGIS Pipeline

Referencing tools.




P_TestPressureRange features as event records with the ArcGIS Pipeline Referencing tools.




tools. This attribute is only used by organizations wanting to maintain the P_TestPressureRange




attribute is only used by organizations wanting to maintain the P_TestPressureRange features as




This attribute is only used by organizations wanting to maintain the P_TestPressureRange




to maintain the P_TestPressureRange features as event records with the ArcGIS Pipeline








This attribute is only used by organizations wanting to maintain the P_TestPressureRange












P_TestPressureRange features as event records with the ArcGIS Pipeline Referencing tools. The



Mapping The purpose of the feature classes in this section is to aid in the visual and cartographic presentation of

the gas system. This includes feature classes to aid in the creation of paper representations of the gas

system, as well as feature classes to aid in the visual representation of information.

Alignment

Sheet

Mapping

Capital

Projects

Pipe Job

Separator


Alignment Sheet

The polygon feature class P_AlignmentSheet describes the spatial extent along a pipeline to be

used to generate a map layout.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


sheetname (Text[45])–The unique name used to identify a single map sheet.

sheetnumber (Text[45])–The unique alphanumeric value used to identify a single map sheet.

sheettype (Text[25])–The type of map series that this map sheet will generate.

Coded Value Domain: Pipeline_AlignmentSheetType

status (Text[15])–The life cycle status of the alignment sheet.











relationships to associated components


Capital Project

The polygon feature class P_CapitalProject describes the location where the organization plans

to perform work that is financed through capital funding.


Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:


projectname (Text[50])–The textual name associated with the capital project.

projectid (Short Integer)–The project management assigned unique identifier for the capital

project.

status (Text[30])–The life cycle state of the capital project.


assignedto (Text[50])–The name of the department to which the project is currently assigned.

description (Text[50])–The textual description of the project.

perccomplete (Double[8,5])–The overall progress of the capital project toward completion.

Initialization of the project is 0 percent; completion of the project is 100 percent.

estmaterialcost (Double[8,5])–The project’s estimated total cost of materials required to

complete the project.

estlaboreqptcost (Double[8,5])–The project’s estimated total cost of labor and equipment

required to complete the project.

esttotalcost (Double[8,5])–The project’s total estimated cost.










relationships to associated components


Pipe Job Separator

The point feature class P_PipeJobSeparator describes the location along a pipe segment in the

pipe system where one capital project terminated and another capital project started.

GeometryType: Point

Relationships: No

Subtypes: No

Attachments: No

Editor Tracking:







Attributes:




geodatabase.




populated.



populated.

eventid (Text[38])–The unique ID for each pipe job separator event record. This value is


is only used by organizations wanting to maintain the P_PipeJobSeparator features as event


fromdate (Date)–The date the pipe job separator event became active on the route. This value is




todate (Date)–The date the pipe job separator event was retired from the route. This value is







P_PipeJobSeparator features as event records with the ArcGIS Pipeline Referencing tools.

engrouteid (Text[38])–The unique ID of the engineering network route where the pipe job

separator is located. This value is automatically generated and populated by the ArcGIS Pipeline








engm (Double[16,5])–The engineering network measure location along the route where the

pipe job separator is located. This value is automatically generated and populated by the ArcGIS





wanting to maintain the P_PipeJobSeparator features as event records with the ArcGIS Pipeline

Referencing tools.

continroutename (Text[100])—The continuous network route name where the point event is









organizations wanting to maintain the P_PipeJobSeparator features as event records with the









Utility and Pipeline data Model - iSpatial Tec

Documents

Transcript of Utility and Pipeline data Model - iSpatial Tec