Skip to content
ORLA · Local Adaptive Control Intelligence

One building.
One intelligence.

Local adaptive control for energy systems.

ORLA learns how real installations respond and evaluates actions within operator-defined limits. The same local approach can support a single installation or a coordinated energy portfolio.

Validation starts with HVACBESS and multi-asset coordination require separate validation
HVACBESSPVEVHot waterCoolingORLALOCAL ORLALOCAL INTELLIGENCE
ComfortCostPeakBatteryFlexibilitySelf-consumption
Architecture illustration
01 / ORLA

The intelligence
is in the interaction.

A modern building contains many smart systems. But the best decision for each device in isolation is not necessarily the best decision for the building.

01 / INTERACTION

Kitchen → HVAC

Heat from breakfast preparation changes the actual heating demand of nearby spaces.

02 / INTERACTION

PV → Hot water + BESS

Surplus generation can prepare hot water or charge a battery — depending on what will be needed next.

03 / INTERACTION

EV → Building power

EV charging can coincide with HVAC start-up. Coordinating loads can avoid a shared peak.

How should the whole building operate, considering what happens next?

02 / ORLA

Sense now. Predict next. Decide together.

ORLA combines operational data, forecasts and operator constraints. In the local pilot setup, ORLA and Home Assistant run in separate containers. Home Assistant connects to available data and authorised control points.

01 / INPUT

Sense

Zone temperatures, occupancy, equipment, energy, weather, prices, PV generation and battery SOC.

02 / FORECAST

Predict

Future zone needs, temperature changes, power peaks and the cost of preparing the building.

03 / INTELLIGENCE

Decide

Which resources to use, when and how intensely. Evaluate consequences across the whole system.

04 / ACTION

Coordinate

An approved strategy can act within comfort, process and equipment limits. Operational feedback informs future learning.

Potential objectives

You define the boundaries. ORLA chooses the strategy.

A site can set goals for comfort, cost, demand and flexibility. The available equipment, operating limits and validation determine which goals ORLA can pursue.

COMFORT

Prepare spaces before they are needed.

SAVINGS

Reduce the cost of the whole system.

PEAK

Coordinate demand ahead of the peak.

BATTERY CARE

Use building flexibility before the battery when it makes sense.

SELF-CONSUMPTION

Give local generation its greatest value.

FLEXIBILITY

Offer only a demand change the building can deliver.

Technology evidence

Tested on real operational data.

Two separate HVAC studies used historical BMS data from a real building.

Validated offline

Thermal prediction

0.23°C MAE

1-hour temperature forecast vs 0.27°C persistence baseline.

13 months of BMS archives, four rooms and four held-out monthly tests covering different seasons.

Retrospective simulation

Control strategy evaluation

24–33% lower

Modelled heating-demand indicator vs historical BMS control.

119.5 days, over 34,000 evaluated decisions and four HVAC zones. The indicator is based on valve operation. Metered kWh and bill savings require active M&V.

How the studies were evaluated

The persistence forecast keeps the current temperature unchanged for one hour. MAE is the average absolute difference between predicted and observed temperatures. The retrospective control study compares a candidate policy with historical BMS behaviour using a valve-based indicator.

Scalability

From individual assets to energy portfolios.

Choose where the intelligence runs and how many assets to coordinate. Each step beyond the current edge pilot has its own validation requirements.

Implemented / pilot

Edge / on-prem

Local models, learning and decisions can run on site without a continuous cloud connection. Integration and control permissions are qualified for each site.

Proposed

Cloud

Optional portfolio coordination, analytics, reporting and flexibility aggregation. Execution stays within each site’s local limits.

Development direction

Embedded / MCU

Selected functions could run directly on OEM devices, subject to processor, memory and integration limits. Full ORLA currently targets edge hardware.

  1. Device

    Learn the response of a controllable device.

  2. Installation

    Evaluate actions within process limits.

  3. Building / site

    Coordinate qualified installations against a shared goal.

  4. Portfolio

    Aggregate the flexibility offered by participating sites.

  5. Microgrid / VPP

    Coordinate a portfolio response. Sites retain local execution.

Conceptual path to scale. Portfolio and multi-asset operation require validation.
Cybersecurity by architecture

Cloud coordination. Local control.

A central platform can send an energy objective without direct access to every device. Sites can return the flexibility and telemetry needed to coordinate a response.

  1. Cloud / EMS / VPP

    Sets objectives, coordinates the portfolio, aggregates flexibility and connects to market processes.

  2. Local ORLA / edge

    Models the process, checks operating limits and executes authorised actions. Operational data can stay on site.

  3. Existing BMS / OEM automation

    Retains baseline control, independent equipment protection, safety limits and fallback procedures.

