Hello,
I am wondering if there is any step-by-step documentation available for setting up services in the latest UPDM on an enterprise level. We have noticed that the pipeline_line layer includes a service group asset type, but there is also a separate layer for service summary. Currently, we have only been adding service lines to the pipeline_line layer and are unsure if this is the correct approach. Additionally, we recently discovered the service summary layer and are unsure if we should be drawing a single line segment for services. For example, if our DIMP sheet has 2 sections of pipe, we have been splitting it into 2 segments. Any clarification and guidance on this matter would be greatly appreciated.
Solved! Go to Solution.
Hello neomapper.
Great question about how to manage service lines within UPDM. The purpose of PipelineLine is to store ALL pipes (gathering, storage, transmission, distribution, station, service). Based on your message it looks like this is what you are currently doing. This Utility Network participating featureclass, is where both of the service line segment records you mentioned, should be stored. The Service_Summary featureclass was created specifically for natural gas distribution organizations within the United States. It's purpose was to be a simplified duplication of the PipelineLine - Service Lines. US federal reporting requires all natural gas organizations to annually report a summary of their natural gas pipe networks (summarized by material, diameter, age, and type). The challenge with this reporting requirement is that it requires a single definition of material, age, and diameter for the entire service line. Your 2 service pipe segments have to be merged into a single record. If they have different material, age, or diameter, you have to pick one to represent the entire service line.
In summary keep managing your service lines within the PipelineLine featureclass. If you work for or support a US based gas distribution company and are struggling with how to accurately manage a summarization of service lines for US DOT Annual reporting, then consider looking at using Service_Summary to store that merged version of your service lines.
Tom DeWitte
Esri Technical Lead supporting Natural Gas and District Energy Industries
Hello neomapper.
Great question about how to manage service lines within UPDM. The purpose of PipelineLine is to store ALL pipes (gathering, storage, transmission, distribution, station, service). Based on your message it looks like this is what you are currently doing. This Utility Network participating featureclass, is where both of the service line segment records you mentioned, should be stored. The Service_Summary featureclass was created specifically for natural gas distribution organizations within the United States. It's purpose was to be a simplified duplication of the PipelineLine - Service Lines. US federal reporting requires all natural gas organizations to annually report a summary of their natural gas pipe networks (summarized by material, diameter, age, and type). The challenge with this reporting requirement is that it requires a single definition of material, age, and diameter for the entire service line. Your 2 service pipe segments have to be merged into a single record. If they have different material, age, or diameter, you have to pick one to represent the entire service line.
In summary keep managing your service lines within the PipelineLine featureclass. If you work for or support a US based gas distribution company and are struggling with how to accurately manage a summarization of service lines for US DOT Annual reporting, then consider looking at using Service_Summary to store that merged version of your service lines.
Tom DeWitte
Esri Technical Lead supporting Natural Gas and District Energy Industries