Utility and Pipeline Data Model 2016 Valves Layer

393
1
Jump to solution
01-29-2018 03:30 PM
Occasional Contributor III

In the UPDM2016 data model we have a single Valve layer.

Do I need to store both inline valves for mainlines and curb valves for services in the Valve layer together or is there another layer?

Reply
0 Kudos
1 Solution

Accepted Solutions
Esri Contributor

Hi Jordan,

The intention of the Valves featureclass in the UPDM 2016 Edition was to store all controllable valves regardless of their installation location.  But, it is important to remember that UPDM is a data model template, it is not a requirement.  Every gas utility has unique data management requirements.  If your unique data requirements lead you to conclude that the curb stop valves should be stored in a separate featureclass, then please do that. 

If you do not have a strong business requirement to separate the distribution main gas valves from the service line curb valves, then my advice would be to keep them in the same featureclass to reduce the number of database queries required on your standard map views every time you pan, zoom or edit.  Reducing the number of featureclasses used to store your assets is a proven method for improving map redraw performance and the scalability of your Geodatabase..

Tom DeWitte

Esri, Inc

Technical Lead - Natural Gas Industry

View solution in original post

1 Reply
Esri Contributor

Hi Jordan,

The intention of the Valves featureclass in the UPDM 2016 Edition was to store all controllable valves regardless of their installation location.  But, it is important to remember that UPDM is a data model template, it is not a requirement.  Every gas utility has unique data management requirements.  If your unique data requirements lead you to conclude that the curb stop valves should be stored in a separate featureclass, then please do that. 

If you do not have a strong business requirement to separate the distribution main gas valves from the service line curb valves, then my advice would be to keep them in the same featureclass to reduce the number of database queries required on your standard map views every time you pan, zoom or edit.  Reducing the number of featureclasses used to store your assets is a proven method for improving map redraw performance and the scalability of your Geodatabase..

Tom DeWitte

Esri, Inc

Technical Lead - Natural Gas Industry

View solution in original post