Services / 03

Software that reliably connects devices, cloud and business processes.

We develop the software between field device and backend: drivers, edge services, device connectivity, updates and the infrastructure it all runs on. We have particularly deep experience with energy systems and charging infrastructure.

Fig. 01System chain
  1. FieldDevicesSensors · meters · controllers
  2. EdgeGatewayDrivers · logic · updates
  3. CloudPlatformData, portal, operations
  4. ApplicationProcessesBilling · market · service

Every transition is an interface that wants to be tested.

Typical duration
from 6 weeks
Starting point
Architecture and interface review
Deliverable
Production-ready software with tests
Deployment
Edge, cloud or both

Software & IoT Engineering

What is included

  • Edge and gateway software on industrial PCs and embedded Linux devices
  • Device connectivity and cloud integration: MQTT, LwM2M, Azure IoT Edge, AWS
  • Over-the-air updates for devices in the field
  • Protocol integration: Modbus RTU/TCP, CAN, SunSpec, EEBUS, OCPP, IEC 60870-5-104
  • Energy applications: energy management, § 14a EnWG, smart meter gateways, German market communication
  • Cloud and network infrastructure as code: Azure, AWS, VPN
  • Technical analysis and platform assessments: root-cause analysis, architecture review, separation and migration

Situations we keep running into

Every new device is its own integration project

Challenge

Each sensor, each controller and each device from a new vendor gets a special path. The effort grows with every variant.

How we help

We define a shared data contract with validation and develop drivers against it. New devices become configuration instead of a project.

Devices in the field cannot be updated

Challenge

Every change needs a technician on site. Bug fixes and security updates are left undone.

How we help

We build in an update path that is fail-safe and can be rolled back, and we test it before it reaches the fleet.

Nobody knows exactly what the platform contains

Challenge

Before an acquisition, separation or migration, there is no overview of repositories, dependencies and risks.

How we help

We analyse the estate systematically, name the risks and support the work through to a running target environment.

Next step

Let’s talk about your project.

A short conversation usually settles faster than a specification whether and how we can help.