Bermondsey Blocks S+T: Building the Landlord BMS

Automatry is delivering the Trend-based landlord BMS at Bermondsey Blocks S+T through Kane Group, contracted to Sisk. This project update covers the path from design and panel coordination through installation, commissioning and handover.

The traditional BMS is at the centre of the delivery. Our Edge gateway sits alongside it as an additional layer that helps engineers through commissioning and handover.

Design the operating system before the interface

The visible supervisor is one part of a much larger package.

Before there is a useful graphic, the project needs a clear account of the plant being controlled, the points available, the interfaces with packaged equipment and the way alarms, schedules and operating modes will behave. Panel architecture, network layout, point naming and control descriptions all have to agree.

That coordination is where much of the engineering sits. A point on a drawing needs to become the right physical connection, the right controller object and the right item in the operator interface. If those layers drift apart, the building may still run, but it becomes harder to commission and much harder to maintain.

At Bermondsey, the landlord system spans multiple plant areas, shared services and energy monitoring. Each part has its own delivery sequence and dependencies. The BMS has to bring them into one operating record without hiding where the underlying responsibility sits.

Repetition helps, but it does not remove judgement

Large residential projects contain a lot of repeated equipment and repeated design patterns. Reuse is essential. It makes panel design, controller software, graphics and testing more consistent.

It can also create false confidence.

The tenth copy of a control pattern still has to be connected to the correct plant. A repeated alarm still needs the right priority and destination. A standard graphic still needs to reflect what was actually installed. Site changes have to flow back into the record rather than remain in one engineer's notebook.

Our approach is to standardise the pattern and keep the project-specific evidence visible. That makes repetition useful without treating the two towers as a collection of identical rooms.

Commissioning is where the records meet the building

Commissioning is not simply the final stage after installation. It is where the drawings, controller software, field wiring, equipment interfaces and physical response are tested against each other.

A point can exist in software and still be connected incorrectly. A command can be accepted without producing the expected plant response. An alarm can trigger without reaching the person who needs it. Those are different failures and need different evidence.

The useful commissioning record shows what was tested, what the system did and what remains open. It gives the handover team something stronger than a completed checklist with no operating context.

For a project of this scale, that evidence also helps manage progress. It separates systems that are ready to witness from those waiting on access, power, network, packaged plant or another trade. The BMS cannot remove those dependencies, but it can make them easier to see.

Handover should leave a system people can understand

The finished job is not the moment the supervisor first loads. It is when the operating team can use the system without relying on the people who built it being in the room.

That means readable naming, clear graphics, sensible alarms, maintainable control logic and records that match the installation. This project update follows that work through commissioning and towards a handover the operating team can use with confidence.

Projects like this are important to Automatry because they keep our software work grounded. We see where information is lost between design, installation and commissioning because our engineers work across those boundaries.

The immediate job at Bermondsey is straightforward to describe: deliver a dependable landlord BMS for Kane Group on Sisk's project. The wider lesson is that scale does not reduce the need for detail. It makes a consistent engineering record more valuable.