Smart Buildings / BMS

Bring building systems into one operational layer.

Connect lighting, energy, environmental and building-control systems through a configurable platform.

Book a DemoDiscuss this Solution

Three buildings with a rooftop HVAC unit and an electrical panel connected to the Vision Smart Platform core, with a chart comparing consumption between buildings

One model, many buildingsEach site is an IoT system described the same way as every other.
Policy applied onceA schedule or threshold is a rule, not forty manual changes.
Comparable across the estateShared units and timestamps make buildings honestly comparable.

Challenge

A portfolio of buildings is a portfolio of systems.

Each building works. The difficulty starts when you own forty of them and want one answer.

Every building has its own stack

Lighting, HVAC, metering and access were installed at different times by different contractors, each with a separate interface.

Comparison is manual

Asking which building consumes the most, or which one runs longest out of hours, means gathering exports from several systems.

Changes do not travel

A policy agreed centrally — a schedule, a threshold, a setpoint — has to be re-applied building by building.

Architecture

One model across the whole portfolio.

Each building becomes an IoT system with its own inventory and dashboard, described the same way as every other. The exact architecture is configured around the systems, protocols and processes already in place.

Building systemsLighting, HVAC, metering, sensors

›

Controller or gatewayLocal control per building

›

NetworkEthernet, LTE, LoRaWAN, MQTT

›

Protocol instanceContainerised service per protocol

›

Vision Smart PlatformPortfolio registry and screens

What each stage becomes in the platform

A building becomes an IoT systemIt carries its own inventory, its own operational dashboard, its own retention policy, and the customer and integrator responsible for it.
Equipment becomes instancesA luminaire in one building and the same product in another are two instances of one version — described once, deployed many times.
Readings become comparable metricsShared units of measure and data types are what make two buildings comparable at all.
Policy becomes rulesA schedule or a threshold is a rule with conditions on metrics, parameters and time — applied where it should apply, not retyped per site.

Operational scenario

A policy that has to reach forty buildings.

The test of a portfolio system is not the first building. It is the fortieth.

Illustrative example

1

The policy is decided centrally

A change to out-of-hours behaviour is agreed once, for a class of equipment rather than for a location.

2

It is expressed as a rule

Conditions on time, occupancy or a measured value, combined with AND/OR, with a priority relative to other rules.

3

It applies to the right scope

The rule acts on devices, groups or systems — so a floor, a building or the whole class, without retyping it.

4

Commands carry it out

Where equipment accepts commands, the command template supplies the parameters and names the metrics that confirm them.

5

Results are comparable

Because the metrics share units and timestamps, the effect can be read across buildings rather than described anecdotally.

6

The change is on the record

The audit trail keeps who changed the rule and what the value was before.

This example is illustrative. Which policies exist, and which equipment can act on them, are decided by the deployment and the systems already installed.

Operational scenario

Occupancy / environment event
Rule
Lighting / HVAC command
Updated state

Outcome

Integrated operations across building subsystems.

 

Inside the platform.

Vision Smart Platform instrument list for a building: light fixtures and a gas meter grouped as simple devices under one IoT system

What it is built on

The platform capabilities behind this solution.

Use the documented device, data, automation, visualisation and integration capabilities to build a portfolio layer around the building systems you already run.

Digital Twins & Device Lifecycle

Building equipment as models, versions and instances, with each building an IoT system of its own.

Explore ›

Data, Metrics & Commands

Metric templates that normalise readings, and command templates with response validation.

Explore ›

Rules & Automation

Schedules, thresholds and conditions combined with AND/OR, applied to devices, groups or whole systems.

Explore ›

Dashboards & Visualization

Portfolio and per-building screens, defined per version and per installation.

Explore ›

Enterprise Administration

Organisational units, units of measure, data types, states and the holiday calendar.

Explore ›

Security & Audit

Roles and permissions per organisational unit, with a change history on practically every entity.

Explore ›

Fit with what you already have

Existing building systemsEquipment is described by its model and version, so a mixed estate is normal rather than exceptional.
Existing local controlLocal logic and safety stay where they are. The platform is the portfolio layer above them.
Existing systemsIntegration APIs let facilities, energy or reporting systems read the same values instead of keeping a copy.
Who can do what, whereRoles, permissions and the organisational structure decide access — per unit, not per person per building.

See how Vision can fit your deployment.

Share your current devices, connectivity and operational objectives.

Discuss your project