What Is Modular Dispatch?

Traditional emergency software is monolithic: you buy a massive system and get features for disciplines you’ll never use. TPT Emergency takes the opposite approach. It’s a common dispatch layer with swappable modules on top.

Think of it like a smartphone. The operating system (common dispatch layer) handles calls, contacts, and messaging. Apps (modules) provide specialised functionality. You install only the apps you need. TPT Emergency works the same way.

The Common Dispatch Layer

Every module in TPT Emergency sits on top of a shared foundation called the Common Dispatch Layer. Regardless of which modules are enabled, every agency shares:

• Incident management — A unified incident record that any module can read and extend
• User roles & permissions — Granular access control with role-based permissions across all modules
• Audit logging — Every action logged with a tamper-evident event history
• Resource tracking — Shared inventory of units, equipment, and personnel
• Real-time sync — Socket.IO mesh network broadcasts updates to all connected clients
• Offline data — SQLite + IndexedDB storage used by all modules uniformly

A Fire module and an Ambulance module can both reference the same incident, see each other’s unit assignments, and share a common timeline — without duplicating data or building brittle integrations.

Module Breakdown

TPT Emergency ships with 20+ modules. Each can be enabled or disabled independently via the admin panel.

Integration Ecosystem

Beyond the core agency modules, TPT Emergency includes cross-cutting integration modules that connect to external systems and sensors:

• Bluetooth Beacon Monitoring — Personnel and equipment tracking via BLE beacons with real-time ranging
• Geofence Alerting — Automatic alerts when units enter or leave defined zones
• Traffic-Aware Routing — ETA calculations that factor in real-time traffic conditions
• Search & Rescue Patterns — Predefined search patterns (grid, line, spiral) with coverage tracking
• Route Calculation — Turn-by-turn routing with hazmat and vehicle-type restrictions
• Resource Maintenance Logging — Equipment inspection schedules, failure tracking, and readiness status
• Unit Shift Scheduling — Crew roster management with overtime tracking and qualification checking

Deployment Flexibility

The modular design directly enables flexible deployment. A rural volunteer fire department can run TPT Emergency on a single laptop with only the Fire and Personnel Accountability modules enabled. A metropolitan EMS system can deploy a full server cluster with Ambulance, Medical Command, Call Centre, and Weather modules active.

Because modules load dynamically at runtime, disabled modules carry zero performance penalty. The application bundle only includes what you enable — tree-shaking removes unused modules from the static HTML build automatically.

Building a Custom Module

TPT Emergency’s module system is designed for extension. A custom module is a SolidJS component that exports a standard interface. The ModuleLoader dynamically imports and renders modules based on the enabled configuration from the admin API.

To build a new module you create:

• A .jsx component file in src/modules/
• A module registration entry that defines the module ID, name, icon, and required permissions
• Optionally, a context provider if the module needs to share state with other components

The module automatically gains access to the common dispatch layer, user roles, audit logging, and real-time sync without any additional wiring. A new module can be operational in hours, not months.

Real-World Use Cases

Multi-Agency Disaster: Earthquake Response

A magnitude 7.2 earthquake damages infrastructure across a county. The Emergency Operations Centre activates TPT Emergency with Fire, Ambulance, Police, Disaster Response, HazMat, and Mutual Aid modules enabled. Each agency sees its own interface but shares a common incident map. Fire marks a collapsed building. Ambulance dispatches a medic unit. Police cordons the area. All actions appear on a shared timeline.

Single-Agency Focus: Rural EMS

A rural ambulance service with 4 vehicles deploys TPT Emergency on tablets mounted in each rig. Only Ambulance Service, Call Centre Console, and Patient Transport Tracking are enabled. The interface is clean and focused. If the service later mutual aids with a neighbouring region, the Mutual Aid module can be enabled in seconds.

Specialised Operation: Urban Search & Rescue

A USAR team deploys to a building collapse. They enable Fire Department, Medical Command, Personnel Accountability, Search & Rescue Patterns, and Bluetooth Beacon Monitoring. Each rescuer wears a BLE beacon. The incident commander sees real-time positions on the map, manages PAR checks automatically, and assigns search grids. When the operation concludes, USAR-specific modules are disabled and the team returns to standard operations.

Conclusion

Monolithic emergency software forces agencies to adapt to the software. TPT Emergency’s modular architecture lets the software adapt to the agency. Enable what you need. Disable what you don’t. Add custom modules for your unique workflows — all while sharing a common operational picture that keeps every responder aligned.