Good morning y'all. I have just started a new role for a new local government where I've stepped midway into an ongoing process of assigning unique asset ID tags for asset data. The goal of the IT director is to create a system of assigning IDs to our assets (facilities, roads, stormwater infrastructure, utilities, etc) shared among all departments. The IT director is hoping to indicate a hierarchical relationship (grandparent-parent-child-etc) somehow in a field (15 characters) by identifying the Township-Section-Range of each asset, followed by a numeric value indicating it's location within the township/section/range (i.e 01=the most westerly portion of the section), and a letter code for the it's type (i.e. Land=L, Transportation = T, and so on). I don't see how we can create a sustainable method for assigning unique values given this method. I understand his desire to maintain an intuitive method for understanding the hierarchy of different features (i.e. a park is an asset, a pavilion or a boardwalk is a sub-asset of the park) and having a shared ID to link facilities from our finance, public works, etc to our spatial data, but this particular method has brought me great confusion.
Has anyone dealt with with this type of issue before? I'm willing to recommend throwing out the existing process if anyone has suggestions for a simpler method for assigning unique IDs AND somehow providing inside into the hierarchical relationships among the asset features.
Any help would be GREATLY appreciated!!!!!!!!
Thanks,
Brennan