Question COM 08

COM-08 How will people and maintainers see whether a kiosk, connection, sensor, notice or request is current, working, waiting or uncertain?

Start here · Questions · Progress · People decide

Why this matters

Visible status helps people act on information and helps maintainers find the next repair.

What to bring back

Design a public status display and a maintenance view. Show last contact, age of waiting messages and source information, uncertain time and battery state. Set local alerts and response steps, and keep private information out of unnecessary logs.

What we know so far

• Straddie Disaster Kiosk Pitch.pdf — reviewed source; public copy can be added through the evidence process
• Professional review and comparison of proposed improvements (When this work overlaps professional or public-authority responsibilities, compare the proposal and Luke's research with applicable industry/global best practice and relevant legal-engine sources. Record differences, reasonable improvements and deficiencies, with the responsible reviewer and response. Routine authorised drafting and wiki work can advance.)
• Council plan crosswalk and proposed Aura integration (Relevant question row identifies the management/recovery source section and printed/PDF page. AI-generated analysis, 21 October 2026; proposed checks and actual review/operating agreements retain separate status.)

AI-generated potential answers

For discussion and review · research checked 2026-10-20. These are AI-generated options and transfer assessments. The user's request and research method identify the source of this work. The source catalogue states what the references establish. The decision and approval record retains its own status.

Show people what the station can do now, when its information last changed and which messages are waiting. Give maintainers a separate detail view of links, queue age, battery and faults. When time is uncertain, preserve the last trusted check and explain uncertainty plainly.

Public status and maintenance view

AI-generated adaptation of an existing pattern. Join measured energy status with device health and message receipts, publishing only useful non-private summaries. Compare a retained e-paper status face with a richer interactive display; both would carry update time and current capability.

Research basis: Cerbo GX manual: configuration · NIST's IoT Cybersecurity Capabilities Catalog · E Ink technology benefits.

Explainable network twin

AI-generated future concept. Develop an Aura view that explains dependencies in everyday words: local notices available, mainland connection waiting, next check due. XR could help maintainers trace a fault while public users receive the same essential status in text or audio.

Examples and local differences

• NIST's IoT Cybersecurity Capabilities Catalog: AI transfer assessment: NIST includes cybersecurity-state awareness among device capabilities. Local difference to check: A useful public view also needs service, content freshness and privacy rules beyond security status.

Evidence to bring back next

• Test whether users distinguish an old visible notice from a live service.
• Inject clock loss, stale telemetry and a one-way link into the maintenance demonstration.

People and connected choices

Who reviews: Proposed network operations lead with publisher and privacy reviewer; role and appointment awaiting confirmation

Connected questions: DAT-01, ENE-05, COM-04, COM-05, COM-06

Work state: open. Assigned person or AI assistant: Ready to be assigned.

Research and alternatives can move ahead while connected decisions develop. Before acting on a choice, check the people, evidence and approved scope in People decide.