Netsocs Dispatch · in design
From the control center to the field. One coordinated response.
The decision made in the control center reaches the person on site, and the evidence returns to the operation. Not a GPS app, not a chat.
Design stage: what you see is the concept and simulated prototypes. It is not released software.
One incident, six moments
From assignment to a closed record.
Concept wireframes. The final screens are still in design.
What it is designed to do
Eleven capabilities, and where each one stands.
- Assign incidents to field personnelIn first-release design
- Customer, site and event informationIn first-release design
- Location and routesIn first-release design
- Navigation to the destinationHands off to the map app.In first-release design
- Communication with the control centerPhone call first; chat and IP calls come in a later phase.In first-release design
- Live video, when authorizedDepends on the video integration being validated.Later-phase concept
- Photos and evidenceIn first-release design
- Audio and voice notesLater-phase concept
- Dispatch status updatesIn first-release design
- Log of the interventionIn first-release design
- Closure and return to the control centerIn first-release design
With CARA
Decision, execution, evidence.
Dispatch is meant to extend what CARA coordinates to the people in the field, and to send results back to the situation.
- CARAA situation and a guided procedure
- Dispatch actionThe procedure assigns a responder
- Field responderBriefed, on site, documenting
- Status and evidenceReturn to the operation
- CARA timelineThe record is complete
Intended flow, part of the design. The connection between CARA and Dispatch has not been verified in a running product. Dispatching from CARA is an action of its procedure; Netsocs Dispatch is the separate field application. About CARA
How does your field team respond today?
Tell us the incident, the people on site and the systems involved. We will show where Dispatch fits.