design

Product Manager · KaaG operations

Job to be done

Give the KaaG Product Manager an operational P0 workspace to monitor the full fleet, understand adoption and energy, investigate individual sessions, respond to safety exceptions, and control inverters without exposing raw engineering telemetry.

Information architecture

• Operations overview: 6-up RADR KPI cards, last-seen honesty bucket strip (Reporting now / Quiet / Silent / Offline / Dark, summing to the fleet), live fleet state, active safety exceptions, adoption, energy, and inspection summary.
• Fleet & control: JS-rendered dense roster (9 columns, no horizontal scroll at 1440) with age chips, 7-day uptime sparkbars, SOC bars, colored SOH, carrier + RSSI cells, MCU · VCU · BMS · DU system chips (DU = display-link health), mono FW column, and audited KAAG_ON / KAAG_OFF row actions. Kill-switch state (radr.commands.enabled) surfaced as an honest inline note.
• Sessions & energy: session-level energy, depletion, end reasons, data-quality status, unit last-seen age chips, and usage frequency.
• Inspection pipeline: read-only eligibility and inverter-assignment visibility. Product cannot modify rider profiles or inspection records.
• Alert centre: operational exceptions (including data-quality honesty items such as the unpublished fault register, RUNBOOK §4.4) plus the shared Product and Engineering remote-command audit trail with SENT / QUEUED results.
• Device detail: RADR identity card (mono serial, custody, cluster, SIM · APN onomondo with “IMEI/ICCID not captured · backlog”, KaaG kit / Telpo VCU badges), status KPI strip, live decoded-signal table with real payload keys (soc, batv, mwc, mpd, spd, tp1, tmp, tlg) ticking every 2 s with sparklines, 24 h connectivity timeline, Display & indicators section (MCU vehicle-lights frame 0x18F86590 chips, SOC-push-to-display health, odometer trio), and scoped commands. A boundary card marks raw frames as an Engineering surface.

Access boundary

Product Manager may filter, search, export, view rider and device history, flag a unit for Engineering, and send KAAG_ON / KAAG_OFF (INVON / INVOFF) or AUTO (return to night schedule). Every remote command requires a reason and records actor, timestamp, command, and result (SENT once acked, QUEUED while offline). Raw MQTT payloads, firmware actions, commissioning edits, inspection edits, and rider-profile edits are excluded. There is no networked display unit and no DU commands; DU surfaces are decoded indicator states and display-link health.

Canon

Web 1440 Atlas shell over the RADR visual foundation (kaag-radr-foundation.css). Uses 82 px .kpi-card KPI rows with circular tonal icons and delta lines, .pseg filters, .tbl-card > .tscroll > .tbl tables (48 px grey header, dense rows), .age last-seen chips (never bare Online/Offline where an age is known), canonical badges, outline icons, centered .dlg confirmations with required audit reason, and top-center toasts. Cards have no visible borders. Telemetry timestamps are UTC; human-facing times are WAT.