Decide what needs to leave the site
Edge is an on-site system, not just a forwarding service. It provides device configuration, dashboards, data exploration, calculated readings and local automation. Start by deciding which of those tasks stay local and which information an external platform needs.
A cloud service may need periodic energy totals, selected telemetry or events rather than every available reading. Agree the measurements and reporting intervals before choosing the transport or estimating storage requirements.
Use a supported flow, or build one for your platform
Edge supports pre-built and partner-built integration flows. These can adapt site data to the receiving platform's interfaces and message format.
MQTT and HTTP are possible integration transports, not compatibility guarantees. For the destination service, confirm its authentication method, endpoint, payload structure, topic or resource naming, limits and acknowledgement behaviour. An MQTT service can still require a particular device identity and message contract.
Do not assume that an old connector's endpoint or setup instructions apply unchanged to a current platform release.
Map devices and measurements deliberately
Use stable site, device and sensor identifiers. Agree units, timestamp format, time zone and whether a reading is an instantaneous value, a cumulative total or an interval quantity.
Keep quality and availability visible. The receiving application should distinguish missing or stale data from a real zero. If a value is transformed or calculated, document that calculation and preserve a way to relate it to the original readings.
Design for interruptions
Define retry, duplicate-handling and recovery behaviour for the chosen flow. Local storage and queued delivery are bounded by the installed configuration and available resources; they are not a promise of unlimited outage retention or zero data loss under every failure.
Test a controlled network interruption and compare the recovered data at both ends. Agree what should happen to commands and notifications while the destination is unavailable.
Keep access and operations manageable
Use the permissions and credential-handling approach supported by each endpoint. Agree how credentials are provisioned, rotated and revoked, and who monitors failed deliveries. Do not place secrets in public URLs, screenshots or support enquiries.
The Gateway and hardware range provide the site connection. A company's directory profile helps explain its offering, but does not certify a deployment.
For downstream dashboards and reports, see the reporting and BI guide. To plan a new receiving service or flow, talk to the integration team.