Sanitary Sewer Pipe IDs\u00a0<\/b>– Often done with a combination of downstream manhole, a dash, and then upstream manhole.\u00a0 So sanitary sewer pipe ID 26-27 takes flow from manhole 27 and carries it to manhole 26.<\/p>\n
Geopins \u2013\u00a0<\/b>Not often seen in utilities for asset IDs, a geopin is calculated using the X & Y coordinates of a spatial feature.\u00a0 Geopins are commonly seen in land records.\u00a0 Geopins are not a good choice for spatial features that are assigned new loction, such as when a utility improves the spatial accuracy of their asset base by doing something like sub-foot GPS field data collection.<\/p>\n
This is an example how geopin would work for a valve at coordinates: X = 23658974.365\u00a0Y = 6584752584.968
\nGeopin Formula = X2 Y2 X3 Y3 \u2013 X4 Y4 \u2013 X5 Y5 X6 Y6
\nGeoPIN = 3568-54-8795<\/p>\n
Asset ID Tips<\/b><\/p>\n
Don\u2019t use internal database IDs\u00a0or geodatabase IDs for your asset IDs<\/b>\u00a0\u2013 This is a cardinal rule!\u00a0 Never use any internal IDs from a geodatabase or any other database for your unique IDs unless you are 100% certain that it will not be automatically recalculated by the application in the future.\u00a0 An example of this is the OBJECTID attribute in a geodatabase.\u00a0 Because the OBJECTID attribute is internally used by the geodatabase, on occasion in may be recalculated by ArcMap.<\/p>\n
Keep your legacy asset IDs\u00a0<\/b>– It\u2019s perfectly acceptable to store your \u201clegacy\u201d asset IDs when you switch to a new asset ID system.\u00a0 It may be very helpful to know legacy asset IDs if someone needs to refer back to as-builts or old field map books.\u00a0 We saw a great example of this with a municipality that created a table with a one to many relationship between new asset IDs and legacy asset IDs that were used on any old plans or maps that showed the assets.<\/p>\n
Make sure only 1 application or person assign new asset IDs \u2013 \u00a0<\/b>This is critically important.\u00a0 Only 1 application, such as ArcMap, your CMMS or 1 employee is who assigns unique IDs, otherwise you are running the risk of assigning duplicate IDs.<\/p>\n
Storm Water IDs\u00a0<\/b>– because of the ad-hoc nature of how most water storm networks were built, especially in suburbia and the difficulty in understanding how the water flows without good elevation data, it\u2019s difficult to create an asset ID system for stormwater that describes which assets flow into each other.\u00a0 It\u2019s much easier to just use incrementing IDs.<\/p>\n
If you\u2019d like to share other asset ID systems you\u2019ve seen, please feel free to post a comment on this blog.<\/p>\n"}],"authors":[{"ID":4661,"user_firstname":"Howard","user_lastname":"Crothers","nickname":"Howard Crothers","user_nicename":"hcrothers","display_name":"Howard Crothers","user_email":"hcrothers@esri.com","user_url":"http:\/\/solutions.arcgis.com","user_registered":"2018-03-02 00:16:15","user_description":"Howard leads the Esri team developing ArcGIS Solutions for electric, gas, water, sewer, stormwater, communications, renewables, and district heating and cooling.","user_avatar":"
"}],"related_articles":"","card_image":false,"wide_image":false},"yoast_head":"\n