Skip to main content

Suggestion System: Area Responsibility (Level 1)

Area Responsibility identifies the primary resources in charge by matching the operation keyword with the specific dispatch plans of the operation area. It operates based on the principle of the "Tag Handshake."

Updated over 2 weeks ago

Core Principle: The Tag Handshake

The logic consists of three elements that, in their entirety, result in a suggestion:

  • Of the Keyword: The selected keyword requests a group (e.g., HLF, LZ_*).

  • Of the Area: The operation area defines which specific unit represents this group in the current district.

  • Of the Resource: The resource belongs to a unit that matches the area assignment.


Syntax and Logic Links

Punctuation in the area definition (DispatchGroups) controls the selection strategy:

Symbol

Meaning

Function

; (Semicolon)

OR link

Defines alternatives within a group. The system checks from left to right and selects the first available unit.

, (Comma)

AND link

Separates different areas of responsibility. Allows multiple units from one resource.

()(Parentheses)

Grouping

Combines units into a logical entity. A parenthesis indicates that an alternative regulation should take effect.

* (Asterisk)

Wildcard

Allows partial matches. HLF* finds both HLF-1 and HLF-2. LZ_* finds all units starting with LZ_.


Matching Process

Requirement Determination

The system counts how often a specific pattern occurs in the keywords.

  • Example: Keyword 1 requests LZ_*, Keyword 2 requests LZ_*.

  • Requirement: 2x units starting with LZ_.

Group Search in the Area

The system searches the DispatchGroups of the operation area for matches to these patterns.

  • Scenario: Area definition contains (LZ_BF_SampleTown; LZ_FF_SampleTown).

  • Logic: The system checks the availability of LZ_BF_SampleTown first, then LZ_FF_SampleTown.

Principle of Consumption

To avoid double assignments, each successfully assigned unit is locked for further searches within the same level.


Configuration Fields

Field

Path

Description

Required Units

The tactical requirement (e.g., LZ_*, B_*, TH_*).

Responsible Units

The local assignment (e.g., (LZ_BF_SampleTown; LZ_FF_SampleTown), B_SampleTown).

Associated with Unit

The identifier of the unit to which the resource is assigned.

Special Features of Wildcards

  • Prefix Search: HLF* accepts any unit starting with these characters (e.g., HLF-FW, HLF-FF).

  • Order Priority: The sorting within the parentheses corresponds to the dispatch priority (left = primary unit).

  • Availability Jump: If the primary unit is unavailable (Status 3, 4, 6, etc.), the logic jumps to the next alternative.

Priorities

  1. Locality: Only units listed in the Area of the operation site are considered.

  2. Availability: Non-operational units are skipped immediately.

  3. Order: The definition in the Area determines the dispatch sequence in case of equivalent status.


Practical Examples

Example 1: Suggestion of a Fire Station (LZ)

Configuration:

Resource

Associated with Unit

ELW 1-11-1 (Command)

LZ_Sampletown

HLF 1-48-1 (Engine)

LZ_Sampletown

DLK 1-30-1 (Ladder)

LZ_Sampletown

HLF 1-48-2 (Engine)

LZ_Sampletown

Keyword

Required Units

Room Fire

LZ_*

Area

Responsible Units

Sampletown (Downtown)

LZ_Sampletown

  • Operation: Room fire in Sampletown (Downtown)

  • Result: ELW 1-11-1, HLF 1-48-1, DLK 1-30-1, HLF 1-48-2

  • Explanation: All four resources belong to the unit LZ_Sampletown, which is responsible for the area and requested by the keyword.

Example 2: Multiple Units from one Resource

Configuration:

Resource

Associated with Unit

ELW 1-11-1 (Command)

LZ_Sampletown, RSU_Sampletown

HLF 1-48-1 (Engine)

LZ_Sampletown, RSU_Sampletown

DLK 1-30-1 (Ladder)

LZ_Sampletown, RSU_Sampletown

HLF 1-48-2 (Engine)

LZ_Sampletown

RW 1-52-1 (Rescue)

RSU_Sampletown

Keyword

Required Units

Traffic Accident

RSU_*

Area

Responsible Units

Sampletown (Downtown)

