Development direction · Not current operational CAD

A configurable multi-agency operating environment.

Nexus CAD is intended to connect calls, units, records, agencies, civilian information, permissions, jurisdiction configuration, and FiveM instead of operating as an isolated CAD product.

Open current CAD / MDT Back to Nexus hub

The stable ASRP CAD address currently routes to Imperial CAD. That remains the approved operational CAD/MDT until ASRP formally announces a Nexus CAD transition.

Operational areas

Different disciplines, connected where they need to be.

Nexus CAD is intended to provide purpose-built operational sections rather than forcing every agency into a law-enforcement-only workflow.

Law enforcement

Calls, units, person/vehicle records, reports, warnings, citations, charges, arrests, warrants, BOLOs, evidence references, and configurable enforcement authority.

Fire & EMS

Dispatch, unit/apparatus status, incidents, patient or response documentation where appropriate, mutual aid, and agency-specific operational forms.

Dispatch & support disciplines

Emergency communications, DOT, tow, judicial/courts, civilian, and a distinct private-security CAD area can use separate workflows with controlled interoperability.

Records

More than calls and unit status.

CAD and records are intended to share one permission-aware data model so authorized information can move through the roleplay ecosystem cleanly.

People

Identities & credentials

Configurable identity cards, driver licenses, hunting/fishing licenses, permits, professional or business licenses, and other jurisdiction-specific credentials.

Property

Vehicles, vessels & weapons

Vehicle registrations, boats/vessels, firearms or weapons records, ownership history, status, and jurisdiction-specific registration rules.

Enforcement

Reports & actions

Agency reports, citations, warnings, charges, arrests, warrants, alerts, and record-linked workflow history.

Authority

Cross-agency scope

Configurable rules can allow non-law-enforcement agencies to issue specific citations or enforcement actions where the jurisdiction and roleplay framework permit it.

Jurisdiction packs

Alaska configuration without hard-coding Alaska into Nexus.

A reusable jurisdiction pack can provision established agencies, terminology, unit conventions, call types, statuses, forms, permissions, numbering formats, maps, workflows, response plans, and code/statute references where appropriate.

Tenant-specific changes remain customizable after installation, and future pack updates are intended not to overwrite local changes.

ASRP deployment

Alaska is the reference jurisdiction.

ASRP is the first community used to build and refine the system. The Nexus core should remain community-agnostic so future states and communities can use their own configuration packs.

Interoperability

Controlled sharing, not a fake government database.

Long-term Nexus federation can support authorized cross-community information sharing while clearly identifying the source tenant, record owner, status, effective dates, restrictions, and query history. It must never imply access to NCIC or any real government database.

Integration