Based on the IEC 61499 standard, VION offers an event-based logic engine whose operation can be distributed across almost any number of physical and virtual gateways. Time-critical controls remain on site - where they belong.

Thanks to the actor-based architecture, the system scales automatically from the individual plant to the building portfolio. Standardized interface contracts between logic modules make it possible to develop control logic once and use it everywhere .

The distributed architecture normally remains invisible to developers. If you want to exploit its full potential, you can make it visible and use it in a targeted manner.

DALE - the Distributed Actor-based Logic Engine - currently supports C# as the optimal balance between simplicity, performance and reliability. Other languages - Python for an easier introduction, Rust for even more performance and reliability - are in the pipeline.

VION does not tie integrators to specific manufacturers. The platform consistently abstracts all hardware interfaces - sensors, actuators and controllers from a wide range of suppliers appear in a standardized data model.

The "Everything over MQTT" approach also applies to classic bus systems such as Modbus, CAN or KNX. This means that customer hardware specifications can be adhered to, suppliers can be changed if necessary - and logic modules remain untouched.

This opens up retrofit scenarios that would be unthinkable with conventional approaches.

A resource-saving MQTT broker and flat buffers as a serialization format ensure minimum latency and maximum throughput. The integration of additional hardware platforms requires little effort.

VION relies on open standards throughout. REST APIs for system integration and MQTT for real-time data are available in the cloud - also via WebSockets if required. On site, logic modules communicate with standard bus systems such as Modbus, CAN or KNX as well as with analog and digital I/Os.

All communication, both local and to the cloud, runs via MQTT. If required, the information flow can be bridged to additional brokers or third-party systems can be docked to the local broker in order to react locally to events.

This openness allows integrators to seamlessly embed VION into existing IT landscapes and control systems and avoid proprietary lock-ins.

VION reliably updates firmware, software components and logic modules remotely. Only components that have actually been changed are downloaded. This saves bandwidth and speeds up the rollout, especially for large fleets.

Before installation, the system checks dependencies between logic modules and resolves them automatically. Signed software packages ensure that only authentic, unmodified components reach the gateways.

If an update fails, an automatic rollback takes effect: the gateway automatically reverts to the last functioning status. On-site deployments only take place if they are planned and not because an update has gone wrong.

The status of each rollout is monitored and visualized live. Integrators can see at a glance which gateways have been updated, which are pending and where action is required. Security updates thus reach the entire fleet within hours instead of weeks.

All telemetry data and logs are collected and stored centrally and can be viewed live, allowing integrators and end customers to analyze historical data and monitor current system statuses in real time.

The platform handles data compression and retention management, while local data collection and caching ensures that no data is lost even if the connection is lost. Time-consuming on-site diagnostics become the exception.

Thanks to the Open Telemetry standard, telemetry data can also be easily forwarded to third-party systems.

VION versions all configurations automatically. Every change is documented and can be tracked historically at any time. In the event of incorrect changes, integrators can roll back to a working version with just a few clicks.

Logic modules and configuration templates are managed centrally in libraries. Changes to a module can be rolled out in a targeted manner or deliberately withheld where stability has priority. This eliminates configuration drift and makes deployments reproducible.

Integrators can maintain release notes for each new version of their libraries and thus clearly document changes to commissioning teams and end customers. Communication remains with the integrator, VION provides the structure.

VION follows a zero-trust principle: all devices, accounts and third-party systems are given a cryptographically secured, unique identity. All actions and their triggers are traceable and permanently logged.

Users and third-party systems authenticate themselves via OpenID Connect. Gateways and service components use short-lived certificates (mTLS) that are automatically rotated. This means that every connection, whether to the cloud or between components, is protected against spoofing and man-in-the-middle attacks.

Multi-factor authentication and single sign-on are available for additional security. Together, these mechanisms form the basis for compliance requirements and auditability in critical infrastructure.

Simple projects should remain simple, complex projects clear. VION allows free hierarchical structuring, the levels of which are defined by the integrators themselves. A housing estate, for example, can be divided into buildings, apartments and rooms. An industrial complex consists of sites, divisions, plants and machines. A small energy management system also manages without any additional levels.

Accounts are authorized individually or as groups. Role-based access management takes effect at every level and automatically assigns authorizations downwards. This means that everyone quickly and easily receives exactly the rights they need for their tasks. When structural changes are made, the system shows which authorizations are added or removed as a result. This prevents uncontrolled expansion of rights and confusion caused by suddenly missing rights.

Clear displays show at a glance who has which role where and which authorizations are associated with it. This creates transparency for integrators and makes audits easier.

VION separates clients at data, configuration and access level. In the standard model, all clients share a common infrastructure with logical isolation at database level. This is cost-efficient and sufficient for most scenarios.

Where stricter requirements exist, the separation can be reinforced: with a separate database, separate user administration or both. For large integrators with particularly high compliance requirements, VION offers fully dedicated cloud instances with their own resources.

Support for self-hosted private cloud instances is being planned.

This allows each integrator to choose the level of isolation that suits their requirements and budget.

End-to-end encryption, mTLS, role-based access control and auditable certificate chains form the foundation of our security concept.
The architecture is already based on ISO 27001 and official certification is planned for 2026.
EU Data Act requirements are continuously incorporated into the design and development process and ensure long-term compliance and transparency.

Unlike many other IoT platforms, VION evaluates alarms directly on site. Alarms are reliably triggered and logged even if there is no internet connection. This guarantees fast response times regardless of network failures or problems with service providers.

Integrators can provide logic modules with standard alarms that are automatically available for every instance of the module. In addition, individual alarms can be configured for each project based on freely definable conditions.

Each alarm can be assigned to one or more accounts. These specify via their notification settings whether and how they want to be informed: by email, SMS or webhook.

All alarms are aggregated and historicized in the cloud. This allows integrators and end customers to keep track of current and past events.

In addition to the logic modules, individual If-Then-Else logics and schedules can be defined for each project. The conditions can be combined with logic operations (AND/OR) as required. Measured values and states from the logic system as well as system states can be used as input values. This creates flexible rules that go far beyond simple threshold value monitoring.

Rules are created via a visual interface and are also available to end customers if required. This speeds up commissioning and enables trained users to make simple adjustments themselves. Integrators save time on routine tasks and can concentrate on more demanding aspects.

The evaluation takes place entirely on site on the gateway and works independently of the cloud connection. Whether the current configuration has been successfully synchronized is visible at all times. Executed logics, schedules and errors are logged and collected centrally. This provides clarity about the status on site at all times, even remotely.