Open jgunstone opened 2 months ago
we talked about this today, some notes from the discussion:
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.
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".
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.
note the below is presented for discussion - and does not yet outline a proposal about how this might be supported in BDNS...
Broadly, common practice follows like so:
In addition to this, on many larger projects we are provided with an "Asset Information Requirements" document that requires plant references are built in a specific way, and sometimes the requirements for mechanical plant is different than for electrical plant (!): therefore we require flexibility in approach to adapt to changing client requirements.
To give flexibility, our process is as follows, every digital asset contains the following "identity data" fields:
an equipment reference is then built from these fields. on a project, we can specify how the equipment reference is built
for type references:
e.g. for instance references:
on projects, for main pieces of electrical distribution equipment there was a desire to only show the instance information in the tag - that way if the type specification of the equipment changes, this change only happens in the schedules and the drawings don't need to change. this can be done as follows:
e.g. for instance references of major electrical distribution equipment:
in the example above the type information still exists as data in the asset, but is not shown on the tag.
it would be great if in BDNS we could acknowledge this type of use case, and potentially develop a "tag definition schema" that provides a compliant method for defining how equipment references should be built for type and instance references.