Response
How an incident is created, assigned, dispatched and closed in Virtik, what the incident scene shows, and what was and was not verified.
- Versione
- 0.2
- Ultimo aggiornamento
- Disponibilità
- Parzialmente disponibile
Sfoglia la documentazione
In questa pagina
Questo documento è attualmente pubblicato solo in inglese. Leggi la versione inglese di riferimento
Response is where an incident is worked. It holds the list of incidents, each incident's summary, map, responders, tasks, reports, communications, evidence and timeline, and the dispatch console that tracks each responder from assignment to release. It reads the same site model as the rest of Virtik, so an incident is tied to a site and, where it can be resolved, to the zone, cameras and responders around it.
The six tabs
| Tab | What it holds |
|---|---|
| Overview | Four counts (Active incidents, Resources deployed, Awaiting acknowledgement, Critical or high) and the incidents that need attention. |
| Incidents | The incident list with filters, and the incident workspace. |
| Dispatch | The dispatch console for the selected incident: who is assigned and where each responder is in the sequence. |
| Resources | All resources, Personnel or Assets. |
| Plans | Response plans, shown as All plans, Published, Drafts or Archived. |
| Activity | An event journal and a queue of field reports. |
The toolbar commands depend on the tab. New Incident is on Overview and Incidents; Export is on Incidents, Dispatch and Activity; Resources has only Refresh; New Response Plan switches to the Plans tab. Export is disabled until an incident is selected, and produces a JSON file of that incident.
Creating an incident
New Incident opens a form with: Title, Incident type, Severity, Site, Occurred at, Location, Description, Initial commander and External reference. The incident types are fire, medical, intrusion, theft, vandalism, assault, suspicious activity, access violation, equipment failure, hazmat, weather and other. Location is required. Severity is one of critical, high, medium, low or informational.
If you choose an initial commander, that is saved as a second step after the incident. If it fails, the screen says "Incident created, but the commander could not be assigned" rather than reporting complete success. The incident already exists at that point and the form stays open, so pressing Create again would create a second incident; assign the commander from the incident instead.
An incident can also begin elsewhere: Live Operations activates incidents, and Detection can escalate an event into one. An incident that came from a detection shows its source, with a link back to the originating camera when it can be resolved for your account.
Statuses
An incident is Open, Acknowledged, Active, Resolved or Closed. Buttons in the incident move it along ("Move to Acknowledged", and so on). Which moves are allowed is enforced in the database, every change is recorded in the incident's history, and Closed is final: the incident then shows "Closed — no further transition available".
The incident workspace
An incident opens with eight sections: Summary, Map, Responders, Tasks, Reports, Comms, Evidence and Timeline.
Incident scene
The Summary includes an Incident Scene card with rows for Location, Cameras in zone, Operational assets, Access control, Procedures and Responders assigned. Each row carries a badge: Available, Not configured, Unavailable, Stale, UNAUTHORIZED or Unknown. The card does not guess. In this release the Access control and Procedures rows are always Not configured, and the product says so in its own words: "No access-control integration is configured for this organization" and "No procedure/SOP model exists in this system yet". The cameras row is filled only when the incident's location resolves to a zone.
Dispatch
A responder moves through Assigned, Dispatched, Acknowledged, En route, On scene and Released, with a button for each next step and a confirmation before release. These are records that people update. To reach a responder, use Communication or an alert in Live Operations.
On the incident Map, Find Nearest Responder proposes the best eligible on-duty responder as the "Best real candidate"; you then confirm with Assign. It needs the incident to have coordinates and the account to have access to presence data. If none is eligible it says "No eligible on-duty responder found near this incident."
Communications
The Comms section can send a Broadcast through Virtik's in-app communications. It goes to everyone at the incident's site, or to the whole organisation, not to people you choose; it needs a write role, and the Require acknowledgement option is ticked by default.
After-action review
After-action reviews have their own screen, titled After Action Review, which is reached by a direct address for the incident; Response has no link to it. A review is a draft, in review, completed or reopened. It holds findings, graded as observation, minor, major or critical, and improvement actions, each open, in progress, resolved or cancelled.
Who can do what
Everyone in the organisation can open Response. Creating an incident, changing a status, assigning and dispatching need an administrator or editor role, and a disabled control says "Requires an administrator or editor role" (for a status change, "Changing incident status requires…"). Mutual aid is for administrators only.