This architecture can reduce remote exposure. Each deployment needs authentication, network segmentation, secure updates, decision logging, withdrawal procedures and security testing. Local operation during a connectivity loss depends on site-tested scenarios.

03 / ORLA

One winter morning. Hundreds of connected decisions.

Explore how a hotel’s context changes. This is an illustrative scenario, not a record from a deployment.

HOTEL / ILLUSTRATIVE SCENARIO
05:30

The building wakes up

It is cold outside. The kitchen will start shortly.

Comfort / prediction
Independently controlled systems

HVAC starts heating according to its schedule.

One ORLA autopilot

ORLA prepares the required zones while accounting for heat gains that will arrive later.

Applications

Starting with HVAC. Expanding toward multi-asset coordination.

HVAC is the current focus of validation. Thermal inertia can help shift demand, while batteries can provide a faster response. Coordinating them with other assets is a development direction that requires site-specific validation.

Illustrative pairing
HVACThermal flexibility
+
BESSFast response
Other potential applications
PV / self-consumptionHot water / thermal storageEV / managed chargingRefrigeration / thermal inertiaIndustrial processes / controllable loads
Illustrative · HVAC + BESS

How much of the response could the building deliver?

A building can contribute part of a demand reduction, leaving the battery to supply the balance. Move the slider to explore the split.

Illustrative allocation for a 100 kW reduction. Effects on battery throughput and lifetime require measurement and verification (M&V).

Required reduction100 kW
BuildingBESS
BESS alone100 kW
BESS 100 kW
Building + BESS100 kW
40 kW
60 kW
06 / ORLA

How much demand can the site change, and when?

A flexibility envelope describes feasible changes against a baseline, given the forecast and local constraints. An EMS, VPP or aggregator could use it to coordinate a response. Delivery must be validated on site.

Illustrative · Office HVAC forecast for 12:00
DOWN · demand reduction2.5 kW
UP · demand increase3.4 kW
Full reduction available45 min
Delay / DOWN ramp5 min / 0.5 kW/min
Comfort band / headroom21–24°C / depends on current state
Confidence score0.82
Rebound vs baseline+1.2 kW peak · 90 min · 0.9 kWh
Request / full delivery11:50 / 12:00–12:45
07 / ORLA

Learn the site. Validate decisions. Enable bounded control.

The five stages lead from data access to controlled activation. Agree on a baseline, stop criteria and return to baseline control before active M&V.

01

Connect data

Link BMS, meters, controllers and sensors.

02

Learn

ORLA learns the dynamics of the actual site.

03

Shadow mode

Evaluate decisions without affecting equipment.

04

Bounded autonomy

Enable selected resources after validation.

05

Expand

Add resources and optimisation objectives.

Every installation is different. Deployment should be repeatable.

ORLA aims to reduce site-specific modelling effort. Point mapping, integration, testing and commissioning still need to be completed at each site.

Modelling-intensive workflow

  1. Analyse the installation
  2. Build and calibrate a site model
  3. Tune the control strategy
  4. Repeat engineering at the next site

ORLA workflow

  1. Integrate operational data
  2. Define objectives and constraints
  3. Learn the installation response
  4. Validate candidates and adapt

For integrators, OEMs and portfolio operators, the pilot measures time to integrate, engineering hours, reuse and maintenance cost. A proposed renewable partner licence can support repeat deployments within an agreed scope.

08 / RETROFIT-READY

Keep the infrastructure. Add the intelligence.

ORLA complements existing BMS, EMS, local controllers and OEM systems. The integration scope is matched to the equipment and interfaces at the site.

BACnetModbusHome AssistantMQTTBMS / EMSOEM
EDGE-FIRST ARCHITECTURE

Local decisions.
Optional cloud.

Sensing, prediction, decisions, control and fallback can run inside the building. Reporting, portfolio monitoring and external integrations can use optional services.

09 / APPLICATIONS

Where to start and where to expand.

HVAC is the validation focus. The applications below illustrate potential uses and require qualification for each site.

Buildings and portfolios

Cost, comfort, power peaks and PV/BESS coordination.

Hotels

Guest comfort, HVAC, hot water and occupancy forecasts.

Retail and refrigeration

Repeatable sites and processes with their own inertia.

EMS, integrators, OEMs

Autonomous intelligence above existing automation.

HOMEMIND / ORLA

Start with a pilot.

Start with a free assessment of your data, equipment and objectives. A pilot can progress from site qualification and shadow to controlled operation and active M&V against an agreed baseline.

Building owner or operator

Assess your building

HVAC / BMS integrator

Become a deployment partner

OEM / technology partner

Discuss technology integration

Pilot scope and success criteria are agreed for each site.