BMS Point Mapping: Units, Status and Meter Replacement
A practical worksheet for operations, stores and project teams.
By addanode · Published 5 November 2026
A BMS point map should explain how each source value becomes an operational record. Preserve the source address, physical identity, unit, scale and quality meaning, then test the conversion with witnessed evidence. Meter replacement needs an explicit handover so a new device does not silently inherit the old counter history or create a false consumption event. BMS point mapping provides a maintainable contract between the physical installation, its source interface and the facilities report.
Use the working record
Download the editable worksheet. Record the actual evidence and responsible reviewer against each relevant row. The empty results are inputs for your project, not completed tests. Add the equipment identity, operating period and reference method before assigning an outcome. Retain unsuccessful checks and the evidence from any repeat after correction.
Give the physical asset a stable identity
Start with the building, system and physical point being measured. A source address is a connection detail; it can change when a controller is replaced. Keep an asset identity that remains understandable to facilities staff and link each technical address to its effective period.
Record the installation location and the service boundary. Two meters with similar names may measure different floors or include different common areas. The point map should identify that distinction before a report compares their totals or assigns a consumption quantity to a tenant.
Preserve the original source definition
For each point, record the interface, address, data type and manufacturer or integrator documentation. Confirm whether the source value is instantaneous, cumulative, calculated or a status. A numeric field can contain a coded state rather than a physical measurement.
Keep a representative authorised sample alongside the mapping. The sample should show the source value, timestamp and quality where available. This provides a reference for later troubleshooting and exposes assumptions that a finished dashboard might otherwise conceal.
Test scaling and units end to end
Write the transformation explicitly, including multiplication, offsets and unit conversion. Check the result against an accepted local indication or calculation. A value of 250 can represent 250 units, 25.0 units or a code depending on the source definition.
Include negative values, zero and relevant range boundaries in the test plan. Do not fix an unexpected result by adjusting a multiplier until it looks plausible. Resolve the source meaning and preserve the approved mapping so the same error is not repeated at the next building.
Translate quality without erasing it
Identify the source's available, unavailable, faulted, substituted and manually overridden conditions. Map them to understandable application states while preserving the original quality evidence. A displayed number can remain unchanged during a communication failure, so value alone does not establish freshness.
Agree when a point becomes stale and what timestamp supports that rule. The interval should suit the actual acquisition arrangement and operating purpose. Keep the last known reading visibly historical rather than presenting it as a current observation after updates stop.
| Mapping field | Record | Test evidence |
|---|---|---|
| Physical identity | Building, asset and boundary | Drawing or witnessed location |
| Source definition | Address, type and documentation | Authorised sample |
| Transformation | Scale, offset and unit | Reference comparison |
| Quality | Original and displayed states | Fault or simulation result |
| Time | Acquisition and arrival meaning | Aligned event sequence |
| Replacement | Old/new identity and effective time | Closing and opening readings |
Distinguish command, feedback and availability
A commanded state indicates what the system requested. Feedback indicates what the selected source observed. Availability describes whether the point or equipment is able to report or operate under its defined conditions. Keep these records separate when the project includes them.
For monitoring integration, define the authorised read scope and any separately approved control work. A successful read test does not authorise a write test. Facilities, controls and IT representatives should agree the interface responsibilities before commissioning activities begin.
Close the old meter deliberately
Before replacement, capture the old meter identity, final readable total, timestamp and relevant operating state. Record any unreadable value as unavailable rather than inventing a closing number. Keep photographs or field records where the site procedure permits them.
Open the new meter with its own identity and initial value. The initial total may not be zero. Record scaling, direction, units and verification results again; a similar model can still have a different configuration. Preserve the relationship between the devices without treating them as one uninterrupted physical counter.
Reconcile the replacement interval
Calculate consumption separately on each valid counter segment. Identify the gap between the final old reading and first accepted new reading. If the reporting owner approves an estimate, retain the method, inputs and label. A reset should not create negative usage or an artificial large increase.
Check whether the replacement changes the measured boundary. Pipework, circuits or tenant allocation may have changed during the same work. In that case, the new series needs both a device transition and a boundary revision before historical comparisons are presented.
Make the handover independently reproducible
Select representative points and reproduce their displayed values from the exported source data and mapping. Include a status point, a cumulative meter and a deliberately unavailable condition using the approved test method. Retain failed checks and the corrected configuration.
Assign owners for address changes, unit mappings, access permissions and meter replacement records. Store the current map with its history and effective dates. A facilities reviewer should be able to explain a changed consumption report from those records without relying on undocumented knowledge held by the original integrator.
Connect the decision to the project
Use Hvac monitoring, Building management to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.
Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.
Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.
Keep a signed mapping revision with the commissioning record. When responsibility transfers to another service provider, include the source documentation and outstanding exceptions so the new team can maintain the same evidence chain.
Sources and method
NIST SP 800-82 Revision 3 supplies operational-technology architecture and access background. Point meanings and meter conversions require the actual source documentation and site verification.
Frequently asked questions
Can the source address serve as the asset identity?
Keep a stable physical identity as well. Addresses can change with controllers, interfaces or configuration.
Should a replaced meter continue the old total?
Retain separate source segments and an explicit reconciliation. Any combined presentation must preserve the replacement and gap treatment.
What makes a point mapping accepted?
Witnessed evidence that identity, units, time, quality and any transformation match the agreed source meaning.
Define a first stage your team can verify.
Tell us the site, equipment, existing records and the decision you need to improve. We will use those inputs to discuss the scope and acceptance evidence.