OPERATIONS LAYER
Security Expert Plus is Knight Watch's independent operations platform, built to run on top of Schneider Electric EcoStruxure Security Expert. It enforces Security Expert's own permission model rather than replacing it: the vendor's configuration becomes the session's claims, and every live control command still goes back through Security Expert's own SOAP service — under the signed-in operator's session, not a shared service account.
OPERATOR CONSOLE
The operator console is the one screen a guard works from — a module inside Security Expert Plus. Individual engagements deploy it under customer-chosen names; those names are not used in Knight Watch marketing. Its tabs follow the operator's access claims, enforced server-side rather than in the browser, and the same claim check runs on every endpoint behind them.
Search the Security Expert cardholder records the operator is actually scoped to see, with the cardholder photo served from its own database rather than copied into the console's.
Every door release that bypasses an access-level or state rule requires an explicit human acknowledgement with a written reason, and that reason is recorded against the access-control event in a dedicated release-audit table.
Door chips on the console update live: a lock, unlock, or latch shows immediately whether it came from an operator command, the vendor's own client, a card or keypad swipe, or a scheduled action.
PERMISSION MODEL
ALARM PIPELINE
RELEASE AUDIT
Every door-release decision — granted or refused — writes a row to the release audit table. Below is the schema of that record, field by field. It is deliberately not a sample of traffic: there is no illustrative data anywhere on this deck.
| Door | Which door the decision was made against | Scoped by the operator's record groups |
|---|---|---|
| Cardholder ID | The numeric identifier of the person | This record does not store a card or badge number |
| Operator | Who made the decision | The same identity the SOAP command is issued under |
| Timestamp (UTC) | When the decision was made | Written on a grant and on a refusal alike |
| Outcome | Granted or refused | A refusal is a row, not a silence |
| Failure reason | Why a refused release was blocked | Badge state hold · no access rights · missing override acknowledgement · operator self-release · controller rejection |
| Override applied + reason | Whether a rule was bypassed, and the written justification | An override cannot be applied without an explicit human acknowledgement |
| Event code | The organization's own event codes | The record reads in the customer's vocabulary, not ours |
STATUS & DELIVERY
Written and code-complete. The operator console carries automated test coverage; every other item here carries its own status, and several ship from a customer engagement's build rather than the platform mainline.
Tested outside a laboratory, with the date and the environment attached to each result.
Finished work that has not reached a released build, or that lives on a customer engagement's branch rather than the platform mainline.
Named here rather than left for a prospect to find. Badge Requests is hidden from the sidebar for the current engagement milestone — the route stays registered so direct URLs still work — and one of its seventeen scoped items is done.
HOW YOU RUN IT
Knight Watch publishes a release; your own IT deploys it. There is no standing access into your estate, no data migration, and the console you have today stays available as a fallback the whole way through.
Releases are the only deployment artifact. Knight Watch publishes a versioned, checksummed release package; your own IT deploys it to hosts you control.
Designed to run alongside an existing web client through cutover rather than replace it in one move, dual-writing the legacy audit tables in a single transaction so both consoles agree.
Every deployment leaves the previous version on disk, so going back is a documented procedure rather than a restore from backup.
Business-hours support is standard, with an optional Premium tier adding 24x7 response for critical (P1/P2) incidents.