Qisense AI Technology CenterQISENSE / PHYSICAL INTELLIGENCECollaborate
Back to applications
SCENARIO DESIGN / 04

Edge–cloud coordination: keeping spaces working offline

Qisense AI Technology Center2026.10 · Application design

The on-site question

On-site experiences cannot depend entirely on continuously available remote services. Basic lighting, exit actions and human takeover need defined behavior during network outages, slow model responses and device maintenance.

Interaction & system design

Separate local rules from remote content services. Edge systems handle event deduplication, baseline states and recoverable responses. Remote services process delay-tolerant content and distribute configurations. Every configuration change needs a version record and rollback path.

Validation approach

  1. Specify which local responses remain available offline.
  2. Simulate expired configurations and service timeouts. Inspect feedback and rollback.
  3. Record how states realign after reconnection.
Discuss your space
DEPLOYMENT PLAYBOOK

From pilot to operations: what delivery includes

Define delivery boundaries at the outset. Start with an observable, reversible response and validate a small pilot. Combine device settings, rule versions, site tests and rollback procedures in one handover record so maintenance does not depend on the original developer.

Delivery stages & outputs

StageWhat to recordWhat to check
Define the pilotTarget zones, trigger conditions, connected devicesSpecify behavior outside the pilot scope
Engineering acceptanceOffline behavior, false triggers, power recovery, manual overrideReturn to a predefined baseline after faults
Maintenance handoverConfiguration backups, change history, inspection checklistRollback to an accepted version

Exception handling & manual override

Stop automatic rules that depend on an offline device while retaining baseline lighting and manual controls. Give manual overrides explicit priority and recheck device connectivity before restoring automation. Log false, repeated and missed triggers separately rather than masking zone configuration issues with increased sensitivity.

Delivery checklist

  • Zone and device inventory: location, purpose, connection method and maintenance owner.
  • Coordination rules: triggers, cooldowns, priorities and cancellation conditions.
  • Acceptance records: normal flows, exceptions and human takeover replays.
  • Operations manual: inspections, configuration backups, content updates and fault rollback.