From One Gateway to a Fleet

That distinction has shaped the development of Automatry Edge. Our early site software was deliberately specific. At the UCL Anthropology Lab, a local gateway, BACnet service and tablet interface were built around the needs of a specialist research environment. At Oaks Park High School, the controls delivery extended into a tailored operating interface for the facilities team.

Those systems taught us what a standard platform needed to handle and gave Edge a strong engineering foundation.

Different buildings expose different problems

A commercial tower, a residential phase and a specialist laboratory do not produce the same engineering conditions.

Thirty High is a 30-storey office retrofit for Landsec with more than 1,000 mechanical plant assets. The job requires estate-scale visibility: structured equipment, live operating data and a route from commissioning evidence into ongoing operation.

At King's Road Park Phase 3, the focus is different. Automatry is working across more than 140 apartments for Berkeley St William, with the gateway supporting an apartment-by-apartment Titan commissioning workflow. Repetition matters, but so does the individual evidence for each home.

UCL and Oaks Park add another set of constraints: specialist environmental control, local interfaces, long-lived control logic and site operation that cannot depend on a cloud connection to remain useful.

Further through the delivery pipeline, the scale continues. At Bermondsey Blocks S+T, Automatry is delivering the landlord Trend BMS through Kane Group, contracted to Sisk, across a scheme of about 500 apartments. Field work at this scale directly informs how our gateway and commissioning tools need to behave.

A fleet is a set of invariants

The repeatable part is not the dashboard layout. It is the set of engineering rules underneath it.

Each gateway needs a durable identity. It needs to understand the local BACnet network without overwhelming slower field buses. It needs to buffer data when the wider network disappears, recover after a restart, and send data out without opening the building network to inbound internet traffic.

It also needs to respect the operating brief for that site. One project may need deep telemetry and asset mapping. Another may need focused gateway health. A residential commissioning team needs guided tests and evidence per apartment; an estate operator needs trends and system context across the building.

Standardisation should make those differences manageable, not erase them.

From site knowledge to product knowledge

The useful advantage is that Automatry meets these systems from both sides. Our engineers design, install and commission the controls. Our software team builds the gateway, data path and operating tools around the same systems.

That closes a gap which often appears in building technology. The software is designed around naming inconsistencies, partial networks, phased handovers, changing project conditions and the ordinary imperfections of live sites.

The result is a platform that becomes more repeatable while remaining practical. From purpose-built site systems, to a production Edge deployment at Thirty High, to gateway workflows on other projects, the direction is clear.

The fleet is the ability to operate each gateway to the same engineering standard while giving each building the treatment it actually needs.