Skip to content
WINNIIO
Building automation

From Building Automation to Automated Buildings

Making buildings understandable, interoperable, secure and continuously improvable.

WINNIIO helps organisations move from fragmented building systems to secure, interoperable and increasingly automated buildings by connecting engineering, information, operational data, people and AI around the physical reality of the asset.

Few people anywhere have worked this problem from the sensor to the boardroom — from BACnet frames to national strategy — for as long as we have. At Go-IoT, that work spanned roughly 500 buildings across a portfolio. This is what being among the best in the world at building automation actually looks like: receipts, from 2018 onward — Cheating Death by 1000 Cuts (2018) and Wireless-First Strategy (2020), both on AutomatedBuildings.com.

One of our main arenas

Smart Buildings.

From indoor climate and room control to portfolio connectivity, BIM-to-operations and AI on the edge — smart buildings are where WINNIIO's methods were forged.

Smart BuildingsBuilding AutomationIndoor ClimateBACnet & InteroperabilityWireless MeshBIM → OperationsEdge AICybersecurity
01 — No longer a silo

Building automation is no longer a silo.

What used to be a standalone controls discipline now touches every layer of the building and its portfolio.

Indoor climateEnergyElectricalFire & safetyOperationsCybersecurityBIMIT / OT / IoTPortfolioAIOutcomes
Read more

Strategy work for a leading BIM orchestrator — who wanted to take the next step in delivering information across the lifecycle, toward connected buildings, and needed a blueprint — identified the shift six years ago: hardware/software separation, open interoperable systems, standardised APIs, local control, cloud augmentation, wireless-first design, metadata and AI at the edge.

Hardware / software separationOpen, interoperable systemsStandardised APIsLocal controlCloud augmentationWireless-firstMetadataAI at the edge

The harder problem was changing building behaviour without dependence on proprietary tools and vendors.

Diagram separating a building's hardware layer from its software layer, connected through open, standardised interfaces
Hardware / software separation — the founding principle behind every point below it.
02 — Lifecycle

The building lifecycle.

Strategy & early planning

Reverse-engineer from outcomes, not from a product list.

Read more
  • Start from the operational outcome the building needs to deliver, then work backward into systems architecture.
  • Define interoperability, data ownership and automation ambition before procurement — not after.
  • Set the taxonomy and tagging convention early; retrofitting it later is the expensive path.

New construction

Operationally ready, not construction-complete.

Read more
  • Construction-complete and operationally ready are different milestones — commissioning must prove the latter.
  • BIM-to-BAS handover with verified point lists, not just as-built drawings.
  • Cybersecurity and network segmentation designed in from day one, not bolted on at close-out.

Existing buildings

Pragmatic modernisation over rip-and-replace.

Read more
  • Retrofit connectivity and interoperability onto legacy BAS without forcing a full system replacement.
  • Prioritise the systems and data points that unlock the next decision, not the ones easiest to sell.
  • Wireless-first sensing to close data gaps cheaply where wiring is cost-prohibitive.

Operations & continuous improvement

The twin is a working tool, not a one-off deliverable.

Read more
  • Continuous commissioning: the building is monitored and re-tuned, not just handed over and left.
  • Feedback loops from operations back into design standards for the next project.
  • AI recommendations grounded in real operational and engineering context — not generic building benchmarks.
03 — Practical experience

Practical experience, not theory.

Product owner and PM for Swegon WISE and Indoor Climate Designer — applications used to design indoor-climate solutions for hundreds of buildings, spanning wireless mesh sensing and hardware/software coordination.

Read more

Styrprojektering (controls engineering design) experience covers design, architecture and review depth; formal inspection sign-off is a more limited part of that scope. WINNIIO does not claim one person should replace every specialist — the value is in connecting the specialists around a shared, interoperable picture of the building.

04 — Portfolio connectivity

BACnet, IoT and portfolio connectivity.

At Go-IoT, connectivity work spanned roughly 500 buildings across a portfolio — BACnet over web services, the edge-to-cloud chain, and semantic tagging to make that data usable at scale.

Read more

Public record from that period:

