Reference, Time & Hub
Rows near the top of the Event panel answer the questions that come up the moment somebody else is on the line: which event are we talking about, when exactly did it come in, and what is installed there.
Event Reference
Every event carries a short Reference — six characters, like 08G16E. It is
the handle you quote to a client, a responder, or SAPS so that both sides are
certainly talking about the same incident.
Click the reference to copy it. The tooltip also spaces it out (08G 16E) for
reading aloud.
The alphabet deliberately leaves out I, L, O and U, because those are the characters that get misheard as 1, 1, 0 and V. If someone reads a reference back to you with an "O" or an "I" in it, typing it as they said it still finds the right event — those substitutions are understood.
Finding an event from its reference
A reference works straight in the address bar. If a client quotes 08G16E, go to:
/events/08G16E
and CleverCommand opens that event. The numeric form (/events/8914126) keeps
working exactly as before.
They sit on the same screen and it is worth keeping them apart:
- The Event Reference is ours. CleverCommand generates it for every event, automatically, and it never changes.
- The OB number is theirs. It is the police station's Occurrence Book
number (
OB 123/07/2026), and an operator types it into the burglary case once SAPS provides it — see Confirming a burglary.
On a call to SAPS you will often quote both: your reference, and their OB.
How long a reference stays valid
The reference is derived from the event itself rather than stored separately, so it stays valid for as long as the event does. Full event detail is kept for 35 days; after that, the archive still resolves the site, time, signal and description for roughly 19 months.
Time received
Time received shows the date and the second the signal landed, not just the minute:
3 Sept, 05:50:51
Hovering gives the full stamp with the weekday and the year. The Signal restored row, when an event has one, reads the same way.
Rounding to the minute hides the thing operators most often need from it — two signals from the same panel four seconds apart is a panel behaving badly or an intruder moving; four minutes apart is something else entirely.
Hub
For events that came from an alarm panel, one row names the hub — its type and the code it reports under:
HUB Olarm - 2246
The type is the communicator installed at the client's site (Olarm, FSK, RDC, FOX, HYYP, Ajax, FinMon, AVLytics), and the number after it is the account code — the TX number on serial radios, where it is the same number as the radio's own serial.
This answers "what is on the wall there, and what does it come in as?" without leaving CleverCommand for CleverOps.
Sites with more than one hub
Plenty of sites have two ways in — an Olarm alongside an RDC, say. The row then reads Hubs and gives one line each, with the hub that sent this signal first and in bold:
HUBS RDC - 3108 Olarm - 8456
The others stay muted: they are on the site, but they are not what fired.
Hubs that have no account code
A hub that never reports an account code still gets a line — its own identity stands in, such as an Olarm serial or a panel IMEI. Hover the line to see which kind of identifier you are looking at, so a device ID is never mistaken for a four-digit account code.
Older events
Past the 35-day detail window, which hub sent the signal is no longer recorded. Those events list the site's hubs without bolding any of them, and say so underneath: "site's hubs today — which one sent this is not recorded".
When the row does not appear
It only appears for alarm-panel events. Camera detections, mobile panics and app events have no hub to name.