HXA BUILDING AUTOMATION
A building that knows what comes next.
Building automation for businesses that look ahead. HXA connects planned room use with connected building systems. Our goal: AI-assisted operation that prepares for people and uses energy according to demand.
The next use of a room starts in the calendar.
Tomorrow’s nine o’clock meeting is already in the calendar. A room booking tells you when a space will be needed. Current device states and connected sensors add information about what is actually happening in the building. Together, they create a basis for control that considers upcoming demand.
Planned use
Room bookings and calendar events provide context: which room will be needed, and when? Changes and cancellations are part of that picture.
Current conditions
Available device and sensor data enrich the plan. Depending on the installation, this can include temperature, air quality and occupancy.
Appropriate action
Defined rules connect this information to room functions. Preparation times, comfort limits and manual controls are specified for each project.
Building automation. Informed by tomorrow’s plans.
For HXA, “knowing the future” means incorporating a building’s planned use into its operation. A populated calendar becomes valuable information for lighting, heating and ventilation.
HXA Building Automation describes this overall approach. HXA Environment Control provides the interface and integration for specific room functions. The Automation Portal brings configuration of connected resources together.
Our vision: a building prepares for its next use and adjusts its operation when plans change.
Designed around AI. For operation that looks ahead.
We are developing HXA with the aim of using artificial intelligence to connect planned use, current conditions and patterns of use more effectively. AI is intended to help estimate demand and refine how rooms are prepared.
Forecast demand
Development goal: use bookings and suitable historical data to estimate when rooms are likely to be needed. Forecast quality depends on the available data.
Refine preparation
Development goal: account for how a room responds to heating or cooling to suggest suitable preparation times. Equipment, building characteristics and comfort targets define the parameters.
Evaluate impact
Development goal: compare expected use, actual operation and available measurements. This should make deviations visible and support gradual improvements to operating rules.
AI outlook: these capabilities describe our development direction. Availability, data requirements and scope are agreed for each project. Connected room functions and configurable calendar-based workflows provide the existing foundation.
A working day. Prepared in advance.
Here is an example of a coordinated office workflow. Times and actions are illustrative and are adapted to your building.
-
Prepare
A room is booked from 09:00. A configured rule starts preparation using the lead time defined for that room.
-
Use
The agreed room functions are ready for the meeting. Employees can adjust permitted settings through Environment Control.
-
Reassess
After the meeting, configured logic uses the next booking and available state information to determine the appropriate operating mode.
-
Reduce demand
Agreed idle or setback rules apply to rooms that are no longer needed, while maintaining essential background functions.
Lighting, climate and spaces. Connected by context.
Lighting control
Control lighting through connected devices and include it in time-based or event-based workflows, covering meetings, focused work and the periods in between.
Heating, ventilation and cooling
Connect climate control with planned room use. Available setpoints and operating modes depend on the system, interface and configuration.
Room automation
Define recurring workflows for meeting rooms, Smart Cubes and flexible office spaces. Calendar events can trigger the appropriate sequence.
Sensors and device states
Incorporate available information from connected devices into operation. Data points, update intervals and behaviour when values are missing are specified during setup.
Privacy and equipment
Bring Smart Glass and other suitable room components into the control interface, allowing comfort and room equipment to be considered together.
Central configuration
Configure connected smart modules and resources in the Automation Portal. Examples include relay modules, Shelly devices and smart lighting.
Efficiency starts when operation matches demand.
An unused room does not always need the same operating conditions as one with an upcoming meeting. Predictive building automation provides a basis for preparing comfortable conditions in time and avoiding unnecessary running hours.
Prepare selectively
Align preparation times with the room, equipment and planned use. The aim is to reach the required conditions when use begins.
Limit idle operation
Reduce running hours where no use is planned and technical requirements allow it. Include calendar changes in the operating plan.
Evaluate impact
Compare before and after: for example running hours, energy consumption and comfort where measurements are available. Account for weather and occupancy when evaluating results.
Achievable savings depend on the building, baseline operation, data quality and integration. We define measurable targets together, rather than assuming a universal savings percentage.
Coordinated operation. With your existing systems.
Start with an assessment of your existing rooms, calendars, sensors and controllable devices. Which information can be exchanged reliably? The answers form a practical integration plan.
Microsoft 365 & HXA
Room bookings and calendar events establish the link to planned use. Resource setup, permissions and required calendar information are agreed during implementation.
Devices and interfaces
Environment Control supports interfaces including HTTP, HTTPS and MQTT. For each device, we assess which values can be read and which actions can be executed safely.
Existing building management
Integration of additional systems depends on their interfaces and available gateways. Protocols, responsibilities and fallback behaviour are established before implementation.
Further topics such as energy management, charging infrastructure or workflows spanning multiple buildings are considered during project planning. They are not a universally included feature set.
One ecosystem. From booking to room control.
HXA Environment Control
The interface for lighting, climate and other room functions. Explore operation and setup.
HXA Room Booking
Room bookings as a starting point for planned use. Software and displays for your meeting rooms.
HXA Sparo
Book rooms and desks and organise the working environment. An entry point for employees in the flexible office.
Start with one room. Grow with a clear objective.
Understand use and equipment
We discuss daily routines, recurring workflows and existing equipment. Together, we select a suitable pilot area and measurable objectives.
Connect and test
Resources, calendars and devices are configured. We then test triggers, manual controls and behaviour when appointments change or data is unavailable.
Evaluate and expand
We assess operation against agreed objectives. Proven workflows can be extended to additional rooms and new functions added selectively.
Your questions about building automation.
What does “a building that knows the future” mean?
It refers to use that is already planned: bookings and calendars show when rooms are expected to be needed. HXA uses this context as a basis for predictive workflows. Unplanned events can still occur, so current conditions and defined rules are part of the concept.
What role does AI play?
AI is part of our development direction for predictive building operation. It is intended to help identify usage patterns, estimate demand and derive suitable preparation times. The AI capabilities available for a project are agreed specifically. Calendar-based rules and connected room functions provide the foundation.
How do Building Automation and Environment Control differ?
Building Automation describes the overall relationship between planned use, building data and operating workflows. Environment Control is the specific app and interface for connected room functions such as lighting, heating, ventilation and privacy glass.
Can building automation be connected to room bookings?
Yes. Within the HXA ecosystem, calendar events such as the start of a booking can trigger automation workflows. The resulting actions depend on connected devices and configured logic. Preparation times and behaviour when plans change are defined for the project.
Can existing building equipment be retained?
We assess this using the existing devices and interfaces. Environment Control supports interfaces including HTTP, HTTPS and MQTT. Additional systems may require suitable interfaces or gateways. Compatibility with every system is not assumed.
How much energy can be saved?
A reliable answer requires a baseline measurement and a comparison that accounts for use and operating conditions. Potential savings can come from preparation based on demand and fewer unnecessary operating hours. This does not establish a universal savings percentage.
Which data is required?
Calendar-based workflows need the agreed resource and scheduling information. Additional state or sensor data depends on the use case. Data scope, access permissions, responsibilities and retention are defined during project planning.
How do we get started with HXA Building Automation?
Start with a conversation about your building, workflows and existing equipment. We use this to identify a suitable starting point, such as a meeting room pilot. Objectives, integrations and available capabilities are specified before implementation.
What should your building be ready for next?
Tell us which spaces and workflows you would like to connect. Together, we will identify the right starting point for your predictive building automation.
From a first meeting room to a connected office building: we discuss existing equipment, your objectives and practical next steps.