Skip to content
MissionChief UK Operational Field Guide
Guide online TKB Games

Fire Mission-Family Pressure Analysis

Stage 37A closes by converting the complete canonical Fire mission estate into a live, evidence-labelled demand profile. The analysis below reads the same versioned missions.json export used by Mission Lookup and the public API, then reports only transparent counts and sums from published fields.

Current evidence baseline: 28 July 2026.

Use the dashboard to identify:

  • which capability families occupy the largest part of the Fire catalogue;
  • which guaranteed resources accumulate the greatest catalogue-wide demand;
  • which missions create the highest single-incident unit load;
  • where independent alternative groups create command or specialist bottlenecks;
  • where patient and personnel fields add pressure beyond vehicle quantities;
  • which family should drive the next fleet, training or geographic investment.

It does not estimate how often a mission will spawn. A quantity summed across the catalogue is a catalogue pressure indicator, not an expected daily dispatch total.

A mission can belong to several families because operational capabilities overlap. For example, a railway incident may also be technical rescue, mass casualty, HazMat and foam response.

FamilyTagging evidence
Airfield and airportAirport category, airfield extensions or dedicated airfield resources
Railway and tunnelRailway categories, Railway Fire Response or Road Rail capability
Flood and water damageFlood/pump extensions, water-damage category or Flood Rescue Units
Wildfire and forest firePublished mission name contains forest fire or wildfire
HazMat and CBRNHazMat, CBRN or HazMat-container alternatives
Foam and fire supportFire-support category, Foam Extensions or verified foam resources
Technical rescueTechnical Rescue Extensions, Rescue Support Vehicles or rescue containers
Mass casualty and high patient loadMass-casualty category/equipment or patient maximum of at least 20
Rural fireOfficial rural category
Urban and structural fireOfficial urban category
General fireNo specialist analytical tag applies

Loading the canonical Fire mission export…

Family profile

Analytical family Missions Guaranteed units across catalogue Fire Engine units Highest single mission
Loading…

Highest accumulated guaranteed-resource demand

This table sums only guaranteed resource rows in the current filter. Alternatives remain separate because selecting one valid option is a dispatch decision.

Canonical resource ID Guaranteed quantity across catalogue Missions containing the guaranteed row
Loading…

Highest single-mission guaranteed load

Mission Analytical families Guaranteed units Independent alternative slots Patient maximum
Loading…

This is the arithmetic sum of all quantities in requirements.guaranteed. It provides a reproducible measure of visible vehicle/resource pressure. It does not account for journey time, treatment duration, crew availability or whether one vehicle can satisfy another capability through verified substitution.

This sums the quantity attached to every alternative group. Each group must be treated independently. A single ICCU, Ambulance Control Unit or specialist vehicle must not be reused across several slots unless dispatch behaviour explicitly proves that reuse.

The dashboard reports the published maximum patient field. It does not convert patients into a guessed ambulance requirement. Treatment, transport probability, critical-care probability, hospital availability and handoff time remain separate operational constraints.

A mission is counted when it publishes required, available or ranged personnel data. The count indicates where vehicle-only fleet planning is insufficient; it does not flatten different personnel semantics into one number.

  1. Select the family currently generating delays or alliance dependence.
  2. Review its accumulated guaranteed-resource table.
  3. Inspect the highest single-mission loads.
  4. Open representative missions in Mission Lookup.
  5. Test two or more incidents in the Concurrent Fleet Planner.
  6. Compare candidate resources in Resource Comparison.
  7. Identify whether the deficit is quantity, geography, training, command, towing, carrier capacity or another service.
  8. Correct the measured bottleneck before activating more generators.
Pressure patternRecommended interpretation
High mission count, low single-mission loadPrioritise geographic frontline coverage and routine concurrency
Low mission count, high specialist loadProtect rare specialists and use regional reserve planning
High alternative-slot pressureIncrease independently crewed command or substitution options
High patient maximaAudit ambulance command, transport, critical care and hospitals separately
High Fire Engine accumulationExpand staffed frontline depth before adding another specialist generator
High technical-rescue accumulationDistribute Rescue Support and trained crews by response zone
High railway/airfield/flood pressureCommission the complete cross-service chain rather than Fire assets alone

Batch 7 completes the Fire & Rescue operational-guide programme:

  1. progression foundation;
  2. specialist extensions and container logistics;
  3. training and personnel planning;
  4. airfield and railway response;
  5. wildfire, flood and water rescue;
  6. major-incident resilience;
  7. live mission-family pressure analysis.

The Fire programme now moves into evidence maintenance. The next service programme is Stage 37B — Ambulance & HART operational progression.