Responder supports the concept of regions—also called areas of responsibility, districts, zones, etc. Using model names (see the Configuration Guide) your administrator can break regions into three levels (or groups) for display and reporting purposes. In the example below, one region layer is denoted by the names (e.g., Benzie, Gladwin). Each named polygon represents a region. This is the smallest level of region. All other levels are groupings of these regions.
These smaller regions can be grouped into another level of regions (indicated by color in the example). For example, the Gladwin and Bay City regions form one larger region indicated with light green. The last level of regions in this example encompasses all visible regions in the sample. This can be an entire zip code or city. This last level of regions can encompass all regions (as in the example) or a different collection of regions than the original grouping.
The Dispatchers flyout tab displays all users that have access to the currently displayed regions. It also displays any incidents assigned to those dispatchers. Use this tab to view the incidents assigned to each dispatcher. If a dispatcher is missing, that person may not have access to the region(s) being viewed. Click Show All Regions to display all dispatchers in this window.
The Selected Regions tab displays all regions currently selected for viewing in Responder Explorer. Modify the regions selected for viewing using the Select Regions tool.
Regions and Prediction: If Prediction causes an incident to roll up to a device in a different region, in some circumstances a message on the desktop tray notifies the user that the incident is moving to a new region. For this to occur, the incident must be owned by the current user, and it must have a crew assigned. Click the X on this message to close it.
The Responder web browser provides means to assign dispatchers to specific regions. Restoration Estimates allows you to assign an estimated time of restoration for incidents in a particular region or on a specific feeder. This functionality is meant to be used primarily in a storm situation when an entire region or feeder is out due to down trees, etc.
Responder Web Browser: