Documented customer deployment

Spacewell Energy integration with EpiSensor Edge

EpiSensor measurements have fed Spacewell Energy in a published retail deployment. The prior Dexma route used scheduled CSV files; a new Edge project confirms the current receiving service and secure transport.

See the complete route Plan the site system
Woodie's retail store in the EpiSensor, ETS and Spacewell Energy deployment
A published 36-store deployment and a previously documented file-export path establish the integration pattern.

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. Store measurements

    Electricity and other agreed meter channels

  2. EpiSensor Edge

    Naming, units, intervals and scheduled file generation

  3. Secure file delivery

    Transport agreed with the receiving administrator

  4. Spacewell Energy

    Portfolio analytics, alerts and reporting

What this route does

  • Collects consistent site measurements across a multi-building or retail portfolio.
  • Generates a platform-specific file feed using stable site and meter identities.
  • Keeps local Edge history and diagnostics available alongside the external analytics platform.

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

    Confirm whether the destination is branded Spacewell Energy or Dexma and identify the current receiving administrator.

  • 2

    Agree the file schema, delimiter, naming, reporting interval, time zone and cumulative-or-interval meaning.

  • 3

    Choose a small number of meters and known source readings for the first import.

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. Create stable site, building and meter identifiers that match the receiving hierarchy.
  2. Generate one representative file and inspect its headers, units, timestamps and decimal format before transfer.
  3. Use the secure transport and account supplied for this deployment; do not substitute FTP, FTPS and SFTP as if they were interchangeable.
  4. Confirm the file arrived, was imported and created readings under the intended meters.
  5. Compare the imported values with Edge, then repeat after a normal schedule boundary before adding the remaining estate.

What not to infer

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

  • The historical guide described plain FTP; a new deployment must agree an appropriately secured transport or network arrangement.
  • A delivered file can still fail import or map to the wrong site, so receiver-side confirmation is required.
  • The published project demonstrates the pattern, not guaranteed savings or an identical configuration for another estate.

Evidence and further reading

  1. Woodie's multi-site energy managementEpiSensor
  2. Spacewell energy management softwareSpacewell
  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.