Skip to content

Edge Device

Overview of the Edge Device provided by the aedifion GmbH.

Overview

The aedifion Edge Device is an industrial PC enabling data connection between local devices as well as local data sources and the aedifion.io cloud platform. It uses most IP based industry bus communication standards and is able to automatically ingest data from your plant, building or district using auto-discovery of all available datapoints and devices for easy set-up.

The Edge Device is connected to the internet. If a plant's automation network has no internet connection, it uses its second Ethernet adapter to connect to the Building Automation Network.

The Edge Device operation is fully plug-and-play from the customer perspective. Once connected to the internet, the Edge Device connects to the aedifion.io platform where aedifion's staff take care of its configuration.

edge-device
Figure 1: aedifion's Edge Device

The Edge Device offers very high security since its communication is unidirectional only. Clients do not need to open up their firewall for incoming connections. For outgoing connections only a few standard ports are necessary, such as 22 (SSH), 123 (NTP), 443 (HTTPS) and 8884 (MQTT). In special cases, this can even be limited to HTTPS only.

The Edge Device offers multi-core computation power accounting for diverse edge services, such as cloud-control, fallback functions, operation of local control algorithms, data buffering and so forth.

Learn more? Go through the security section for further information on how we approach IT security and take a look at the Edge Device subpage for system integrators and IT admins.

Integrations

The aedifion Edge Device can speak to a variety of third-party systems via standardized protocols and APIs. These are integrated as plugins which are divided into four categories:

  • Loggers collect measurement and meta data from a data source, e.g., sensor readings from the building automation network
  • Publishers send data collected by loggers to a data sink, e.g., to an MQTT broker or database
  • Subscribers wait for commands from another controller, e.g., to write a setpoint for a room temperature
  • Writers act on received commands and execute them on the target system, e.g., write a setpoint on a BACnet device

Edge device plugin architecture
Figure 1: Plugin architecture of the Edge Device

The following integrations are available:

Integration Logger Publisher Subscriber Writer
Archibus - -
BACnet - -
Comgy - - -
Cumulocity - - -
Discovergy - - -
GeorgFischer Hycleen - -
Influx - -
Kafka () -
KNX - -
Kolibri - -
Microsoft SQL - - -
Modbus - -
MQTT () -
OPC UA - - -
RDM DM - -
S3 - - -
Thing-it - -
ZennerIoT - -

= available, () = available on demand, - = not applicable, = not supported by third party


Last update: