Use cases
Six scenarios we hear from operators every week — full-time municipal agencies, multi-day events, backup deployments, security details, recurring markets, and EMS services running mixed 911 + non-emergent. Same product, every shape. Find the one that looks like your shop — or tell us about yours.
A full-time dispatch center running ctHelixCAD™ as primary — twin consoles, three shifts, every call. ctHelixRMS™ feeds from the same incidents into long-form records; ctHelixMobile™ puts the right surface in every cruiser. The agency owns the host, the database, and the upgrade cadence. Same product the next-county-over festival ops team uses — same backbone, just scaled up.
Three dispatcher seats, twenty units in the field, EMS and PD sharing the board. Configure posts and roster in the off-season; clone them into this year’s event in under a minute. Pack up Sunday night, archive the database, repeat next July. The previous year’s incident log is one SQLite file in your backup vault — searchable for the after-action review, the insurance claim, or next year’s planning meeting.
Your primary CAD goes down. ctHelixCAD™ comes up on a laptop on the EOC table in minutes. Pre-loaded rosters, pre-built CFS codes, ready to take traffic. When the primary is back, you have a full timestamped incident log to import. The same instance can be spun up for tabletop exercises and quarterly drills — the muscle memory transfers directly.
Forty officers on shift, four supervisors, one ops command. Supervisor PINs go out at the pre-event briefing. Every status, every assignment, every incident note ends up in one timestamped log. The after-action report writes itself, and the client gets a single PDF that proves coverage minute-by-minute.
A two-hour Saturday market doesn’t need a permanent CAD — but it does need a record. ctHelixCAD™ runs from a laptop in a folding-chair command post, then sleeps until next month. Same configuration, every time. Numbering with month tokens means each market’s incidents are uniquely tagged without any operator intervention.
Non-emergent transports and on-scene patient flow on the same board as live 911 traffic. Scheduled dialysis runs and inter-facility transfers sit alongside spontaneous calls; the same units pick them up in mixed mode. Multi-patient transports carry explicit phase timestamps — loaded, departed scene, arrived destination, transfer of care, cleared — and the transport phase drives the unit status automatically. Service-level classification (BLS, ALS, Critical Care) feeds the billing export to your existing partner. CAD-only — we capture the data, you keep your existing PCR.
Operations come in more shapes than four cards can hold. Tell us how you work — we’ll tell you whether ctHelixCAD™ is the fit or whether you need something else.
A 20-minute conversation with the team who built it. No nurture sequence.