Integrations

Connects to what you already run.

Phones, stations, vehicles, responders' phones and the agencies next door. Priority One brings them into the call instead of leaving a dispatcher to copy between screens.

Alerting & paging

Integrated

Active911

CAD incidents push to Active911 with the address, type and notes, so responders get mapped alerts with navigation.

  • Mapped alert delivery
  • Turn-by-turn navigation
  • Incident data sync
  • Response tracking
Integrated

IP station alerting

Network-based station alerting: tones, PA announcements and display screens at the station, driven by the assignment.

  • Custom tone sequences
  • Per-station configuration
  • Display screen triggers
  • Multi-bay control
Integrated

Paging

Outbound alerting that goes with the dispatch, including volunteers' phones and pagers.

  • Sent with the assignment
  • Per-agency paging rules
  • Volunteer notification

Data & E911

Integrated

E911 ANI/ALI

Incoming 911 calls populate caller name, address and callback number into a new incident.

  • ANI/ALI auto-populate
  • Wireless Phase I/II
  • Callback number capture
  • Address validation
Integrated

GIS & shapefile import

Address points, street centrelines, town boundaries and response areas from standard GIS files, into one spatial database.

  • Shapefile import
  • Response area sync
  • Address geocoding
  • WGS84 throughout
Native

CAD-to-CAD

Share incidents with a neighbouring centre — request units, pass calls and keep both records in step.

  • Mutual-aid requests
  • Shared incidents
  • Each side keeps its own record

Responders & hardware

Native

Priority One MDT

The in-vehicle system, connected through the P1 API over HTTPS: live calls, statuses, notes, premise cautions and your own map.

  • Real-time call data
  • Crew status updates
  • Self-initiated activity
  • Address history
Native

P1 Station Mobile

A mobile app for station dashboards: active calls, station assignments and alert tones on tablets and wall displays.

  • iOS and Android
  • Station dashboard mode
  • Alert tone playback
  • Call detail display
Integrated

AVL / GPS

Vehicle positions from GPS hardware feed the dispatch map and travel-time recommendations, with history kept for playback.

  • Multi-vendor GPS
  • Live map positions
  • Proximity dispatch
  • Track history
Integrated

Vehicle hardware

The MDT runs on ruggedised laptops and tablets from the major manufacturers — any Windows device in the field.

  • Ruggedised laptops
  • Rugged tablets
  • Any Windows device
Planned

Radio systems

Console-to-radio integration for unit ID decoding and emergency button alerts feeding the CAD.

  • Unit ID decoding
  • Emergency button
  • Status auto-update
Planned

ePCR / patient care

Incident data, demographics and transport details bridged into your electronic patient care reporting software.

  • Incident data bridge
  • Transport details
  • NEMSIS-ready fields

Records & reporting

Planned

Records management

Closed incidents bridged into your RMS — incident data, involved persons and vehicles, and dispositions.

  • Incident data export
  • Person and vehicle records
  • Disposition mapping
Planned

State reporting exports

NFIRS, NIBRS and NEMSIS exports from the call record, validated before they leave — with the details a CAD does not capture flagged for your RMS or ePCR.

  • NFIRS first, then NIBRS and NEMSIS
  • Validate before submit
  • Gaps flagged, not guessed
Native

REST API

Your own tools, dashboards and partners on your data — calls, units and the map, with keys you control.

  • Documented endpoints
  • Per-key scopes
  • Your SQL Server — it's your database
Need something else?

Tell us what you need to connect.

If your agency relies on a system that isn't listed, ask. We'd rather build the right link than have a dispatcher copy between screens.