A prison cannot pause a count, a medication round or a release because a ticket is queued. Support is staffed to that reality, with severity defined by operational consequence — not by software categories.
| Severity | Definition | Response | Channel |
|---|---|---|---|
| SEV-1 | Liberty, life-safety or count at risk Release gate, sentence calculation, formal count, eMAR or duress alerting impaired | 15 min acknowledge · continuous work · named incident commander | 24×7 hotline + pager |
| SEV-2 | Core operations degraded Movements, visits, clinical queue, trust ledger or ICJS exchange impaired | 1 h acknowledge · 8 h workaround target | 24×7 hotline |
| SEV-3 | Function fault with workaround Reports, exports, non-blocking screen defects | Next business day · fix in scheduled release | Portal + email |
| SEV-4 | Question, change or enhancement Configuration guidance, rule-pack drafting, training requests | 3 business days · roadmap review monthly | Portal |
Degraded-mode support is part of SEV-1 handling: the on-call engineer joins the facility's declared degraded-mode bridge, and reconciliation is verified jointly before the incident closes.
Identity · tenancy · policy · audit · integration · edge
Admission · legal · count · movement · incidents
Clinical EHR · eMAR · occupational health · fatigue · staff app
Programmes · reentry · self-service · research
Sequence by risk and operating readiness — not by the most impressive demo. If a gate fails, the phase does not ship.
Wing staff, clinicians, legal officers and residents-by-proxy shape the workflows before build. Double entry and workarounds are treated as defects.
Command, unit officer, clinician, legal officer, accounts, stores and kiosk-support tracks — rostered against relief so training never creates a staffing gap.
Tabletop plus live failover each quarter, including a night scenario with an urgent release. Findings become versioned change-sets with owners.
We baseline before go-live and report adoption, workload and error rates after — including where the system made work harder.
Legal configuration drafted with your counsel: statutory tests, effective dates, scenario suites and rollback points for every change.
Screen, API and KPI registers; integration runbooks; degraded-mode cards for every unit; and an evidence-export guide for court and audit.
platform availability target, measured monthly excluding declared maintenance (For Axxonet Cloud Hosted Instances)
SEV-1 acknowledgement, 24×7, with a named engineer on the bridge
facility edge nodes healthy in the reference deployment — offline continuity always on
unresolved reconciliation conflicts across offline events to date
No call-centre triage. Support conversations run with the engineers and correctional practitioners who designed the workflow you are calling about.