BMS Contractor in Swanley

Swanley's real problem: buildings too small to be worth doing properly

Swanley is not a town of large single-occupier buildings with a facilities team on staff. It is a compact mix of light industrial and trade units, schools, care homes, community and leisure buildings, and small-to-mid commercial premises — the kind of building stock that exists at a scale nobody plans around. A site like this is too small to justify an in-house facilities manager, let alone a dedicated controls engineer, and it is too small for most national contractors to service at a margin that makes sending someone worthwhile. The building falls into the gap between the two, and the gap is where the controls sit unexamined.

What that produces, consistently, is a control system running exactly as it was left on the day it was commissioned. Nobody has changed a schedule, checked a setpoint against how the building is actually used, or noticed that a sensor has drifted, because nobody has been paid to look. The original installer is long gone, the maintenance budget — if there is one — goes on the roof or the boiler, and the time clock or basic controller in the plant room has simply been running the same programme for years, quietly, in the background, while everyone assumes it is fine because nothing has obviously broken.

That is not a criticism of the buildings or the people running them — it is a straightforward consequence of size, and it is exactly the situation we are set up to work in. We do not have a minimum job size and we are not trying to sell a full BMS replacement to a two-unit trade estate. A survey of a small building's existing controls, an honest assessment of what is actually wrong with it, and a fix scaled to match — that is most of what Swanley work looks like, and it is usually cheaper and quicker than the building's owner expects.

• Controls surveys sized for small and mid-sized buildings, not just large estates
• No minimum job size — a single plant room gets the same attention as a multi-floor site
• Honest assessment of what a small building's controls actually need
• Upgrades scoped to the building, not sold as a full replacement by default

The M25 Junction 3 problem: in a London contract, physically in Kent

Swanley sits on the Kent/Greater London boundary, right where the M25 meets the A20 at Junction 3. That position creates a specific problem that is easy to see once you know to look for it: a building in Swanley is often owned or managed as part of a client's London portfolio, grouped administratively with sites in Bromley, Croydon or further into the capital, while sitting physically in Kent. The building gets serviced by whichever contractor holds the wider London contract — a contractor based in or dispatching from central London, working to central London travel times, for a site that is, in reality, a short run off the M25.

That arrangement is not dishonest and it is not unusual — portfolios get built around ownership and management structure, not postcode boundaries, and nobody sits down and asks whether Junction 3 is a sensible place to draw a service-area line. But it has a practical cost. A contractor coming from central London to a Swanley site is adding real drive time to every visit, both planned and emergency, and that time gets paid for one way or another — either in the contract rate or in how long the building waits when something goes wrong.

We are not asking anyone to break up a portfolio contract, and we are realistic that a lot of London-managed estates will stay managed that way regardless of where the individual buildings sit. What we do say plainly is that a Swanley building inside a London contract is a reasonable thing to ask a second opinion on, particularly at renewal — whether the response time actually written into that contract reflects where the site is, or where the contract was drawn up from.

• Local coverage for Swanley buildings even where the parent contract is managed from London
• A second opinion on response times where a Kent site sits inside a London-based service contract
• Direct engineer attendance without routing through a central London dispatch desk

Schools and care settings: occupancy patterns generic schedules don't handle

Swanley has a working share of schools and care and community buildings, and both carry occupancy patterns that a generic weekday time schedule handles badly. A school runs to term dates, not a calendar week — half-term, inset days and the long summer shutdown all fall outside a standard Monday-to-Friday schedule, and unless somebody has gone into the controller and set those dates deliberately, the building keeps heating an empty site through the holiday exactly as it would a normal teaching day. We see this constantly, and it is one of the cheapest and most avoidable sources of wasted energy in this kind of building stock.

In care settings the calculation is different again, because temperature stability there is not a comfort question, it is a duty-of-care question. Some care buildings run genuinely continuous occupancy, with no holiday dip to schedule around at all, and the tolerance for a heating or ventilation fault that leaves part of the building too hot or too cold is much lower than in a normal commercial building. A control strategy that would be a minor inconvenience in an office is a real problem in a care setting, and it needs to be treated that way from the schedule outward, not just from the alarm response.

The fix in both cases is usually not new equipment. It is going into the existing controller, understanding how the building is actually occupied across the year rather than how a default schedule assumes it is occupied, and setting schedules, holiday dates and setpoints to match. Where there is no ability to schedule holidays properly at all — which is common on older or very basic controllers — that is worth flagging honestly as a limitation, rather than pretending a workaround solves it.

• Term-time and holiday scheduling reviewed and corrected on existing controllers
• Setpoint and schedule strategy appropriate to continuous-occupancy care settings
• Honest flagging of controller limitations rather than a workaround that doesn't hold
• Half-term and summer shutdown scheduling checked as part of routine maintenance

Two splits, a wall controller, and nothing joined up

The typical Swanley small building has a heating system on a time clock and two or three split or cassette air-conditioning units, each with its own handset on the wall. Nothing connects them. In practice a unit gets turned down to sixteen degrees on a warm afternoon and left there, the heating works against it the following morning, and the first anyone knows is a bill that makes no sense against a building nobody has changed.

