BDNS for equipment type tagging / custom tags about bdns HOT 3 OPEN

we talked about this today, some notes from the discussion:

• do we want to support Type tags?
  • deviation from original use case of asset tagging during as built stage
  • ... but type references are essential when dealing with BIM data which is a listed use case
  • the abbrevations themselves are very useful for encouraging standardisation in equipment references
• BDNS is keen to avoid developing a meta-schema for how to build an equipment reference, preferring to have a simple, defined and documented approach that can be adopted or not
• being able to easily distinguish at TypeReference from a unique Asset Identification Reference is essential to avoid confusion
  • maybe they could use different separators instead of "-" ?

next steps - try and come up with some examples of how TypeReferences could work, demonstrate that it won't cause confusion when comparing to the primary use case of unique Asset Identification Reference.

from bdns.

discussed this internally...
liked the idea of a "." as separator for type references (or "" potentially).
reinforced the point that for some items of equipment type tags are essential for the production of design info (drawings etc.) and that the abbreviations should remain consistent as the design progresses to the "in-operation".

from bdns.

After more discussions, we achieved agreement on creating an asset.type in the form of XZ where X is the abbreviation and Z is an incremental number. Then the asset.name can be in the form of X-Y or XZ-Y, where Y is still the instance incremental number.

from bdns.