Documented integration path

MRI eSight integration with EpiSensor Edge

EpiSensor previously documented an eSight integration using scheduled CSV delivery over SFTP. For a current Edge deployment, the project team re-confirms the file contract, receiving account and installed export flow.

See the complete route Plan the site system
Edge integration flow showing equipment reads, transformation, secure delivery and error handling
A previously published EpiSensor route, retained as a practical design guide and re-qualified for each current deployment.

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.

  1. Meter readings

    Selected electricity, gas, water or other utility channels

  2. EpiSensor Edge

    Meter mapping, file creation and schedule

  3. SFTP

    Receiving host, account and folder supplied for the project

  4. MRI eSight

    Import into the intended buildings, meters and reports

What this route does

  • Selects the site measurements that belong in the receiving platform.
  • Writes a scheduled CSV feed with the agreed identifiers, timestamps, units and values.
  • Transfers the file over SFTP while Edge retains local history and integration diagnostics.

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

    Ask the MRI or project administrator for the current file specification, SFTP host, account and destination folder.

  • 2

    Define every meter identifier, unit, time zone, interval and cumulative-or-interval meaning.

  • 3

    Confirm which current Edge export flow will own the schedule, buffering and retry behavior.

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.

  1. Build a sample file containing a small, known set of readings and validate it against the agreed schema.
  2. Verify the SFTP host key and destination before installing credentials on the Gateway.
  3. Transfer one file and confirm its arrival separately from its successful import.
  4. Compare meter identity, value, unit and timestamp inside eSight with the source reading in Edge.
  5. Observe a normal scheduled export and document the retry and duplicate-handling rules before estate rollout.

What not to infer

These limits make the guide usable during design review and acceptance, not just persuasive before purchase.

  • The previous guide used the legacy Gateway interface; its menu instructions are not current Edge documentation.
  • SFTP delivery proves only that a file reached the server, not that eSight accepted or mapped its rows.
  • Credentials and host details belong in the approved secret-management path, never in an enquiry form or published example.

Evidence and further reading

  1. Edge platform integrationsEpiSensor
  2. MRI energy management softwareMRI Software
  3. Energy management with EpiSensorEpiSensor

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.