At the facility
Equipment & sensors
Capture temperature, state, consumption, and events
Passes onwardRaw signals
AZIOT Platform
From field signal to operational action
A vendor-independent IoT platform that connects devices, protocols, business rules, and operator interfaces in one controlled architecture.
System architecture
Who does what — from the facility to the operator
Architecture is the division of responsibility between equipment, integration, the AZIOT platform, and the customer team. Each layer receives a defined input and passes a defined result onward.
Customer perimeterAZIOT perimeter
Edge / integration
AZIOT gateway
Reads local systems and unifies MQTT, Modbus, BACnet, and APIs
Passes onwardNormalized data
AZIOT platform
Data & context
Stores history, facility structure, states, and relations
Passes onwardUnified facility model
AZIOT platform
Rules & scenarios
Detects deviations, assigns priority, and triggers the required response
Passes onwardDecision or command
Customer team
Operator & business systems
Receive alerts, manage the process, and verify the outcome
Passes onwardControlled action
Technology foundation
AZIOT combines IoT operations with the UnityBase application foundation
The field layer communicates with equipment. The application layer gives signals business context, access rules, interfaces, and an audit trail. This separation keeps hardware integration distinct from operational management.
Enterprise application foundation
UnityBase provides a metadata-driven domain model, database-independent data access, generated REST interfaces and administration UI. Its documented security layer includes authentication, roles, row-level access controls and audit capabilities.
AZIOT IoT layer
Gateways and adapters receive field signals, normalize protocol-specific values into the facility model, evaluate events and scenarios, send commands, and expose the result to operators and connected business systems.
Logical model
- Connect equipment
- Normalize the signal
- Add facility context
- Apply a rule
- Execute and verify
This is a reasoned implementation model based on the confirmed homepage flow and documented UnityBase capabilities; the exact production configuration requires technical confirmation.
One end-to-end scenario
How a signal becomes a verified action
Not six separate functions, but one traceable chain. Below is a concrete overheating response example.
01
Signal
Sensor: 28°C02
Normalization
Temperature · zone 403
Rule check
> 26°C for 5 min04
Decision
Start ventilation05
Command
Gateway → controller06
Verification
State and result in the logResultThe system acted automatically; the operator sees why, when, and whether the command worked.
Capabilities
What the platform delivers
Integration
Works with your infrastructure
MQTT
REST API
Modbus
KNX
OPC UA
BACnet
WebSocket
RS-485
ONVIF
Wiegand
M-Bus
DALI
Alternatives
Why a platform, and not one more system
Single-vendor BMS
Control is tied to one manufacturer’s equipment: extensions and integrations are possible only within its catalog and pricing policy.
SCADA + separate contractors
Each subsystem has its own interface and its own owner; the overall picture is assembled manually, and every change needs new custom work.
AZIOT
Open protocols, one facility model, and scenarios on top of your existing equipment — no system replacement and no vendor lock-in.
FAQ
Frequently asked questions
Do we have to replace existing equipment?
No. AZIOT works on top of your existing infrastructure via MQTT, Modbus, BACnet, ONVIF, and APIs. Replacement is needed only where equipment physically has no integration interface.
How long does a pilot take?
A typical single-site pilot takes from a few weeks: an architecture session, connection of the key subsystems, and scenarios with the KPI fixed before launch.
Where is the data stored and processed?
Depending on the facility’s requirements: locally at the edge, in the cloud, or in a hybrid layout. Critical logic can run locally and does not depend on the internet connection.
How is the platform secured?
Authentication, roles, row-level access, action audit, and a controlled integration layer are part of the UnityBase application core — not external add-ons.
What happens after the rollout?
Your team receives documentation, training, and access to the settings. We support the system, evolve the scenarios, and connect new sites as needed.