feat(operator-view): focus on doors and alarms #188

Open
opened 2026-09-30 15:25:37 +00:00 by gabogg · 0 comments
Owner

Part of #187 — milestone: Focused operator and supervisor door operations.

Intended outcome

Give an Operator a focused live workspace for doors and alarms. The current shared content-doors deck in app/static/index.html also contains occupancy telemetry, while its HUD mixes door alarms with occupancy and cycle figures. This issue decides the Operator presentation boundary before UI changes are specified.

Agreed scope

Keep live door states, the open-longest ranking, door activity, alarms, and permitted one-shot door controls in the Operator view. Move occupancy, configuration, and diagnostics out of that view. Preserve #72's command policy and enforce permissions on the server.
For an existing door with a current manual status (#191), show both that operational assessment and the raw HikCentral reading with their sources. Keep hardware alarms visible.

Triage questions

  1. Which other door details should be visible: access person details, sensor classification, and offline status? How should an overdue manual assessment appear?
  2. What counts as an alarm here: HikCentral forced-open/timeout signals only, or also locally inferred conditions? Is an alarm list, count, filter, or acknowledgement needed in this milestone?
  3. Where should the removed occupancy, configuration, and diagnostics content live for other authorized roles? Should video or facility-cycle indicators appear anywhere in the Operator view?
  4. How should a door or alarm be selected and handed off to the Supervisor workflow? What must work on narrow displays and in EN/ES?

Ready-to-spec outcome

A screen/content inventory for the Operator role, alarm terminology and actions, navigation rules, and explicit tests for role visibility without changing backend authorization by hiding controls.

Related: #72 already specifies door-command permissions and audit; this issue must preserve that policy unless separately retriaged.

Part of #187 — milestone: Focused operator and supervisor door operations. ## Intended outcome Give an Operator a focused live workspace for doors and alarms. The current shared `content-doors` deck in `app/static/index.html` also contains occupancy telemetry, while its HUD mixes door alarms with occupancy and cycle figures. This issue decides the Operator presentation boundary before UI changes are specified. ## Agreed scope Keep live door states, the open-longest ranking, door activity, alarms, and permitted one-shot door controls in the Operator view. Move occupancy, configuration, and diagnostics out of that view. Preserve #72's command policy and enforce permissions on the server. For an existing door with a current manual status (#191), show both that operational assessment and the raw HikCentral reading with their sources. Keep hardware alarms visible. ## Triage questions 1. Which other door details should be visible: access person details, sensor classification, and offline status? How should an overdue manual assessment appear? 2. What counts as an alarm here: HikCentral forced-open/timeout signals only, or also locally inferred conditions? Is an alarm list, count, filter, or acknowledgement needed in this milestone? 3. Where should the removed occupancy, configuration, and diagnostics content live for other authorized roles? Should video or facility-cycle indicators appear anywhere in the Operator view? 4. How should a door or alarm be selected and handed off to the Supervisor workflow? What must work on narrow displays and in EN/ES? ## Ready-to-spec outcome A screen/content inventory for the Operator role, alarm terminology and actions, navigation rules, and explicit tests for role visibility without changing backend authorization by hiding controls. Related: #72 already specifies door-command permissions and audit; this issue must preserve that policy unless separately retriaged.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gabogg/hikcentral#188
No description provided.