ctHelixOne

Use cases

From event posts to permanent dispatch centers.

Six scenarios we hear from operators every week — full-time municipal agencies, private security ops, EMS services running mixed 911 + non-emergent, multi-day events, recurring markets, and backup-CAD postures. All six ship at launch: full-time dispatch and high-volume operations on ctHelixCAD™; smaller agencies, security firms, events, and EOC backup deployments on ctHelixCAD™ Portable. Same backbone, same security, same audit model. Find the one that looks like your shop, or tell us about yours.

Police Chief · Municipal agency · 24/7 dispatch ctHelixCAD

The Primary CAD

A full-time dispatch center running ctHelixCAD™ as primary — twin consoles, three shifts, every call. Production-grade SQL on a hardened Linux VM with replication and hot-standby; encryption at rest, TLS in transit, the agency’s existing DBA team handling backups alongside the rest of the fleet. ctHelixRMS™ feeds from the same incidents into long-form records; ctHelixMobile™ puts the right surface in every cruiser. Console operators authenticate against agency-managed identity; field units carry rotated PINs on an isolated auth surface.

EMS Service Director · mixed 911 + non-emergent · EMS Transport add-on ctHelixCAD

The EMS Service

Non-emergent transports and on-scene patient flow on the same board as live 911 traffic. Production deployment — replication-ready, hot-standby, audit-log-heavy, with PHI tables scoped to the EMS Transport module and a distinct PHI audit log separate from the general audit log. 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 encrypted-at-rest billing export to your existing partner. CAD-only — we capture the data, you keep your existing PCR.

Private security firm · stadium event ctHelixCAD Portable

The Security Detail

Forty officers on shift, four supervisors, one ops command. ctHelixCAD™ Portable on the firm’s own hardware with full audit, encrypted at rest, TLS in transit. Supervisor PINs go out at the pre-event briefing, Argon2id-hashed, rotated in seconds if a phone goes missing. Every status, every assignment, every incident note ends up in one timestamped, attributed log. The after-action report writes itself, and the client gets a single PDF that proves coverage minute-by-minute.

Event Operations Lead · multi-day event · mixed agency ctHelixCAD Portable

The County Fair

Three dispatcher seats, twenty units in the field, EMS and PD sharing the board. ctHelixCAD™ Portable deploys on a dedicated mini-PC at the field command post — one host, encrypted at rest, snapshotted to an encrypted backup target every night. 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 encrypted archive in your backup vault — searchable for the after-action review, the insurance claim, or next year’s planning meeting.

Emergency Management Director · regional county ctHelixCAD Portable

The Backup CAD

Your primary CAD goes down. ctHelixCAD™ Portable comes up on a hardened backup host on the EOC table in minutes — encrypted at rest, 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 — operational familiarity transfers directly, and the backup host is just as protected as the primary’s production engine.

Municipal Special Events Coordinator ctHelixCAD Portable

The Monthly Market

A two-hour Saturday market doesn’t need a permanent CAD — but it does need a record. ctHelixCAD™ Portable runs from a dedicated field box, encrypted at rest, 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, and the encrypted database travels with the coordinator under full disk encryption.

Don’t see yours?

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.

Get in touch

Tell us how you operate. We’ll show you the fit.

A 20-minute conversation with the team who built it. No nurture sequence.