⌁
Data connection
Integration of IoT, API, database and external systems.
The layers of a web-based operating system.
One shared, modular environment connects devices, data, users, business applications and executable workflows.
Platform layers
Not monolithic. Not an island system.
The common cores ensure uniform operation, and the modules provide solutions for specific tasks of the organization.
◆
Shared data
Devices, locations, clients and document relationships.
↻
Processes
Events, Notifications, Tasks and Automation.
▦
Applications
Desktop, mobile and field interfaces by role.
Data path
The signal becomes a measure.
A measurement deviation does not stop at the dashboard: it can trigger a notification, a task or a business process.
1
Collection
Provides sensor, meter, gateway or external system data.
2
Context
The data is related to device, location and organizational manager.
3
Evaluation
Interpreted by rule, threshold, trend or business logic.
4
Execution
An alert, worksheet, approval, billing and allocation or report is created.
The platform in operation
Not a promise. Working interfaces.
These anonymised screens show real platform functions. Open any image for a larger view.
Multiple sites on one map
Sites, devices and events appear in a shared geographical operating view.
Energy and system connections
The relationship graph presents grid points, producers, consumers and storage together.
Project and delivery scheduling
Tasks, dependencies and deadlines remain connected to the same project.
Controlled approval workflows
Value limits, approval stages and substitutions create an auditable business process.
Finance and exchange-rate management
Supplier invoices, currencies and MNB-sourced or manually recorded exchange rates are managed in the same business environment.
Platform principles
| Principle | What does it mean in practice? |
|---|---|
| One dataset, one place | Common data is not copied to all modules; functions are associated with the same authoritative record. |
| Modular introduction | You can start with a narrow use case, while maintaining the necessary foundations for later expansion. |
| Integrability | Existing devices and systems do not necessarily need to be replaced; they can be connected via regulated interfaces. |
| Authorization and organizational boundary | Users and devices have access only to the data and operations authorized for them. |
| Traceability | The source of events, automated decisions and business operations can be linked. |