The edge-to-cloud data chain — from BACnet devices through gateways and semantic tagging to portfolio-wide analytics
The edge-to-cloud chain that made ~500-building portfolio connectivity workable.
05 — Wireless-first

Wireless-first, but fit for purpose.

Wireless-first where it improves deployment, flexibility and lifecycle economics. Wired where safety, latency, reliability, power or operational criticality requires it. Open and interoperable in both cases.

A triangle weighing cost, reliability and deployment flexibility when choosing wired versus wireless building sensors
The IoT selection triangle — how the wired/wireless call actually gets made.
06 — Context layers

BIM, CIM, GIS and operational context.

Four roles, one shared reality: BIM sets design context, GIS/CIM sets the wider context, automation carries operational state — the twin is what connects them.

Read more

The EU Construction Products Regulation points toward interoperability with BIM as part of how construction product information should be exchanged — Regulation (EU) 2024/3110.

07 — Shared language

Taxonomies, ontologies and a shared building language.

22.4 is not just a number — without a shared tag, it could be a temperature, a flow rate or a fault code. Taxonomy is what turns a raw point into meaning.

BACnetHaystackBrickRealEstateCoreIFCBIMGIS/CIMKnowledge graphs
08 — Boundary objects

Digital twins as operational boundary objects.

A twin has to work across roles that don't share a vocabulary — facilities, engineering, IT, security, sustainability. It spans those stakeholder boundaries by giving each of them a shared, queryable representation of the same physical reality.

The digital twin maturity journey, from a shared boundary-object picture through to autonomous, human-orchestrated operations
The twin maturity journey — see the full ladder on /method.
09 — AI with context

AI with engineering context.

ObserveUnderstandRecommendSimulateApproveActVerifyLearn
Read more

The EU AI Act (Regulation (EU) 2024/1689) frames the direction: explainability, boundaries, and human authority before autonomy.

10 — Cybersecurity

Cybersecurity and post-quantum readiness.

You must know what exists, how it is connected and who can access it before it can be protected.

Read more

That principle came out of the same engagement's security work. It maps directly to NIS2 and the Cyber Resilience Act — and to cryptographic agility for buildings whose systems outlive the crypto they were built with.

A building's full attack surface — devices, protocols, networks, remote access, people and suppliers, treated as one connected surface
One attack surface, defended as a whole — attackers don't respect your org chart.
11 — Regulatory direction

European regulatory direction.

Read the regulatory map

Building automation becomes the operational evidence layer connecting regulation, sustainability, energy, resilience and customer outcomes.

12 — What WINNIIO delivers

What WINNIIO delivers.

Strategy

Building automation and automated-building strategy, reverse-engineered from outcomes.

Connectivity & Interoperability Architecture

BACnet, IoT and portfolio-wide connectivity design across hardware and software layers.

Automated Building Roadmap

A staged path from status monitoring to closed-loop, human-orchestrated automation.

BIM-to-Operations

Connecting design-time BIM context to live operational and automation data.

AI & Twin Readiness

Assessing whether your building data and systems are ready for AI with engineering context.

Secure Building Systems

Cybersecurity and post-quantum readiness for systems that outlive their crypto.

Product & Offering Development

Shaping building-automation products and offerings with real deployment experience.

Change & Capability

Changing building behaviour without dependence on proprietary tools and vendors.

Innovation Ecosystem Design

Designing the collaboration arena between vendors, operators and standards bodies.

Every offer above follows the same staged path — see the full twin maturity ladder on /method for where each stage compounds.

13 — Take it with you

Two field guides, free.

The working material behind everything above — the protocol trade-offs, the integration traps, and the route from a building you cannot read to one that answers questions.

Field guide · 35 pages

Building Automation Understanding

BACnet and Modbus in practice, local control vs the cloud, metadata standards, and why the data strategy decides what a building can ever become.

Field guide · 23 pages

Intelligent Buildings Approach

Separating hardware from software as the north star — three routes to smarter buildings: new construction, existing systems, and buildings with no logic at all.

Connect reality. Understand context. Test decisions. Improve outcomes.