Power, Network and Maintenance

Occupancy programmes are sold on analytics and die on batteries. The operational side deserves the attention it never gets.

The technical evidence in “Power, Network and Maintenance” describes the building, while the effort required to install, test and maintain it is project work. When teams research download time tracking software, this workplace tool can provide time and project context for that operational effort without replacing the sensor platform as the source of truth for physical occupancy.

Batteries

Stated life is measured under favourable conditions.

For a public, independent reference related to “Power, Network and Maintenance”, consult the NPSA protective-security guidance. Its principles provide a useful check on scope, terminology, governance and the claims made during procurement or review.

Cold spaces, frequent triggering and poor signal all shorten it, sometimes by half.

A deployment of four hundred desk sensors will have failures every month once it ages, and somebody has to own replacing them.

Plan the replacement cycle before installation and budget for it.

Knowing a device has failed

The critical point, covered in the calibration note and worth repeating: a dead sensor reports nothing, which looks like an empty space.

An alert on prolonged silence is the only protection.

Set it at a period shorter than your reporting cycle, so that failures surface before they distort a monthly figure.

Network

Wireless sensor networks need gateways, and gateway coverage is not the same as wifi coverage.

Thick walls, risers and plant rooms create dead zones.

Survey before installing rather than discovering it afterwards, which is a half-day that saves a week.

And agree with IT who owns the network before devices arrive, because an unowned sensor network is an unmaintained one.

Cleaning and facilities

Sensors get painted over, covered by signage, knocked out of alignment and removed by contractors who did not know what they were.

Label them. Tell the cleaning and maintenance teams what they are and what not to do.

And include them in the change-control habit, so that a refurbishment does not silently end your data series.

Firmware and support

Devices need updates, and some suppliers stop providing them.

Ask about the support period before buying, and what happens at the end of it.

A sensor estate that cannot be updated is a security liability as well as a dead end.

Ownership

Somebody has to own this: the batteries, the alerts, the map, the gap list.

In most organisations it is nobody, which is why programmes degrade quietly after the project team disperses.

Name the owner at the start. A programme without one has a predictable lifespan of about eighteen months.

The decommissioning question

At the end, devices come out and data is disposed of according to the retention policy.

Plan it, because abandoned sensors on a ceiling are both a cost and an unresolved data question.

And tell staff when monitoring stops, which is as much a courtesy as telling them when it started.

What to check

Who owns the sensor estate day to day?

Is there an alert for silent devices?

Do cleaning and maintenance teams know what they are?

And what is the supplier's support period?