Connect the site to the software your team already uses.

EpiSensor Edge sits between meters, equipment and the platforms that analyse, report or act on their data. These guides show the complete route: what runs on the Gateway, what leaves the site, and what must be verified at the receiving end.

Find your platform Plan the field system
Example routeCommissioning checkpoints
  1. 01
    Field measurementsModbus · Zigbee · pulse · analogue
  2. 02
    EpiSensor EdgeMap · validate · buffer · transform
  3. 03
    Secure deliveryMQTTS · HTTPS · API · files
  4. 04
    Your platformVerify identity · value · unit · time

A connected transport is one checkpoint. A correctly received reading is the result.

Choose the route with the evidence you need.

We name the basis for every page. A maintained Edge flow, a published customer deployment and a previously documented file route are useful evidence, but they are not the same thing.

Maintained integration flows

Packaged Edge flows that EpiSensor maintains for the named platform.

2 routes
Maintained by EpiSensor Enel XDemand response and virtual power plants Site assetsEpiSensor EdgeSecure MQTTSEnel X Open guide Maintained by EpiSensor IBM EnviziESG and sustainability data management Utility readingsEpiSensor EdgeApproved S3 pathIBM Envizi Open guide

Documented customer deployments

Platforms used in published EpiSensor projects, with a known data path and project evidence.

2 routes
Documented customer deployment EnergyCAPEnergy and utility data management EpiSensor metersEpiSensor EdgeSecure HTTPSEnergyCAP Open guide Documented customer deployment Spacewell EnergyMulti-site energy analytics Store measurementsEpiSensor EdgeSecure file deliverySpacewell Energy Open guide

Documented integration paths

Previously documented platform routes that are re-qualified for each new Edge deployment.

1 route
Documented integration path MRI eSightBuilding energy management software Meter readingsEpiSensor EdgeSFTPMRI eSight Open guide

The integration is a working flow on the Gateway.

Edge reads field equipment, gives each point a stable meaning, reshapes the payload and sends it through the route the platform supports. The same flow can hold or log failed delivery instead of silently losing it.

At the source
Confirm the device, channel, value, unit and sample time.
On Edge
Make mapping, transformation, buffering and delivery observable.
At the platform
Verify the intended asset received the intended reading.
See how Edge integrations are built
Edge flow reading field equipment, shaping a platform message, delivering it over MQTTS or HTTPS and catching errors
One Edge flow: read, transform, deliver and handle errors. The exact nodes and data contract change with the platform.

A protocol opens the route. Commissioning proves the result.

If a platform accepts MQTTS, HTTPS, an API or scheduled files, Edge can usually reach it. That is the architecture, not a claim that every platform has a ready-made connector.

Each guide records the strongest evidence available and then gives the checks that matter in practice: identities, units, timestamps, credentials, buffering, retries and receiver confirmation.

Discuss an integration Choose field devices