# The Differences Between Alerts, Plate, Vehicle Alarms and DNTT

<p class="callout info">The OPS-COM system provides distinct flagging features—Alerts, Plate and Vehicle Alarms, and Do Not Ticket or Tow (DNTT) statuses—to help administrators and field officers identify specific vehicles during patrols. Understanding the operational differences between these statuses ensures that vehicles are appropriately monitored or properly exempted from enforcement. This article is intended for OPS-COM administrators responsible for managing vehicle profiles and dispatch operations.</p>

## Setup and Configuration

These flagging tools are configured directly on individual vehicle profiles within the administrative portal.

### Configuring DNTT

The **[DNTT](https://opscom.wiki/books/the-opscom-admin-portal/page/dntt-do-not-ticket-or-tow "DNTT - Do Not Ticket or Tow")** feature allows administrators to schedule enforcement exemptions and restrict them to specific physical locations.

1. Navigate to the relevant **Vehicle Profile** in the administration portal.
2. Locate the **DNTT** configuration section.
3. Enter the **Start Date** and **End Date** to define the exact validity period of the exemption.
4. Specify the applicable **Location** if the exemption is site-specific.
5. Click the **Save** button to apply the status.

### Configuring Alerts and Alarms

**[Alerts and Alarms](https://opscom.wiki/books/the-opscom-admin-portal/page/plate-and-vehicle-alarms "Plate and Vehicle Alarms")** are general security and monitoring flags that are not limited by schedule or location.

1. Navigate to the relevant **Vehicle Profile**.
2. Locate the **Alerts/Alarms** configuration section.
3. Enter the necessary details or select the appropriate alarm type from the drop-down menu.
4. Click the **Save** button to activate the flag.

<p class="callout info">Unlike **DNTT** statuses that expire based on a schedule, standard Alerts and Alarms remain active indefinitely until they are manually removed by an administrator.</p>

## Using this Feature

Administrators and enforcement personnel interact wi<span class="citation-665 citation-end-665">th these features primarily through handheld scanning devices or License Plate Recognition (LPR) cameras in the field.<sup class="superscript embedded" data-turn-source-index="1"></sup></span>

### <span class="citation-664 citation-end-664">Visual Cues and Status Indicators<sup class="superscript embedded" data-turn-source-index="2"></sup></span>

- **<span class="citation-663">DNTT Status:</span>**<span class="citation-663"> When a vehicle with an active </span>**<span class="citation-663">DNTT</span>**<span class="citation-663 citation-end-663"> status is scann<sup class="superscript embedded" data-turn-source-index="3"></sup></span>ed, a red exclamation mark icon appears on the handheld device screen. No audible alarm will sound, allowing the officer to silently bypass the vehicle.
- **Alerts and Alarms:** When a vehicle with an active Alert or Alarm is scanned by a handheld device or detected by an LPR camera, the system triggers an immediate visual notification and an audible alert to draw the officer's attention.

### Available Actions

- **Dispatch Logs:** Once an Alert or Alarm is triggered in the field, it can be converted into a Dispatch Log. This allows the security team to actively track, investigate, and document the resolution of the alert.

---

## <span style="color: rgb(22, 145, 121);">Best Practices and Considerations</span>

### <span style="color: rgb(22, 145, 121);"></span>

- <span style="color: rgb(22, 145, 121);">**Define Clear Business Rules:** **Organizations should establish clear policies regarding who has the authority to apply a DNTT status** and the specific circumstances under which it is granted (e.g., medical exemptions, maintenance vehicles, VIP guests).</span>
- <span style="color: rgb(22, 145, 121);">**Maintain Accurate Records:** **Regularly review active Alerts and Alarms** to ensure that outdated or resolved flags are removed. This prevents notification fatigue and unnecessary alerts dur<span class="citation-662 citation-end-662">ing standard enforcement activities.<sup class="superscript embedded" data-turn-source-index="4"></sup></span></span>
- <span style="color: rgb(22, 145, 121);">**<span class="citation-661">Utilize Dispatch Logs:</span>** **<span class="citation-661">Always convert triggered Alerts into Dispatch Logs</span>**</span><span class="citation-661 citation-end-661"><span style="color: rgb(22, 145, 121);"> to maintain a comprehensive and permanent audit trail of how security personnel responded to the field notification.</span><sup class="superscript embedded" data-turn-source-index="5"></sup></span>