Introduction

The Lumina Operation Center allows you to download schematics from an Avelon server (Avelon Cloud or Alcedo Inhouse). These schematics can then be displayed and operated on its touch display without an active connection to the server or the Internet. The device is able to autonomously communicate with PLCs in the local network.

To achieve this, the Lumina Operation Center is running a local instance of the Avelon cloud platform, as well as a virtualized instance of the Beetle services.

The device only has to be connected to the Avelon server when new data needs to be synchronized, such as changes on the schematics. The base system will try to synchronize data to the Lumina Operation Center once per day. In order to configure which schematics should be synchronized, create an export set and assign it to the Lumina Operation Center on the configuration page of the device.

During the synchronization process, the dashboards and widgets from the selected export set will be synchronized from the base system to the panel. The synchronization also includes data points, alertings, alarm chains and user accounts, among other things. Any changes made on the Lumina Operation Center will be overwritten with the data from the base system, except changes written to the PLC and their corresponding log entries.

In fact, log entries for values written to the PLC will be sent from the Lumina Operation Center to the base system and are therefore persisted across synchronizations.

Limitations of alarm tickets

You can make changes and add comments to tickets, but those changes will get lost during the next synchronization.

The same applies to new tickets that are created for local alarms. These tickets are created on the Lumina Operation Center, but they will get lost the next time the system is synchronized with the base system (typically every 24 hours).