IBM Envizi integration with EpiSensor Edge
EpiSensor maintains an Edge flow for IBM Envizi. It maps selected measurements into Envizi utility records, writes reviewable CSV files and uploads them to a deployment-approved S3 destination.
The complete route
Every boundary below has its own configuration and evidence. Treating “connected” as one state is how mapping and delivery errors become invisible.
- Utility readings
Export-enabled measurements with known units and sample times
- EpiSensor Edge
Utility mapping, scaling, identifiers and CSV buffering
- Approved S3 path
Scheduled file upload using deployment credentials
- IBM Envizi
Import into the agreed accounts and reporting hierarchy
What this route does
- Maps exact Export IDs or sensor IDs to receiver-approved utility types and units.
- Writes utility rows with organization, meter identity, UTC timestamp, value and unit.
- Retains pending files for scheduled S3 upload and exposes local write and upload activity.
Prepare both ends before sending data.
The platform administrator and the site engineer should agree the identity and data contract before credentials are installed.
- 1
Obtain the organization, site and building codes plus the approved utility names and units.
- 2
Confirm the S3 bucket, region, folder and Gateway credential configuration with the deployment administrator.
- 3
Choose one meter whose value, unit, timestamp and cumulative-or-interval meaning are already known.
Commission the route in order.
Keep the first test deliberately small. One reading checked end to end is stronger evidence than a busy dashboard whose source is uncertain.
- Configure the approved organization, site code, two-digit building code, delimiter and filename prefix.
- Map one exact measurement and verify the value, unit, multiplier and meter identifier in the local CSV.
- Enable the approved S3 destination only after the local row is correct.
- Verify the expected object in S3 and then verify the imported meter, value, unit and timestamp in Envizi.
- Record the source sample, local file, remote object and receiver confirmation together.
What not to infer
These limits make the guide usable during design review and acceptance, not just persuasive before purchase.
- A CSV write is not an upload receipt, and a successful S3 upload is not proof that Envizi imported the row.
- The flow scales supplied values; it does not derive interval consumption or convert power into energy.
- Unmapped measurements can be omitted without appearing as invalid data, so zero errors is not proof of complete coverage.
Evidence and further reading
Reviewed September 19, 2026 · revision 1. Platform names and trademarks belong to their respective owners; a guide does not imply endorsement unless the linked evidence says so.