The area management now supports adding according to different area classes (large, medium, and small administrative areas). Additionally, grouping options were inserted. This allows areas that are split into too many postal code areas to be merged into one area to simplify administration. SIMD4-463, SIMD4-453

The window for incident processing was optimized for a more compact representation/view. Functionalities were not changed. This allows the window to be scaled smaller. SIMD4-313, SIMD4-451

A uniform terminus for the suggestion logic at ResQueServe® was introduced. With this, more exact instructions were manufactured.

Different bug fixes in the suggestion logic. SIMD4-299, SIMD4-401

The GIS was not correctly cleaned of finished incidents. SIMD4-417

The GIS did not use a user-defined Tile-Map-Layer. SIMD4-223

Changes to the incident list like sorting or number of entries are now saved and automatically loaded upon rejoining. This now also affects the GIS settings. SIMD4-222

The automatic tab "Active" is displayed again on the status page. SIMD4-335

Contrast problem with search results of the POI administration. SIMD4-479

Reaction time after alerting in Status 1 and Status 8 were improved and adjusted to a realistic measure. SIMD4-419, SIMD4-438

The status which should be used by resources upon arrival at the staging area can be determined in the administration area under General (normally Status 1).

Stuck vehicles at an incident site. SIMD4-473, SIMD4-492

Follow-up messages in radio communication were communicated directly without a request to speak. SIMD4-452

Command services of the emergency medical service leave the incident site upon arrival or too early. SIMD4-321

Triggered fire alarm systems or emergency scenarios are generated at addresses without object affiliation. This leads to, for example, boat accidents in inner-city areas. SIMD4-276, SIMD4-400

Rescue units report the arrival of all forces in the staging area again during an incident while in the staging area. SIMD4-286