LZ_Sampletown, RSU_Sampletown

  • Operation: Traffic accident in Sampletown (Downtown)

  • Result: ELW 1-11-1, HLF 1-48-1, DLK 1-30-1, RW 1-52-1

  • Explanation: The commas create multiple units from the resources. The unit RSU_Sampletown is required by the keyword and is responsible for the area.

Example 3: Suggestion of individual Resources

Configuration:

Resource

Associated with Unit

ELW 1-11-1 (Command)

LZ_Sampletown, RSU_Sampletown

HLF 1-48-1 (Engine)

LZ_Sampletown, RSU_Sampletown, B_Sampletown

DLK 1-30-1 (Ladder)

LZ_Sampletown, RSU_Sampletown

HLF 1-48-2 (Engine)

LZ_Sampletown

RW 1-52-1 (Rescue)

RSU_Sampletown

Keyword

Required Units

Trash Can Fire

B_*

Area

Responsible Units

Sampletown (Downtown)

LZ_Sampletown, RSU_Sampletown, B_Sampletown

  • Operation: Trash can fire in Sampletown (Downtown)

  • Result: HLF 1-48-1

  • Explanation: Only HLF 1-48-1 belongs to the unit B_Sampletown, which is requested by the keyword.

Example 4: Multiple necessary Units

Configuration:

Resource

Associated with Unit

HLF 1-48-1 (Engine)

B_Sampletown

RW 1-52-1 (Rescue)

TH_Sampletown

Keyword

Required Units

Gas Leak

B_, TH_

Area

Responsible Units

Sampletown (Downtown)

B_Sampletown, TH_Sampletown

  • Operation: Gas leak in Sampletown (Downtown)

  • Result: HLF 1-48-1, RW 1-52-1

  • Explanation: The keyword requests two different units (B_* and TH_*), both are responsible for the area.

Example 5: BF and FF combined

Configuration:

Resource

Associated with Unit

ELW 1-11-1 (Career Command)

LZ_BF_Sampletown

HLF 1-48-1 (Career Engine)

LZ_BF_Sampletown

DLK 1-30-1 (Career Ladder)

LZ_BF_Sampletown

HLF 1-48-2 (Career Engine)

LZ_BF_Sampletown

TLF 2-24-1 (Volunteer Tanker)

LZ_FF_Sampletown

LF 2-46-1 (Volunteer Engine)

LZ_FF_Sampletown

Keyword

Required Units

Commercial Fire

LZ_BF_, LZ_FF_

Area

Responsible Units

Sampletown (Downtown)

LZ_BF_Sampletown, LZ_FF_Sampletown

  • Operation: Commercial fire in Sampletown (Downtown)

  • Result: ELW 1-11-1, HLF 1-48-1, DLK 1-30-1, HLF 1-48-2, TLF 2-24-1, LF 2-46-1

  • Explanation: The keyword requests both LZ_BF_* and LZ_FF_*. Both units are dispatched.


Example 6: Alternatives in case of Unavailability

Configuration:

Resource

Associated with Unit

Status

Career Units (Station 1)

LZ_BF_Sampletown

4 (On Scene)

Volunteer Units (Station 2)

LZ_FF_Sampletown

2 (Available)

Keyword

Required Units

Room Fire

LZ_*

Area

Responsible Units

Sampletown (Downtown)

(LZ_BF_Sampletown; LZ_FF_Sampletown)

  • Operation: Room fire in Sampletown (Downtown), Career Units busy

  • Result: TLF 2-24-1, LF 2-46-1 (Units of LZ_FF_Sampletown)

  • Explanation:

    • The two units are placed in parentheses and separated by a semicolon.

    • Priority follows the reading direction from left to right.

    • Since LZ_BF_Sampletown is unavailable, the suggestion falls back to LZ_FF_Sampletown.

Extended Variant: With the configuration (LZ_BF_Sampletown; LZ_FF_Sampletown, LZ_FF_Neighbor), in the event that LZ_BF_Sampletown is unavailable, both units LZ_FF_Sampletown and LZ_FF_Neighbor would be suggested (Comma = AND).

Note: Area Responsibility is "blind" to the actual load of the vehicles. It trusts that a unit tagged as Engine fulfills the functions of an Engine. Quantity verification and technical validation take place in the subsequent Level 2 (Equipment Requirements).

Did this answer your question?