Every measure against its objective

Each metric is reported as the same measure card: adopted objective · measured 90th percentile · gap · share of responses meeting the objective · sample size. Compliance is judged per response against that response's own objective (its demand zone, risk class and service line), then aggregated. Click any metric row to see its distribution and slowest responses

End-to-end response continuum — call received → on location

Measured 90th-percentile segments stacked left to right, with the adopted objective marked on the same clock. Segment 90ths are independent tails and do not sum to the total-response 90th — the total is computed from incident-level totals. Click a segment card for its distribution

Measure cards —

Objectives per NFPA 1750 station-based clocks (elements) and demand-zone totals (Urban 9:00 @ 90% · Suburban 10:00 @ 80% · Rural 14:00 @ 80% · Rural 14:00 @ 80%). Gap shading: green inside objective, red outside.

Metric	Clock	Objective	Measured 90th	Gap	% Meeting	Std	n	vs objective

§ 02 · Trends — quarterly & annual

Direction of travel

Quarterly points show the operational trend; the annual baseline table is the accreditation-format record (CPSE-style, per-year 90th percentiles vs. target). Trend charts respect the service / agency / zone filters but always show the full history.

Trend metric

Compliance trend — % meeting objective, by quarter

Dashed line = NFPA 1750 performance standard for the scope — click a point for that quarter's responses

FireEMSStandard

90th-percentile trend — by quarter

Solid line = measured 90th percentile · dashed = adopted objective

FireEMSObjective

Annual baseline performance — 90th percentile times (CPSE format)

Per calendar year, with the trailing aggregate and the adopted target. LTD = limited data: fewer than 50 qualifying responses — median reported instead of 90th percentile.

§ 03 · Where & when — breakouts

The same scorecard, re-cut

One table, five pivots. Each cell shows the measured 90th percentile with the compliance share underneath; cells shade red as they fall below the standard. Click a row to drill into that slice

Break out by

90th percentile · % meeting objective — current period scope

Zone compliance map — total response vs objective

Demo planning zones (illustrative tract geometry) across the five-station footprint; ● = fire stations. Fill = % of responses meeting the total-response objective. Click a zone to drill in

Zone compliance map — ERF assembly vs objective

Concentration view: share of ERF-qualifying incidents assembling the required force in time. Grey = no qualifying incidents in period.

§ 04 · Force assembly — concentration

Effective response force

Distribution metrics grade the first-arriving unit; concentration grades assembling the full force the risk class demands — ERF 28 personnel (moderate) / 42 (high) for structure fires, 6 for cardiac arrest, per the adopted critical-task analysis.

ERF assembly vs. objective, by risk class

ERF clock: event create → arrival of the unit completing the required force. Click a row for the slowest assemblies

Risk class	ERF Personnel	Objective	Measured 90th	Gap	% Meeting	Day %	Night %	n

§ 05 · Workload & concurrency — the dual-role reality

Who is deployed, for how long, and how often calls collide

The department staffs dual-purpose fire/EMS personnel across all five stations — the crew on the ambulance is the crew that isn't on the engine. Overlapping incidents are therefore a core performance measure, not a curiosity: every overlap is a moment the system ran with less than its full force. Click any row to drill to the incidents

Commitment by incident type — how long crews are tied up

Unit commitment = dispatch → clear. Personnel-hours = Σ personnel × committed time.

Incident type	n	Avg personnel	Median commit	90th commit	Personnel-hrs

Active incidents by hour of day

Average simultaneous incidents underway, by clock hour — the daily shape of system load

Overlap rate by quarter

% of calls beginning while the same agency was already committed elsewhere

The concurrency penalty — clean vs. overlapped responses

"Overlapped" = the call began while at least one same-agency incident was still committed. The delta is the measurable cost of the dual-role staffing model.

Service	Clean n	Clean 90th	Clean % meet	Overlapped n	Overlapped 90th	Overlapped % meet	90th penalty