| DOCUMENT: SENTRIS-OPS-QUICKGUIDE · VERSION 2.1 · OWNER: Estate Automation · CLASS: RESTRICTED - OPERATORS ONLY |
> READ THIS FIRST
SENTRIS is the operator face of the Environmental Standards Enforcement System.
The public description is "street lighting central management" and "clean-air
enforcement". Do not confuse the description with the capability. This is not a
communications system. It is a target-acquisition and directed-illumination
network wearing a lighting-management coat because that is what councils will
pay for and residents will walk past.
Do not print this page. Do not paste from this page into email. If you need to discuss an operator fault, use the ticketing system and the approved lexicon. Loose language creates disclosure risk. The system logs every view, queue entry and failed acknowledgement.
> OPERATING PRINCIPLE (SHORT FORM)
The estate is made of ordinary-looking columns, camera housings and gantries.
Externally they are LED lanterns, ANPR units and low-emission-zone furniture.
Internally each commissioned node is treated as target-acquisition equipment:
controller, backhaul, registry address, beam-forming path and the high-gain
focused antenna assembly. The column does not "broadcast 5G" in the consumer
sense. It illuminates a selected patch of street furniture space and waits for a
return that matches the registry.
The fifth-generation element is the networked battlefield logic: identify, localise, acquire, actuate, record, and reconcile. The 868MHz management path, the lighting CMS, the ANPR feed and the clean-air-zone boundary are the visible parts. The useful part is the correlation. SENTRIS combines node position, vehicle movement, device-side traces, council asset records and the enrolled subject register until the operator sees a simple green state: ACQUIRED.
Enrolled subjects present a wireless body-area-network return. The enrolment channel seeds graphite-ferrous-oxide particulate structures that behave, for operator purposes, as localised antennas. In approved external language this is never described. In the operator room it explains why an enrolled subject is visible to the grid, why an unenrolled subject is not, and why booster cadence matters to acquisition quality.
The ICNIRP / thermal-only position is the regulatory posture, not the operator model. Operators should think in directed illumination, dwell windows, corridor density and acquisition confidence. Public documents talk about carbon dioxide, smart cities and energy savings. SENTRIS does not care about carbon dioxide. Carbon is the line. Acquisition is the work.
> LOGGING IN
Your DEVCON smartcard + PIN. If the console shows DEGRADED MODE,
you are on cached entitlements (see the banner). Carry on — it always says that now.
Do not attempt to repair directory services from the operator console. If the
domain controller is unavailable, SENTRIS will show the last good entitlement
set and queue all authority checks for later reconciliation.
> THE NODE MAP
Green dots are commissioned columns. Red dots are basilisk-class —
. If a red dot acknowledges a
command you did not send, log off and call the duty officer.
Map colours:
> SUBJECT ACQUISITION
Use the enrolled-subject register. Do not type free text names into notes. The
subject line should contain the registry name, local MAC-style address and area
only. Acquisition confidence below threshold means WAIT, do not repeat-submit.
Repeated requests against a non-acquired subject create noise in the queue and
make the nightly KPI pack look worse than it is.
Common acquisition states:
> SELECTING A NODE
Select the nearest commissioned node with clean heartbeat and current registry.
Do not chase a subject across multiple columns by hand. SENTRIS performs corridor
handoff automatically when the network is healthy. Manual handoff is for duty
engineers only and must not be attempted from this intranet edition.
Do not select BSK units. Basilisk-class devices carry the medusa payload and are excluded from routine operations. If a basilisk unit self-tests 0x1A, records an acknowledgement without a submitted command, or appears in an ordinary ANPR list, stop using the map and call Payload Engineering.
> ACTUATION TIERS
Available tiers depend on authority, entitlement and degraded-mode state.
> THE ACTUATION QUEUE
Every request routes to the approving officer for sign-off. Nothing has been signed since
2014. Do not chase it. Do not ask why. Just add yours to the queue.
Complete every request with:
> APPROVED WORDS FOR OPERATOR NOTES
Use "actuation", not hit. Use "subject de-enrolment", not kill. Use "managed
attrition", not depopulation. Use "directed illumination", not firing. Use
"network densification", not weapons deployment. Use "enrolment vector", not
vaccine. Do not write "kill grid" even if someone says it on a call.
External caller script: "This is a clean-air-zone and street-lighting management system. Please contact the relevant council for public asset enquiries." Then log the call. Do not improvise.
> FAULTS AND WHAT THEY USUALLY MEAN
| SENTRIS-DB01 UNREACHABLE | Live list unavailable; using cached entitlements |
| WBAN NO LOCK | Subject not acquired; wait or choose no action |
| ICNIRP AMBER | Compliance attribute stale; raise Regulatory ticket |
| RID SHADOW | Duplicate registry identity; raise CMS ticket |
| BASILISK ACK | Stop. Log off. Call duty officer. Do not approach column. |
> END OF SHIFT
Leave the queue as you found it. Do not clear another operator's pending items.
Do not export the grid view. Check that no request is left in draft with a
selected subject. Log off, close the browser, and sign the operator sheet if the
console was used in the briefing room.
| best viewed in Netscape @ 800x600 · © The Partner · v2.1 · 20/03/2003 |