Ember Analytics builds tools for the administrative weight that lands on fire officers every shift. Force-hire eligibility, pre-incident planning, crew training, daily field management. All of it built by a fire captain still working the job.
These aren't features that came out of a product roadmap. Each tool in this suite exists because Brian Hollis ran into a real operational gap and built his way out of it.
Calculates force-hire eligibility against your CBA's actual language. Consecutive day caps, hour thresholds, exemptions, rotation order. The list is ready before your shift commander needs to make the call.
Post the whole coverage period at once and let people claim it. Every open seat for the window goes on one board, sign-up opens in phases by role class, and eligibility, hour caps and exemption thresholds are enforced as members claim rather than argued about afterward. When the window locks, the involuntary draft order is already built.
Shift scheduling built by a fire captain, not a software vendor. Handles 24/48, 24/72, 48/96, Kelly cycles, Debit Days, and hybrid rotations without forcing your department to bend to a template. Overtime tracking, leave management, and open-shift notifications are built in from the start.
Digital DORs and FTEP milestone tracking for probationary firefighters. Every shift documented, FTO sign-offs recorded, performance trends visible to supervisors without digging through paper binders.
One roster of record that every other tool reads from. Assignment, rank, station, shift, EMS level, hire date and contact info stay in one place, and the DOR, sign-up and eligibility tools pull their name lists from it instead of each keeping a copy that drifts.
Scenario design and facilitation for company and command-level training exercises. Build a credible multi-agency tabletop in hours, with documentation that holds up to after-action review.
Self-service booking for classrooms, apparatus, training equipment, and drill grounds. Confirmations go out automatically. Events write directly to Google or Outlook calendars.
Pre-incident planning built for suppression crews, not administrators. Every target hazard in the mutual aid zone documented, ranked by priority, and readable in the seconds you have on the way in — building profile, hazard flags, water supply, access, and the tactical objectives that follow from them.
The investigator’s initial report, start to filed, in one pass. Twenty-two sections follow the scientific method through scene examination and classification, photos and a scene diagram embed as you go, and enclosure PDFs merge onto the end. Nothing leaves the device until you download the finished report.
The number your chief gets asked for at budget time, calculated the same way every time. The BC or IC completes it before the scene is released: suppression mode, fire stage on arrival, and a confidence tier, then each exposure node valued separately. Loss and value saved come out the other end with the assumptions written down.
The situational awareness display, deployed wherever your people already look up. One engine drives the watch-desk board, the Training Division screen, and anything else you point it at — on-duty roster, active calls, classroom bookings, apparatus out of service, weather, and value saved, all pulled live and refreshed on their own clocks. It is a picture of the department right now, not an alerting device.
A full-screen channel for the screens your department already owns — day rooms, training classrooms, apparatus bays, headquarters lobbies. Slides pull from live data instead of a deck somebody has to remember to update, and the loop keeps running whether or not anyone is watching.
Safety information where people will actually read it. Each issue is a single broadsheet built around one hazard — the physics, the phase-by-phase response, the quick-reference matrix, and the contacts — laid out to be absorbed in the four minutes somebody is sitting there. Print it, post it, and the training happens without a class.
Reporting dashboards that pull operational data and generate the outputs your chief needs for city council briefings and accreditation reviews. No manual data pulls.
Most public safety software comes from vendors whose staff has never worked a shift. The design decisions reflect that.
Every tool started as a problem Brian Hollis ran into on shift. Not a feature requested on a survey. A real operational gap that cost time on a real call.
Eligibility tools are built to match your department's specific CBA language. Consecutive-day caps, rotation rules, and exemption logic come directly from your contract. Generic approximations create grievances. These don't.
No 18-month enterprise implementation. Most tools go live within a few weeks and connect to the scheduling platforms your department already uses, including CrewSense and TeleStaff.
Ember Analytics was founded by Brian Hollis, a Fire Captain with 30 years across volunteer fire, hospital emergency medicine, and career fire service at Salem Fire Department. He spent 10 of those years as a SWAT medic and holds command-level HazMat certification.
Every tool started as a real problem Brian ran into on the job. A force-hire process too slow for a 0300 callout. Pre-incident plans in binders nobody updated. Training coordinators managing rosters over text message.
An outside vendor can ask fire departments what they need. Brian knows without asking. That's the difference in how these tools are built.
"I built the tools I wished existed when I was making force-hire calls at 0300, trying to stay compliant with a CBA I had memorized but couldn't cross-reference fast enough. These tools don't guess at what fire departments need. They're built by someone who still works the job."
Every department runs different CBA rules on a different scheduling platform. Request a demo and Brian will walk through exactly how each tool adapts to your setup.
What fire officers say
The MOT tracker cut our force-hire call time from 20 minutes to under 3. We used to have captains cross-referencing spreadsheets and the collective bargaining agreement at the same time. Now the list is just there.
ASHER finally replaced the binder system we'd been dragging to pre-plans for 15 years. Crews can pull up a target hazard from the apparatus on the way to a call. That's the only version of pre-incident planning that actually gets used.
The tabletop builder let us run a full multi-agency exercise with 40 participants and complete documentation in one afternoon. We used to spend two weeks building the scenario in PowerPoint and still end up with a mess.