Why FacilityOS
The advantages below are features of the platform you can check in the live demo — not promises.
Open and brand-neutral
Any brand, mixed on one site
Not tied to any equipment maker: devices with a standard protocol from different brands are monitored together. The model library has 967 brands and 1306 product families, and unknown devices fall back to the generic protocol template.
Learn more →Open, with no data lock-in
Northbound OPC UA server, MQTT Sparkplug B, a REST API and CSV / Parquet export. Your data always belongs to you.
Learn more →One platform
Nine systems, one platform
FMCS, BMS, EPMS, EMS, SCADA, PLC/DCS, CMMS, DCIM and CEMS share one data set, one alarm system, one audit trail and one set of permissions. No separate products to buy and no integration between them to build.
Learn more →Control-room video wall
Each site designs its own boards by drag and drop, shown full screen in 1080p or 4K, with one display rotating through several sites. When the connection drops the whole board says so and shows no old values.
Learn more →AI that advises, never operates
Explains alarms, analyses root causes, writes shift summaries and suggests maintenance. Acting on a suggestion still needs a person and the change approval flow; data is redacted before sending and cost is capped.
Learn more →Safe control
8-step change flow
Request → validate → approve → pre-check → execute → read back → verify → complete. Requesters can't approve their own changes; writes are blocked in manual, fault or when data can't be trusted; success is decided by the read-back; anyone can press emergency stop; commands carry an Ed25519 signature and a lease epoch.
Learn more →Life safety: monitor only
Fire alarm, gas detection and protection devices are read-only in the platform, and the catalog check rejects any change that would make such a point writable.
Learn more →Soft PLC with open programming
Write Structured Text, ladder, function block and sequential function chart programs in the browser and simulate them; signed programs run on the gateway and hand outputs back to the equipment on a fault. The Go, Rust and browser runtimes give bit-for-bit the same results.
Learn more →Reliable data
Data you can trust
Data from a broken or timed-out connection is marked stale and left as a gap on trends; questionable data is never shown as normal.
Learn more →No data loss, control in the field
During a network outage the gateway buffers to local disk and backfills in time order, so history has no holes. Real-time control stays in the field PLCs and DDCs, and gateways only connect outward — no inbound ports at the site.
Learn more →Power-grade precision
Native IEC 61850 client (MMS reports, GOOSE); sequence of events by each device's own time stamp to the microsecond with its clock source; COMTRADE fault records, power-quality compliance and before/after harmonic mitigation.
Learn more →High availability, room to grow
Multi-node primary/standby or active-active with automatic takeover, multiple sites and tenants, backup and restore, 400 days of history in PostgreSQL + TimescaleDB, and deployment on your own servers.
Learn more →Security and compliance
Security and compliance
Hash-chained audit log; device credentials encrypted (X25519 + AES-GCM); TLS everywhere between platform and gateways with one account per gateway; Entra ID single sign-on, server-side permissions, idle sign-out; several rounds of security review. Compliance support for ISA-18.2 / EEMUA 191, IEEE 519 / EN 50160, NFPA 70E, EPA Part 60 / 75, GMP e-signatures, ISO 14644 and ASHRAE Guideline 36.
Learn more →Easy to adopt
Easy for newcomers
Every page explains what it is, why it matters and what you can do, with a guide mode; role-based training with a drill mode whose alarms never touch the real system.
Learn more →Safe rollout
Pilots go read-only → limited control → full control, each step checked and confirmed by two people. A network scan finds devices and drafts the point list; nothing takes effect until a person confirms it.
Learn more →One-stop delivery
From survey and design to procurement, installation, commissioning, training and support — we can do all of it, or only the stages you need.
Learn more →Compared with the traditional approach
| Aspect | Traditional approach | FacilityOS |
|---|---|---|
| Systems | Several separate systems, each with its own screens, alarms and users | One platform for nine systems, with one alarm system and one audit trail |
| Brands | Tied to one manufacturer's ecosystem | Any brand with a standard protocol, mixed freely on one site |
| Remote changes | Writes without confirming the result | 8-step flow with approval and read-back; uncertain results are marked as such |
| Network outages | Gaps or lost data | Gateway buffers to disk and backfills in order |
| Life safety | Sometimes controlled from the same screens | Monitored only; never sent commands |
| Your data | Locked in a proprietary database | Open: OPC UA, MQTT Sparkplug B, REST API, CSV / Parquet |
"Any brand" means equipment with a standard communication interface. Equipment without one is connected through added meters, sensors or dry contacts. Connecting a device still takes a confirmed point list — it is not plug-and-play without configuration. Life-safety equipment is monitored only, never controlled.