Bringing the cooling onto a small supervisor through a gateway is a modest job on a building this size, and it is often the change with the shortest payback — because it stops two systems working against each other rather than making either one more efficient. It is also the honest place to stop. If a building has one unit in one room and a sensible person adjusting it, we will tell you the integration is not worth doing.

• Split, cassette and VRF cooling interfaced to a small supervisor via BACnet or Modbus gateways
• Heating and cooling put on one schedule with a dead band between them
• Alarms and run hours reported rather than discovered on the bill
• A plain answer when a building is too small for the integration to pay

Light industrial and trade units: a time clock and a thermostat

A meaningful share of Swanley's building stock is light industrial and trade units — the kind of unit with warm-air heating and, in a lot of cases, nothing that could honestly be called a control system at all. The whole of the controls is a time clock and a thermostat, set up once at fit-out and never revisited. That is not necessarily wrong for a small unit with a simple heating load; a time clock and thermostat is a perfectly reasonable way to run some buildings, and we are not going to tell a unit owner they need a full BMS they do not need.

Where it does become a problem is when nobody actually knows what the time clock is doing — the hours it was set to years ago, whatever they were, are the hours it still runs to, regardless of whether the unit is now single-shift, double-shift, or barely used at weekends. Nobody notices, because a warm-air heater running outside the hours it needs to is not a fault; it is just quietly wasted gas, and there is no alarm for that.

Adding even basic monitoring to a unit like this — knowing when the heating is actually calling, what the space temperature is doing against the schedule, whether the thermostat is even reading correctly — is a small piece of work that pays back quickly, without needing to touch the heating equipment itself or turn the site into something more complicated than it needs to be. It is one of the few places in this trade where a genuinely small, genuinely cheap piece of work makes an immediate difference, and we are happy to say so plainly rather than push something bigger.

• Basic monitoring added to time-clock-and-thermostat setups without replacing the heating plant
• Schedule reviews matched to actual shift patterns, not fit-out defaults
• Sub-metering and simple energy monitoring for light industrial and trade units
• No unnecessary upgrades — a unit that only needs a working thermostat gets a working thermostat

What a small-building survey with us actually looks like

Because so much of the work described above starts from 'nobody has looked at this properly', most engagements in Swanley begin the same way regardless of the building type: a survey. We look at what is actually installed, whether it still works as intended, what the schedules and setpoints are currently set to, and how that compares with how the building is genuinely used. For a small site this is a short piece of work, not a drawn-out audit, and it produces a plain answer rather than a sales pitch.

That answer is sometimes 'this is fine, leave it alone' — a working time clock and thermostat on a unit with a simple load does not need converting into a BMS, and we will say so even though it is not the answer that generates the most work for us. More often, for buildings that have genuinely not been looked at in years, the answer involves a handful of specific, inexpensive corrections: a schedule reset, a sensor check, a holiday calendar that was never programmed, a setpoint left over from a previous tenant.

Where a building does need something more — new monitoring on a unit that has none, a proper controls survey ahead of a lease renewal, a small BMS for a site that has outgrown a time clock — we scope that as its own piece of work, priced against what the building actually needs rather than a standard package. Alpha Controls is a BCIA member, SafeContractor approved and Constructionline Gold registered, and we work across London, Kent and the South East, but a Swanley trade unit gets exactly the same straight answer as a much larger site would.

Why a local BMS contractor matters in Swanley

There is an assumption built into how a lot of commercial property gets serviced, which is that the buildings worth doing properly are the big ones. Swanley is a useful place to test that assumption, because so much of its stock is deliberately, permanently small — a trade unit, a single plant room, a community hall — and the assumption fails badly there. Small buildings do not have smaller problems, proportionally; if anything the problems are worse, because nobody has ever been paid to find them.

Being on the Kent/London boundary sharpens that further. A building at Junction 3 is close enough to the M25 to be genuinely convenient to reach from most directions, and far enough from central London that a contractor based there is adding real time to every visit whether they admit it or not. We are close enough that a Swanley call does not require a special trip, and we are not trying to hold a large portfolio together from a head office somewhere else — a site here gets the same engineer twice, not whoever was free.

We work for FM providers, landlords, small businesses and building owners directly, and the size of the building has never determined how carefully we look at it. A single unit with a time clock gets the same honest answer as a school with a full BMS: what is actually wrong, what it would cost to fix, and whether it is worth doing at all. Sometimes the honest answer is that nothing needs doing, and we would rather say that than invent a job.

Alpha Controls is a BCIA member, SafeContractor approved and Constructionline Gold registered, and covers London, Kent and the South East from our Gravesend base. Swanley — with the BR8 postcode and the Kent/London border villages of Hextable, Crockenhill and Well Hill around it — is well within that reach, and it is the kind of town where a straightforward, no-minimum-job approach to controls actually matters, because so much of the building stock there would otherwise go unlooked-at indefinitely.

BMS in Swanley — common questions