Qisense AI Technology Center2026.10 · Application design
The on-site question
An isolated signal rarely determines the right response. An arrival, a dim room and an explicit user choice are different kinds of input. The system must understand how they combine in time and priority.
Interaction & system design
Organize inputs into event windows while retaining their sources and expiry times. Explicit actions take priority over passive inference. Conflicting signals lead to a low-interference state or a request for confirmation. Site operators should be able to explain and adjust these rules.
Validation approach
List each input's validity window and expiry conditions.
Test rule priorities when multiple events occur at once.
Disconnect one input and check whether others are misinterpreted.
Normalize device outputs into events before deciding whether to trigger a workflow. Each event carries a source, zone, time, type, validity period and quality flag. Treat position changes separately from environmental changes so duplicate reports are not mistaken for repeated visits.
Delivery stages & outputs
Stage
What to record
What to check
Device integration
Time synchronization, event format, heartbeat status
Device outages are clearly visible
Event fusion
Time windows, zone association, deduplication
Duplicate reports do not repeat actions
Device coordination
Lighting, screens, audio or service interfaces
Outputs can be canceled and acknowledge outcomes
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.
