Property
Multi-unit residential, serviced apartments, co-living, small developments. One system per unit, one dashboard for the operator.
Property scope →Property · offices · factories
Buildings that run themselves.
Homes taught us the hard part: people. Buildings are the same problem at scale — more rooms, more meters, more keys, and a bill that arrives every month. We automate the building, not the production line.
Mumbai & MMR · Hong Kong · UAE with a local partner
The short answer
Ambient Form Studio automates the building systems in multi-unit property, offices, retail, warehouses and factories: lighting zones, cooling and ventilation, access control, energy sub-metering, leak detection and one operator dashboard. We quote per building after a survey and a metered baseline, usually starting with one floor or one building as a pilot.
We do not take on PLC, SCADA, robot cells or machine safety — the production line belongs to an industrial controls contractor.
- One dashboard
- Every meter per unit, per floor, per line, per tenant
- Pilot first
- 60–90 days measured against your own baseline
- Local-first
- Keep running when the internet or the vendor does not
- Open protocols
- Modbus · BACnet · KNX read the plant you already have
01 — Three scopes
The same layer,
at three scales.
A landlord, an office manager and a factory engineer are all asking the same question: what is running, who is paying for it, and why is it running when nobody is there. The scope changes; the layer does not.
Offices & retail
Meeting-room occupancy, after-hours cooling, lighting zones, access and a floor-level energy view.
Office scope →Factory & warehouse
Lighting zones, ventilation, sub-metering per line, access and the plant dashboard. The building, not the machines.
Factory scope →02 — Property
A block is not
a big house.
A landlord does not want a clever living room. They want vacancy mode between tenants, one-time codes for viewings, per-unit energy, and a leak alarm before the ceiling below is ruined.
The property scope is a repeatable unit specification plus a master dashboard. Each unit gets its own local hub, its own scenes and its own credentials; the operator gets a portfolio view that does not let one tenant see another. Common areas are a separate zone.
- Vacancy mode. Between tenants, the unit runs a frost/heat and leak watch, not a lighting scene.
- Viewing access. One-time codes for agents, expiring the same evening.
- Per-unit metering. Electricity, water and cooling where the building allows sub-metering.
- Common areas. Lift lobbies, corridors, parking and facade on schedules that follow occupancy, not a fixed timer.
- Handover per unit. A device list, credentials and a one-page guide the tenant can actually use.
- Maintenance. Alerts routed to the facilities team, with a history per asset.
For developers: the cheapest time to design this is before the electrical
drawings are frozen. A unit specification that is repeated 40 times needs a
standard bill of materials and a standard handover — not 40 bespoke systems.
03 — Offices & retail
Occupancy is
the control signal.
Most office cooling runs on a timetable written for a different decade. The building does not know that half the floor is empty on Friday, or that one meeting room has been booked since 8 a.m.
Meeting rooms
Calendar-aware cooling and light that starts before the meeting and stops when the room is empty. No more arctic rooms with the door propped open.
After-hours
A single “working late” button that gives one zone 90 minutes of air, then puts it back. Out-of-hours energy stops being invisible.
Lighting zones
Daylight dimming at the perimeter, presence in corridors and washrooms, and a cleaning mode that does not run the whole floor at full brightness.
Access & visitors
Door schedules, one-time visitor codes, and an audit trail that matches the booking system rather than a paper register.
Retail & F&B
Open and close scenes, signage and lighting schedules, shutter and access, and a temperature alarm that calls someone before the stock does.
The floor view
One screen per floor: what is on, what is empty, what is using power, and what changed since yesterday.
04 — Factory & warehouse
Factory automation
of the building.
A factory’s bill is mostly machines, but the building around them is where the easy savings are: lighting left on over an empty aisle, ventilation running at full when the line is down, and no idea which feeder is costing what.
We automate the building envelope and the services that support production — not the production line itself. That line is deliberately narrow, and it is where most “factory automation” enquiries actually belong.
In scope
- Lighting zones by aisle, bay and shift
- HVAC, ventilation and exhaust scheduling
- Energy sub-metering per line, feeder or tenant
- Access control, gates and visitor logs
- Leak, temperature and power-quality alarms
- A plant dashboard for the engineering team
Out of scope
- PLC programming and machine control
- SCADA and production scheduling
- Robot cells and machine safety systems
- Process instrumentation and control loops
- Lifting equipment and pressure systems
- Anything that needs a certified industrial controls contractor
Why the line matters: a building-automation layer that touches a safety
circuit is a liability, not a feature. If the work needs a PLC, we will introduce
you to an industrial controls contractor and design the building layer around them.
05 — Limits
What we
will not do.
The fastest way to lose a building project is to pretend to be something you are not. These are the boundaries we hold, even when the brief asks for more.
- Replace a working BMS to sell a new one. We integrate or meter around it.
- Touch fire detection, suppression or the means of escape.
- Control production machinery, safety interlocks or lifting equipment.
- Put tenant systems on a shared cloud account the landlord controls.
- Promise savings before a metered baseline. The number comes from your meters, not our model.
- Design a system only we can maintain. Documentation and credentials are part of the handover.
06 — How it runs
Pilot. Measure.
Then roll out.
A building is too expensive to automate on faith. We start with one floor or one building, measure it against your own baseline, and only then write the rollout.
-
The walkthrough · half a day
Meters, distribution boards, plant, access, the BMS if there is one, and the people who run the building. We leave with a device count and a data plan.
-
The baseline · 2–4 weeks
Meter the pilot area before changing anything. The savings case is built from your consumption, not an industry average.
-
The pilot · 60–90 days
Lighting, cooling, access and metering on one floor or one building. Measured, reported and reviewed with the facilities team.
-
The rollout
A standard specification per unit or floor, a bill of materials, a commissioning checklist and a handover pack that repeats.
07 — Questions
The building
questions.
The ones that come up before a commercial project starts. If yours is not here, a call is a better use of ten minutes than another page.
Do you do factory automation or only building automation?
We do the building, not the production line. That means lighting zones, HVAC and ventilation, energy sub-metering, access control, leak detection and a plant dashboard. We do not take on PLC programming, SCADA, robot cells or machine safety — those belong to an industrial controls contractor.
Can you automate a block of flats or a property portfolio?
Yes. The usual model is one system per unit with a master dashboard for the operator: per-unit energy, access and vacancy mode, plus a shared view of common areas. It suits serviced apartments, co-living, build-to-rent and small developments.
Will it work with our existing BMS?
Often, yes. We integrate over Modbus, BACnet or an existing API where the BMS exposes one, and read the plant rather than replace it. If the BMS is closed, we meter around it and keep the new layer separate.
How is a commercial project priced?
Per building, after a survey and a metered baseline. Portfolios are priced per unit with a common specification. We usually propose a pilot floor or one building first, measure it for 60–90 days, and only then roll out.
Can you work with our facilities team?
Yes. The system is documented for the people who maintain it: device list, network map, scene and schedule list, alarm matrix and escalation. We train the facilities team and leave the credentials with the owner.
What happens if the internet goes down?
Lighting, cooling schedules and access keep running locally. The dashboard and remote alerts need a connection, but the building does not. Critical access and safety functions are designed to fail safe, not fail open.
Keep reading
Go deeper.
Next
Start with the meter,
not the pitch.
Send twelve months of bills, a single-line diagram if it exists, and the floor you would pilot. We will tell you what the building is doing, what is worth automating, and what the pilot would cost.
Pilot first · metered baseline · no obligation