Computer-aided dispatch · Law · Fire · EMS

Powering next generation of public safety.

Your entire dispatch operation on one platform — call intake, dispatching, mapping, mobile and alerting, from the ring to the clear.

Cloud or on-premises Your data, your rules Built for CJIS
2026-001048 Working fire
Location
1830 Harbor Blvd, Bayshore
Nature
Structure fire — commercial
Area
BAYSHORE 12 / CO-3
Plan
Box alarm — 2 engines, 1 ladder, 1 medic
03:14:02Call receivedCALLTAKER
03:14:38Units dispatchedE31 L12 M4
03:15:11EnrouteE31
03:18:47On sceneE31
03:52:20Cleared · disposition setE31
The platform

One system for the room, the road and the map.

Every part of Priority One ships together and shares one data model — so the console, the vehicle and the map never disagree about where a call is or who is on it.

Dispatch

CAD console

Call intake and dispatching laid out the way your centre actually works.

  • Address-first intake from your own GIS
  • Call editor layouts per position
  • Capability-based response plans
  • Recommendations ranked by travel time
Intake and dispatch
The field

Mobile (MDT)

The same system in the vehicle as on the wall — status, calls, notes and position.

  • Crews change their own status
  • Self-initiated activity from the unit
  • Premise cautions on the call
  • An emergency button only dispatch can clear
Mobile
Mapping

Your own map

Streets, addresses, response areas and pre-sites from your GIS — not a generic basemap.

  • Response areas and county overlays
  • Address points, block ranges, pre-sites
  • Live unit positions (AVL)
  • Hydrants on the map, from your data
GIS and mapping
Alerting

Alerting & interop

Tones out with the dispatch, and the call reaches the systems your people already carry.

  • Station alerting and paging
  • E911 ANI/ALI into the call
  • Active911 alerts from the CAD
  • CAD-to-CAD with neighbouring agencies
Integrations
Who we serve

One CAD, configured for three very different jobs.

Law, fire and EMS dispatch the same call in different ways. Statuses, natures, dispositions, geography and plans are set per agency — on one shared incident.

Ring to clear

Every part of P1 belongs to a phase of the call.

Nothing is an add-on that has to be introduced to the rest of the system.

01 · Intake03:14:02

The address resolves as it is typed

Cross streets, common names and block ranges, with the call editor laid out for the position.

02 · Dispatch03:14:38

Location and nature pick the response

Response areas come from your boundaries; the plan asks for capabilities, not unit numbers.

03 · The field03:15:11

The vehicle and the wall agree

Crews change their own status; the room sees it immediately, and so does everyone on the call.

04 · Clear03:52:20

Each agency closes its own part

Per-agency dispositions on one shared incident, and every change kept as history.

Built for CJIS

Security that names a person, not a workstation.

Dispatch runs on shared consoles. The record still has to say who did what — so every account, every permission and every change belongs to one person.

AccountsOne account per person — never a shared console login.
PasswordsLength, complexity, history and expiry enforced by policy.
PermissionsRole-based, per agency: each person sees what their job needs.
AuditWho dispatched, who changed a status, who wrote the note.
Why agencies move

Legacy CAD is holding your agency back.

Not because it lacks features. Because of what it costs you to use them.

01

Vendors that don't talk

CAD, mobile, mapping and alerting from four companies — and the seams break at 3 a.m.

02

Per-seat pricing games

Every dispatcher, every MDT, every add-on — metered and marked up.

03

You can't change anything

Want a different call layout or workflow? Open a ticket and wait a quarter.

04

Slow, stale screens

Boards that lag, statuses that fight each other, refreshes that miss the update.

05

Mobile as an afterthought

An MDT that doesn't match the console — so the field and the room disagree.

06

Data you can't get out

Reporting locked behind exports that never quite fit NIBRS, NFIRS or NEMSIS.

How we answer each of these

Deployment

Run it our way or yours.

Some agencies want the servers gone. Some cannot put dispatch anywhere but their own network. P1 is the same product either way — the same console, the same mobile, the same data model.

CloudWe host it, patch it and back it up. No server room, no SQL administrator, no hardware refresh on your capital plan.
On-premisesEverything on your own network. Core dispatch needs only the CAD and your database — if the internet drops, your dispatchers keep dispatching.
Either way, CJISPer-user accounts, enforced password policy, and an audit trail that names a person rather than a workstation.
Integrations

Connects to what you already run.

Phones, radios, vehicles, stations and the agencies next door. P1 brings them into the call instead of leaving a dispatcher to copy between screens.

Every integration

E911 ANI/ALICaller and location into the call
AVL / GPSLive unit positions
Station alertingTones with the dispatch
PagingVolunteers' phones and pagers
GIS & shapefilesAddresses and boundaries
Active911Mapped alerts from the CAD
CAD-to-CADCalls with neighbouring agencies
REST APIYour own tools on your data
Next step

See it run a real call.

A working demo on your own addresses and your own units — not a slide deck. Bring the dispatcher who will have to use it at 3 a.m.