Wireless BMS Retrofit: A Scope and Cost Worksheet

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.

Define the additional decision the retrofit supports

Identify the facilities question: room-condition visibility, plant-state review, tenant complaints, meter reconciliation or another bounded task. Map the existing BMS functions and the information already available. The project should explain what the additional points or reports contribute and how staff will use them.

Keep monitoring and control changes separate in the scope. Reading an existing point can require access and mapping work; altering an operating sequence can require a different design authority and test process. The responsible controls specialist should approve any change that affects the plant's behaviour.

Inventory the points before pricing devices

For each proposed point, record the asset, physical location, quantity, unit, range and available source. Identify whether it comes from an existing controller, a meter interface or a new field sensor. A point count without those details can conceal substantial differences in installation and verification effort.

Check whether the existing value is suitable for the proposed purpose. A controller setpoint is not the same as a measured room condition. A status register may need interpretation before it becomes a useful operating label. Keep the source documentation and the person responsible for confirming its meaning.

Survey the occupied building as it operates

Record access restrictions, working hours, tenant coordination, ceilings, service routes and required permits. These conditions can determine the practical installation method and labour cost. A retrofit quotation should use the actual work windows rather than assume unrestricted access to every proposed point.

Survey the radio path at the intended installed positions. Structures, equipment, doors and normal occupancy can affect the observation. Suitable LoRaWAN field points with a verified 4G backhaul should be assessed against the required records and timing. A general coverage claim does not replace evidence from the actual building.

Price power and mounting explicitly

Wireless communication does not eliminate the need for an appropriate power arrangement and physical installation. Identify battery, local supply and gateway requirements for each selected device. The designer should establish the maintenance and autonomy assumptions that apply to the supplied configuration.

Include brackets, enclosures, cable protection and access for replacement. A sensor that can be installed cheaply but requires disruptive access for every service visit may create a higher operating burden. Compare the complete installed and maintainable arrangement, including any work supplied by the building's existing contractors.

Expose integration dependencies before ordering

Ask whether access requires a licence, interface module, vendor attendance or approved network change. Identify the owner of those dependencies and include them in the schedule. A sensor purchase can be straightforward while access to an existing BMS field remains unresolved.

Document the mapping rules for units, status values, cumulative counters and quality. Keep the configuration version with the point register. A report assembled from several systems needs a consistent interpretation of timestamps and missing records, especially when it compares rooms or buildings.

Compare recurring responsibilities

List subscriptions, user administration, device checks, replacement work and instrument verification. Separate platform support from local attendance and from the incumbent BMS provider's responsibilities. Use the actual supplier terms for service commitments and costs; there is no defensible universal project price or payback period.

Identify ownership of devices, accounts and historical records. The customer should know how to export the accepted information and what is required if a provider changes. Include a representative export and account-handover exercise in the scope where those capabilities matter to the operating model.

Accept a representative point set

Select points that exercise the different interfaces and installation conditions. Include a measurement, a state, a cumulative counter where relevant, and an unavailable source. Verify each against its independent reference and document expected behaviour before the test.

Test the complete path through the report and the staff response. A gateway receiving messages does not establish that the application uses the correct units or that the facilities team receives the required exception. Retain failed checks and the repeat evidence after correction.

Use the pilot to refine the remaining rollout

Record actual access time, installation difficulties, integration effort and maintenance implications. These observations can improve the estimate for the remaining points without pretending that the first room represents every building. Group later work by genuinely comparable conditions and identify exceptions explicitly.

The final proposal should show included points, dependencies, exclusions from the quoted work, acceptance responsibilities and recurring services in clear commercial terms. This allows the customer to compare a wireless retrofit with other practical approaches using the same required result and evidence.

Connect the decision to the project

Use Building management, Iot solutions 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.

Sources and method

NIST SP 800-82 Revision 3 supports system-boundary and access-dependency considerations. The cost worksheet contains no invented prices or payback claims; use current quotations for the selected installation.

Frequently asked questions