Processing Order and Prioritization
The calculation of resource suggestions is strictly sequential across three levels. Each level evaluates the results of the previous level to avoid redundancies (Delta Calculation).
Level | Designation | Focus | Core Question | Relevant Fields |
1 | Responsibility | Who is responsible here according to the dispatch plan? |
| |
2 | Technology & Quantity | Are specific vehicle types or special equipment still missing? |
| |
3 | Medical | Is patient care (Doctor/Transport) guaranteed? |
|
Level 1: Area Responsibility
This level identifies units based on their local responsibility and tactical assignment.
Process: Matching of
DispatchGroups(responsibility tags) of the operation keyword with theDispatchGroupsof the operation area.Priority: Highest. These units form the foundation of the suggestion.
Relevant Fields:
IKeyword.DispatchGroups,IArea.DispatchGroups,IUnit.DispatchGroups.
Level 2: Equipment Requirements
This level ensures that all vehicle types and equipment required by the keyword are present in sufficient quantities.
Process: Comparison of the required equipment list with the inventory lists of available units.
Relevant Fields:
IKeyword.RequiredEquipment,IUnit.Equipments.Optional Control (Option 8 & 22): See the Decision Table for System Options.
Decision Table for System Options (Level 2)
Level 2 (Equipment) is highly configurable. The behavior changes significantly depending on the settings:
Option | Status | Impact on Suggestion |
Option 8: Check equipment despite area responsibility | OFF | Level 2 is ignored if Level 1 has already found units. |
Option 8: Check equipment despite area responsibility | ON | Level 2 ALWAYS checks if quantities/technology are sufficient. |
Option 22: Count equipment from area responsibility | OFF | Units from Level 2 are added in addition to Level 1 (Risk of duplication). |
Option 22: Count equipment from area responsibility | ON | Level 2 first utilizes the inventory of units already suggested in Level 1. |
Level 3: EMS Requirements
Final verification of medical capacities.
Process: Summed requirement of doctor levels and transport categories minus the capacities already covered by Levels 1 and 2.
Relevant Fields:
Keyword.DispatchAmount...(e.g.,AmbulanceUrgent,Doctor),Unit.Category,Unit.DoctorOption.
Availability Check in the Suggestion System
Resource availability is the prerequisite for being considered in any of the three logic levels (Responsibility, Equipment, EMS). The system checks both the technical status and the current tactical commitment. A resource is only suggested if all of the following points apply:
Status: Not in Status 3, 4, 6, or 7 (Status 8 is optionally controllable via Option 4: Suggest resources in Status 8).
Duty Status: The unit is currently marked as "On Duty".
Commitment: The unit is not tied to another operation or reserved for one.
Status Filter (Exclusion Criteria)
Units in specific states are fundamentally not suggested. Availability is filtered based on the current status of the resource.
Default Unavailable Statuses:
Not ready for dispatch: Status 6 or explicitly "Off Duty".
Committed to operation: Status 3 (En route), Status 4 (On scene), Status 7 (Patient pickup/Transport).
In Disposition: Units that have already received the transient status "Dispatched" manually or through another process.
Contextual Availability
The system distinguishes whether a unit is already committed to the same operation or to external operations.
External Operation: Units whose
CurrentOperationIddoes not match the ID of the current operation are considered occupied.Same Operation: Units that are already part of the current operation are counted as "present" in the delta calculation for Levels 2 and 3, but are not marked as "to be newly suggested."
Reservations: Units reserved for another operation are ignored.
Special Case: Destination Reached (Status 8)
The availability of units at the destination (e.g., hospital) is controlled via a global system option: Option 4: Suggestion in Status 8.
Disabled (Default): Units in Status 8 are considered "still committed" and are not suggested.
Enabled: Units in Status 8 are treated like free units (Status 1/2) and flow into the calculation. This is particularly relevant in areas with high operation density to reintegrate units into area coverage before the previous transport is fully concluded.
Influence of Availability on the Logic Levels
The availability of a unit is not just a filter; it significantly determines which alternatives the system chooses and how the remaining requirement is calculated.
Influence on Area Responsibility (Level 1)
In this level, availability controls the selection within Alternative Groups (OR-links).
Logic: If the system searches for a vehicle from a group (e.g.,
(HLF-1; HLF-2)), it checks the units in the defined order.Impact: If the primary unit (
HLF-1) is unavailable (e.g., Status 3 or 6), the system immediately skips it and checks the availability of the next unit (HLF-2).
Influence on Equipment Requirements (Level 2)
Availability here affects requirement fulfillment and supplementary dispatch.
Pre-filtering: Before the equipment logic calculates which unit should bring a missing device (e.g., "Boat"), all unavailable units are removed from the search.
Interaction with Option 22: Only units classified as available in Level 1 can have their equipment credited toward the total requirement.
Influence on EMS Requirements (Level 3)
In the medical level, availability ensures the guarantee of care.
Credit: Medical capacities (e.g., Doctor level) are only credited from units identified as available in previous steps.
Selection: The system suggests the geographically closest EMS resource that is available at the time of calculation.
System Maintenance Instructions
For administrators implementing ResQueServe for the first time or making fundamental changes to the dispatch plan, the recommendation is: System maintenance should be performed "backward" – starting with Level 3.
Use Level 1 for strategic distribution (Who should primarily respond?).
Use Level 2 for technical security (What is the minimum equipment required on-site?).
Use Level 3 for basic medical care.
Why not start with Level 1 (Area Responsibility)?
Area logic is the most complex layer because it links individual tags with local responsibilities. Starting here builds a rigid framework without defined underlying vehicle categories and equipment features. This often leads to Levels 2 and 3 later adding too many or incorrect units because the vehicle master data does not align cleanly with the keyword requirements.
The "Bottom-Up" Approach (Recommendation)
Step 1: Configuration of Level 3 (EMS Requirements)
Begin by defining the medical care levels in the keywords and the categorization of medical resources.
Benefit: You ensure that basic patient care (Doctor, Ambulance) always functions, independent of complex fire department dispatch plans.
Step 2: Configuration of Level 2 (Equipment Requirements)
Now define the technical requirements and the vehicle inventory.
Benefit: The system learns which vehicles can perform specific tactical tasks (e.g., Aerial Ladder, Rescue Engine). Since Level 3 is already configured, the system recognizes if a vehicle (e.g., an HLF) simultaneously fulfills a medical requirement.
Step 3: Configuration of Level 1 (Area Responsibility)
Finally, maintain the strategic responsibilities (DispatchGroups) and the area assignments.
Benefit: Since Levels 2 and 3 are already calculating correctly, Level 1 only serves to define "Preferred Units" (who should primarily respond). The system utilizes the existing logic of the other levels to cleanly subtract the remaining requirements and avoid over-dispatching from the start.