Skip to content

Commit

Permalink
resolving comments
Browse files Browse the repository at this point in the history
  • Loading branch information
pisuke committed Jul 24, 2024
1 parent 9cf21a0 commit ff3aa66
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions BDNS_Specification_naming_syntax.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,13 @@ The following definitions apply:

* **Device/Asset Role**: a specific function in a building that is fulfilled by a device. A device role remains fixed for the function even if the hardware is replaced.
* **Device/Asset Instance**: a specific individual piece of hardware. If the hardware is replaced for a particular device role, the device instance changes.
* **Machine Generated/Readable Device/Asset Instance Globally Unique Identifier (Device/Asset Instance GUID)**: a sequence of digits which is machine generated, is immutable and guaranteed to be globally unique among all identifiers used for the purpose of identification of devices within the digital building system. This type of information can be generated by the manufacturer, BIM or asset management software and is unique to the _device instance_. If a device is replaced, its _Device Instance GUID_ will change. This type of information _is in the scope of this document._
* **Human Readable Device/Asset Role Name (Device/Asset Role Name)**: an alphanumeric sequence that is selected by a human operator according to a global standard that guarantees correlation to building devices categories and uniqueness within the building for a _device role_. The device role human readable name will remain unchanged when specific hardware fulfilling the role is changed. This type of information _is in the scope of this document._
* **Physical Label**: a physical piece of material affixed to a building control device including the printed name of the device and additional information in the form of QR code, NFC tag or other data encoding technologies. This type of information _is in the scope of this document._
* **Network Hostname**: the hostname is a sequence of characters assigned to a device (a host) on a network. A hostname should uniquely identify a single device role on the network at a given point in time. This type of information _is not in the scope of this document._
* **Control point name**: the name of each attribute of a device, such as a sensor value or a set point value. This type of information _is not in the scope of this document._
* **Metadata**: data associated with a device that provide information about its attributes. This type of information _is not in the scope of this document._
* **Machine Generated/Readable Device/Asset Instance Globally Unique Identifier (Device/Asset Instance GUID)**: a sequence of digits which is machine generated, is immutable and guaranteed to be globally unique among all identifiers used for the purpose of identification of devices within the digital building system. This type of information can be generated by the manufacturer, BIM or asset management software and is unique to the _device instance_. If a device is replaced, its _Device Instance GUID_ will change. This type of information _is in the scope of this document.
* **Human Readable Device/Asset Type**: a type of device that has been selected to achieve a specific function. A device type remains fixed (provided direct replacement) if the hardware is replaced. (This is an optional field).
* **Human Readable Device/Asset Role Name (Device/Asset Role Name)**: an alphanumeric sequence that is selected by a human operator according to a global standard that guarantees correlation to building devices categories and uniqueness within the building for a _device role_. The device role human readable name will remain unchanged when specific hardware fulfilling the role is changed. This type of information _is in the scope of this document.
* **Physical Label**: a physical piece of material affixed to a building control device including the printed name of the device and additional information in the form of QR code, NFC tag or other data encoding technologies. This type of information _is in the scope of this document.
* **Network Hostname**: the hostname is a sequence of characters assigned to a device (a host) on a network. A hostname should uniquely identify a single device role on the network at a given point in time. This type of information _is not in the scope of this document.
* **Control point name**: the name of each attribute of a device, such as a sensor value or a set point value. This type of information _is not in the scope of this document.
* **Metadata**: data associated with a device that provide information about its attributes. This type of information _is not in the scope of this document.

## Specification clause example

Expand Down Expand Up @@ -111,8 +112,8 @@ For BIM workflows, the validation procedure shall include the following tests:

`[A-Za-z0-9_$]{22} `([IFC base 64](https://standards.buildingsmart.org/IFC/DEV/IFC4_2/FINAL/HTML/schema/ifcutilityresource/lexical/ifcgloballyuniqueid.htm) format)

### Device/Asset type (asset.type)

### Device/Asset type (asset.type)

#### Definition

Expand All @@ -132,7 +133,7 @@ where:

`X `= <type_abbreviation> (alphabetic characters only, variable length, between 2 and 6 characters)

`Z `= <asset_type_incremental_number> (variable length, unique integer numbers by asset type in each building, non zero padded)
`Z `= <asset_type_incremental_number> (variable length, optional unique integer numbers by asset type in each building, non zero padded)

The type abbreviation shall be according to the [Building Device and Asset Abbreviation Registry](https://github.com/theodi/BDNS/blob/master/BDNS_Abbreviations_Register.csv).

Expand Down

0 comments on commit ff3aa66

Please sign in to comment.