Our founder runs IT for a fire district. The apps we build for public safety aren't theoretical — they're things we'd want on our own apparatus and at our own dispatch console.
Common in fire districts, EMS agencies, combined services, and any agency where the IT person is also "the IT person" for half a dozen other things.
Your CAD does CAD. Your RMS does RMS. Your scheduling platform does scheduling. But the tools between them — equipment tracking, inspection workflow, training records, pre-plan management, FDID reporting prep — are spreadsheets and goodwill.
ePCRs get exported, billing company gets the file, sometimes the data is clean, sometimes it isn't. Revenue leaks because nobody has the bandwidth to audit it end-to-end.
Or worse, in a PDF library nobody updates. When a crew rolls up on a target hazard at 0300, the latest pre-plan is probably not what they're looking at.
Inspector goes out with a clipboard. Notes get typed up at the station. Re-inspections track manually. Fees billed slowly. Business owners ask for status updates and there's no portal.
Hours, certifications, evolutions, in-service — tracked in 3-4 different places. When the ISO audit window opens, the training officer spends weeks pulling reports.
NFPA inspection cycles tracked on a wall calendar or in a spreadsheet. SCBA cylinder hydros, hose service tests, pump tests, ladder tests — paperwork-heavy, error-prone, audit-painful.
Most of these are not hypotheticals — they're running in production today inside an Arizona fire-and-EMS operation we run end-to-end. The rest are well-scoped extensions of that same stack. All of it integrates with the CAD, RMS, ePCR, and scheduling vendors you already pay for (ESO, ImageTrend, FirstDue, etc.) rather than replacing them.
Production system we run today: 50+ servers, 100+ network endpoints, 100+ field devices, 10 fire stations, dispatch alerting integration, hypervisor and VPN tunnel health, UPS / iDRAC / printer telemetry — rendered as an auto-rotating dashboard fit for a comms-room TV. Per-asset health, push alerts via email and SMS, mobile-friendly views. Built for the way fire and EMS actually want to see operational state, not a generic NOC tool retrofitted to public safety.
Live in production: dispatch event fires → per-station, per-apparatus, per-role SMS messages go out within seconds via an email-to-SMS carrier gateway. Rate-controlled, delivery-audited, group-managed via a web portal that syncs from your directory. Sends operational notifications every day for an Arizona public-safety operation.
We've integrated production Phoenix-class fire-station alerting controllers (10 stations, multiple firmware generations) with our monitoring and notification stack — real-time portal status, dispatch-event ingest, peripheral health (turnout-room speakers, ATX, mod racks), automatic cross-posting of dispatches to mobile devices via the SMS gateway above. Same pattern adapts to any HTTP-reachable alerting vendor.
Inspector works from a tablet: scheduled inspections, current code references, photo capture, deficiency tagging, re-inspection scheduling, signed receipt for the business owner. Business owners get a portal showing their status. Billing exports clean. Built on the same field-capture stack we use for other mobile public-safety workflows.
Every SCBA bottle, hose, ladder, pump, AED — with service intervals, last inspection, next-due dates. Automatic notifications. Audit-ready compliance reports. Visible to the apparatus officer doing morning checks. Same compliance-tracking discipline we apply to enterprise IT asset audits across multi-site fire operations today.
Hours by category, certifications and expirations, ISO-credit-relevant categorization, automatic dashboards for the chief, captain, and individual firefighter. State and national reporting becomes a query, not a project. Pulls together what's normally split across WHD, scheduling, and a spreadsheet.
The boring middleware between your dispatch vendor, your records vendor, your ePCR platform (we've integrated ImageTrend-class systems via S2S VPN in production), your billing service, and your in-house tools. We've built dispatch → ePCR → billing flows that run daily in production. Same patterns apply to most vendor combinations.
Bare-metal imaging at scale via a dedicated isolated PXE network, gold-master images for ruggedized in-vehicle tablets (Panasonic Toughbook FZ-class fleet today), automated post-deploy configuration (CAD client install, GPS fix, screensaver, branding, all the small ops fixes a brand-new MDC needs before it's road-ready). Cuts hours off every new-unit setup.
Optimized Working's founder is the active Systems Administrator for a fire district. That means the software we build for public safety has been pressure-tested against actual fire-district realities: cross-domain authentication, MDC fleet quirks, integrating with CAD vendors who don't love opening their APIs, the politics of board approval for any spend over $X, the difference between "the chief said yes" and "the union also said yes."
We also know what's not worth building. If your existing CAD/RMS does it, we'll tell you to use what you have. The custom work is for the gaps — and there are always gaps. Our engagements with public safety tend to focus on the boring, durable infrastructure: equipment, training, inspection, target-hazard, audit prep. The stuff that quietly makes the difference between an OK audit and a great one.
Tell us what your CAD/RMS vendor doesn't ship that you wish they would. We'll come back within one business day with an honest take.
solutions@optimizedworking.com