Update Population Information

The Update Population Information tool ensures that reliability reports and customer information remain accurate. This tool can be run in three different ways: In ArcMap, as a stand-alone executable and from a command prompt. The command prompt version of this tool can be run as a scheduled job.

Configuration

If you plan to use the Update Population Information tool in ArcMap, you do not need to perform this configuration. This is necessary only to use the stand-alone or command line tools.

Browse to and open UpdatePopulationInformation.exe.config. By default, this file is installed here: C:\Program Files(x86)\Miner and Miner\Responder\Server.
Look for the following XML:

	Copy Code
<channels> <channel ref="msmq" ComputerName="ServerName" /> </channels>

Set the ComputerName attribute to the name of the server that hosts the Responder Server.
Save and close UpdatePopulationInformation.exe.config.

ArcMap

Select the Update Population Information button to display the Update Population Information dialog. You may need to add this tool to a toolbar using the Customize menu. Select an option and click Start. During processing, the Start button becomes a Cancel button. You may cancel at any time. Options are discussed below.

Stand-alone Executable

Browse to UpdatePopulationInformation.exe and double-click it. By default, this executable is installed here: C:\Program Files (x86)\Miner and Miner\Responder\Server.

In the Update Population Information window, enter a number to select an option. Options are discussed in the Options section below. You will be prompted when the update is finished. Press any key to close the command prompt window.

Command Line

You may also run this tool from a command prompt. First browse to the install location (by default C:\Program Files (x86)\Miner and Miner\Responder\Server). Enter UpdatePopulationInformation.exe and press Enter. This displays the update options. Enter the number that corresponds to the update option to execute. For example:

You will be prompted when the update is finished. Press any key to close the executable, but keep the command prompt window open.

Alternately, you can specify an option when initially executing the tool. For example:

If you choose this method, you can enter any one of the three options using the following syntax:

ServiceRegions
Counties
Feeders

These options are defined in the Options section below.

Options

Service Regions or Counties: If you have service regions or counties configured, use these options to update the population information. These options determine the region (or county) for each customer load point in the map. The tool then assigns the correct region to the Regions field in the RX_CUSTOMERS table. The time it takes for this tool to execute is proportionate to the number of load points in the map. The more customers, the longer it takes for the tool to complete the spatial query.

Execute the Update Population Information tool with one of the Region options (Service Regions or Counties) when setting up Responder for the first time. Portions of Responder rely on an accurate value in the Regions tool. Leaving this field empty may cause portions of Responder to fail. This tool should also be executed any time the boundaries of regions are moved.
Feeders: The Feeders option does two things: 1) provides a customer count for each feeder and 2) updates the FeederID value on the customer records. This information is used by the Reliability Reports in Archive Explorer. Before running Reliability Reports for the first time, you must execute the Update Population Information tool. This populates a field in the Archive tables with the total number of customers (excluding disconnected customers). You may execute this tool to update the customer count before executing subsequent Reliability Reports.

The Feeders option in the Update Population Information tool should be executed any time new users are added to the database. This ensures that new customer records have a valid FeederID value. If you choose not to run this tool after adding new customers to the database, Responder will populate the Feeder ID field when incidents with those new customers are archived. This will slow performance.