“Go edge” is sold as a performance cure. Sites often get more nodes, murky versions and unclear offline behavior. Put these four traps on the risk list before kickoff.
Trap 1: no offline/reconnect plan
If the edge dies without cloud, it is not edge. Local cache, degrade mode and replay must be explicit.
Trap 2: no versions for models/config
Many nodes without a version ledger means human-only rollback. Treat release/canary/revert as seriously as in the cloud.
Trap 3: alerts with no site owner
Anomalies that never reach the shift just move the noise. Owners and ticket loops stay first-class.
Trap 4: no uplink filter
Edge should cut traffic; shipping everything upstream only adds failure modes. Define what must go up.
See IoT architecture and the edge case.
Related products: IoT Platform · AI Engine · Energy Steward