Skip to main content

Commissioning and Data Mapping

Assign metadata and equipment to the appropriate data streaming from our BACER or VACER file import

CIM Support avatar
Written by CIM Support
Updated yesterday

On PEAK:

Navigate to BACER → Commission Favourites

OR

Navigate to Virtual Collector → Commission Favourites

PEAK Commissioning Sheet

Here we can see a list of all the datapoints our BACER can see across all the devices on the site. Our goal is to assign the correct PEAK Equipment and PEAK metadata to any metadata points which we want to monitor or deploy data analytics on.

To utilise the “Predicted Metadata” column, start a prediction job via Bacer → Advanced (top right corner) → View Metadata Prediction Jobs. This will prompt the CIM AI model to predict the appropriate metadata based on a mix of Point Name, Identifier, Device Name, and Units

A quick overview of the Sheet:

For non-BACnet deployments, such as nHaystack, API, or VACER, the columns several columns will not pre-fill. Instead, you will need to manually enter identifiers exactly as they appear in files (VACER) or points lists (nHaystack and APIs). The type of point being commissioned can be changed at the top left of the table; Virtual points must be accessed via Virtual Collectors. Other points must be accessed via Bacers.

Commissioning Points:

In this example we’ll commission all points visible on the BMS for the Chiller:
“CH-5”
Some BMS interfaces will allow the user to hover over datapoints to see additional information such as BACNET Point Name, Device Number and Identifier.

In Instance, we can see CH-5’s enable point is named “CH5_Enable on Device “40100” with Identifier: BO2401.

Some points may not provide extra information as to their device/identifier but may still have descriptive naming in our PEAK sheet.

We can now locate this value in PEAK commissioning sheet and assign the correct Metadata: and Equipment:


Common Points

Creating Common Equipment

Some points must be shared across multiple equipments of the same type, for example a Chilled Water Common Leaving temperature or Master Cooling Call.
In this example, the “Chilled Water Common Entering Temperature” is shared assigned to a common equipment which is shared between CH-1,CH-2,CH-3 and CH-4.

Other instances where you might use Common Equipment:

  • Common outside air temperature/humidity/enthalpy for AHUs/PACs/Chillers/Boilers (a common equipment will need to be created for each equipment type)

  • AHU/PAC return air points when the units share a return air duct.

Point/Equipment Cloning

Cloning is the process of copying points on a given unit to all selected units of the same type and is especially useful for basic equipment that are often templated throughout the building. Common targets for this are VAVs or other terminal boxes as well as third-party integrations such as VSD controllers. This process can significantly reduce commissioning time but is only usable when specific criteria is met:

  • All units being which will have points cloned onto them must share the same identifier → point layout, for example: VAV Analog-in

  • Units should be thoroughly checked to ensure they don't have any extra points than the unit being cloned (some VAVs may have duct heaters, others not).

Cloning utilises the “Primary Device” field of an equipment and copies points (Based upon the Identifier) from the original equipment to all selected equipments.

To Clone Equipment: In PEAK → BACERs → Select the Icon next to the equipment you wish to clone.

Misc Integration Tips:

Car Park Ventilation

Car park CO sensors may not be assigned directly to a fan in the BMS, in this case, assign the CO sensor(s) to the closest exhaust fan and assign the “Car Park CO” metadata to it’s own zone, allowing multiple CO Sensors to be assigned to one fan.

Modifying Points:

Points can be modified post-initial mapping, either by modifying fields in the table, or via clicking the appropriate equipment and using the edit pencil icon next to the desired favourite. This will maintain the history of that point as long as it is not actively deleted or saved in a state where it does not have an equipment linked to it.

Did this answer your question?