# Dispatch System

<figure><img src="/files/MirtlyAfb8B7RILrwnqa" alt=""><figcaption></figcaption></figure>

#### Open Command ;

```lua
/openDispatchTablet
```

#### Unit Editor Command ;

```lua
/uniteditor
```

#### 📖 Dispatch System — General Logic

This is a **police dispatch system** designed to coordinate officers, track incidents, and manage responses in real-time. It provides an advanced map interface, officer status tracking, and event assignment tools, all in one centralized UI.

***

### 🔹 Main Features

* **Live Map Interface**
  * Shows active incidents, officer locations, vehicles, and foot patrols.
  * Heatmap and markers indicate areas of activity (shots fired, robberies, etc.).
  * Dispatchers can zoom, drag, and highlight specific areas.
* **Incident Management**
  * Events are created when crimes or calls are reported.
  * Each incident displays type (e.g., shooting, robbery, accident), time, location, and assigned officers.
  * Notes section allows dispatchers and officers to share quick details.
* **Officer Tracking**
  * Officer list with badge numbers, duty status (On Duty/Off Duty), and current activity.
  * Units are grouped (Unit A, Unit B, etc.) to show teamwork.
  * Officers can be marked as **In Pursuit, In Vehicle, On Foot, or Offline**.
* **Unit Assignment**
  * Dispatchers can assign officers directly to events.
  * Officers can be grouped into units for coordinated response.
  * Each unit’s activity is shown (e.g., chasing suspect, responding to call).
* **Communication & Chat**
  * Integrated chat system for general, unit-specific, command, and private messages.
  * Messages are color-coded by role (General, Officer, High Command).
* **Permission & Visibility**
  * Dispatchers can control who sees global drawings, notes, and shared data.
  * “Give Permission” button shares specific tools with other officers.

***

### 🔹 Workflow Example

1. **Event Triggered**: A shooting occurs at Hasselhoff Street (10-52).
2. **Dispatcher View**: The event shows up in the “Active Events” list with details.
3. **Assign Officers**: Dispatcher selects available units (e.g., J.Smith, F.Urkan) and assigns them.
4. **Officer Tracking**: Their status updates automatically (in vehicle, in pursuit, etc.).
5. **Ongoing Updates**: Officers send notes, and their position updates on the map.
6. **Resolution**: Event is marked complete, and units are freed for new calls.

***

### 🔹 Advantages

* Centralized management of **all police activity**.
* **Real-time map tracking** improves coordination and response times.
* Officers and dispatchers can **communicate seamlessly** through the integrated chat.
* Heatmaps and incident filters make it easy to spot high-crime areas.
* Encourages **team-based roleplay** by grouping officers into units.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.0resmon.org/0resmon/frkn-resources/frkn-police-job/dispatch-system.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.