Command Center
The operational picture across an organisation's sites: what its six tabs show, what each command does, and what depends on other modules or configuration.
- Version
- 0.2
- Dernière mise à jour
- Disponibilité
- Partiellement disponible
Parcourir la documentation
Sur cette page
Ce document n'est actuellement publié qu'en anglais. Lire la version anglaise de référence
Command Center is the first item in Virtik's sidebar and the screen the Virtik logo returns you to. It puts an organisation's sites, people, incidents and cameras on one operational picture, and it is where an operator selects something, understands it and acts on it from the same place.
It reads from the same site model as the rest of the platform: a site is created once, and Command Center lists it, maps it and counts what is attached to it. See What is Virtik? for the platform model.
The six tabs
| Tab | What it shows |
|---|---|
| Overview | Four headline counts, an Operational Queue of items that need attention, and recent activity. |
| Sites | A Site List with state, camera and on-duty counts, beside a map. On a narrow window the tab shows the map only. |
| Incidents | Every incident in scope, with filters, a detail view and its lifecycle buttons. |
| Resources | Personnel, Assets and Cameras, with the commands to add resources and form teams. Cameras summarises, per site, how many are online and the percentage online. |
| Intelligence | A situation brief and attention recommendations computed from the data already on screen. |
| Activity | A single timeline of incident, dispatch, camera, duty, patrol, communications and audit events. |
Each tab has its own commands in a second row, and one search bar in a third. A context panel on the right shows whatever is selected.
Overview
The Overview opens with four counts: Sites operational, Cameras online, Responders available and Active incidents.
Below them, the Operational Queue lists what currently needs an operator, up to 50 items. An item in the queue is one of seven kinds: an incident, a detection, a camera-health problem, a person who needs assistance, an incident with no response, a missed patrol, or a patrol exception. When there is nothing to act on, the queue says so ("Nothing needs attention in this scope"); it does not show placeholder items.
Sites
The Site List can be filtered by state (Operational, Degraded, Offline or Unknown) and sorted by name, cameras or personnel on duty. A site with no location set is listed as "Location not configured" and does not appear on the map. If an organisation has no sites at all, the map says so.
Incidents
The Incidents tab filters by site, status, severity, source, assignment and time window. By default it shows active statuses only.
An incident moves through a fixed set of statuses: Open, Acknowledged, Active, Resolved and Closed. The buttons in the incident detail (Acknowledge, Escalate, Resolve, Close) change that status. The rules about which change is allowed are enforced in the database, not only on screen, and Closed is final: a closed incident cannot be reopened. A confirmation appears only after the change has been saved.
The detail view also holds the incident's assignments, the operational resources committed to it, a timeline, and a list of eligible responders from which an operator can dispatch.
Resources
Resources has three views. Personnel lists members with their team, site, role and duty state. Assets lists non-human resources with their type, capabilities and status. Cameras summarises, per site, cameras online and coverage.
From here an authorised operator can add or remove a resource, Request Status from personnel, Create Team, and start a group conversation (Group Comms). Each of those writes to the organisation's records. A status request that cannot be delivered is reported as not delivered rather than as sent.
Intelligence
The Intelligence tab presents a Situation brief, Recommended operator attention and a Cross-site comparison, and an Ask Virtik AI panel whose Open ChatVRTK button takes you to ChatVRTK. These are produced by fixed rules applied to the figures already loaded on screen. They are not the output of an AI model, and the tab states plainly where it has not assessed something: incident trends are listed as "Not assessed".
Activity
Activity merges events from incidents, dispatch, camera and detection events, duty, status requests, patrols, communications, resources and audit into one list, filterable by source, site, severity and time window. It shows Live unless you pause the stream, and then Paused; paused updates are counted, not lost.
What the commands do
| Command | What it does |
|---|---|
| New Incident | Opens Live Operations, where Activate Incident is under Operations, in Incidents. Nothing is created until that form is submitted. |
| Dispatch | Opens the dispatch console in Response. Inside an incident's detail, each eligible responder has a Dispatch button, and that creates the assignment. |
| Request Status | Asks selected personnel to report their status, and reports clearly if the request could not be delivered. |
| Create Team | Creates a team and its members in the organisation's records. |
| Group Comms | Starts a group conversation with the selected people. |
| Open Virtual Site / Detection / Response | Open Detection opens with the selected site. Open Virtual Site does the same, but is enabled only when the selected site has a spatial model. Open Response opens its Resources view without a site filter. |
| Export | Saves a PDF image of the current screen. It is a screenshot of what you see, not a data export. If it fails, nothing is shown. |
Who can do what
Everyone in the organisation can open Command Center, but they see only the sites they have been given access to. Changing an incident's status, Request Status, Create Team and adding or removing a resource need an administrator or editor role; without one the control is disabled and says why. Editors also need access to the incident's site. Dispatch and Group Comms are not disabled in the interface: the server applies the rules.
Showing individual responder locations and dispatching depend on the organisation's mobile-operations entitlements. Where an organisation is not entitled to individual locations, the responder panel states that rather than showing an empty list.
Live updates
Command Center subscribes to changes in incidents, camera events, patrols, patrol exceptions, presence sessions, safety status and dispatch assignments for the organisation, and refreshes the queue, the headline counts and the incident list when they change. Site, resource and team lists are loaded when Command Center opens and when you press Refresh.
What it depends on
- A map token. The map needs a map-provider token. See Mapping.
- Routes. Responder routes on the map use the map provider's directions service. If routing fails, the panel says "Road route unavailable" or "Routing error".
- Communications. Request Status and Group Comms use the communications backend.
- Cameras and detections. Camera and detection items appear only for cameras that have been added to a site. See Detection and Cameras and data sources.