...
- Go to 'Admin > Imports / Exports > Export Files'.
- Select the 'E911' Record from the Grid, then click the
button. - Check the 'Test Mode' checkbox. It is very important to make sure to run the Report manually in 'Test Mode'.
While in this mode, the Report will not be updated within PCR-360's memory but updates will be visible in the output and will be generated quicker than when running normallyTest Mode the exact same queries are run, but nothing is committed.
- Click either of the two Export File Buttons.
- The
button will display the Report in the browser. - The
button will download the Report to your machine.
- The
...
The CUSTOMER_NAME field will be populated with the Service Owner. This can be either a person or a department. The report does not differentiate between the two owner types and will simply display the name of the owner.
USE_E911_NENA2_FIELDS
The E911 field will only appear on the Location Address form if the USE_E911_NENA2_FIELDS constant is enabled. The Service will not appear in the E911 report if the Street Name or House Number is blank for the Location when USE_E911_NENA2_FIELDS is active.
If USE_E911_NENA2_FIELDS is NOT active, then the E911 report will attempt to parse these fields from the address. The address will be skipped if the Street Address does not have a House Number and Street Name.
The following values will be converted during this process
- 'North' => 'N',
- 'South' => 'S',
- 'East' => 'E',
- 'West' => 'W',
- 'Avenue' => 'AVE',
- 'Drive' => 'DR',
- 'Plaza' => 'PL',
- 'Street' => 'ST'
For more information on the USE_E911_NENA2_FIELDS parameter, please see the Misc Parameter page.
Location
The Location field is populated by the locations hierarchy. Here are a few examples:
...
- 1234 Building Name > Floor 2 > Room 12 would be populated as 1234 Building Name Room 12
Custom Location Formatting
Custom Location Formatting uses REGEX to reformat specific Location Types while building the Enhanced 911 reports. It is configured by adding entries into the pcr360.ini file.
The settings are in the following format:
e911.type.<LOCATION_TYPE>.match = <REGEX_STRING>
e911.type.<<LOCATION_TYPE>.replace = '$1'
LOCATION_TYPE refers to any of the following:
- The List RECID of a Location Type, example: 178
- The List Code (in all caps) of a Location Type, example: FLOOR
- BUILDING_NUMBER, the building number of an address
- BUILDING_NAME, the building name of an address
- SERVICE_LOCATION, the Service Location of the Service
The REGEX strings use a standard REGEX find and replace format: https://regex101.com/.
| Expand | ||
|---|---|---|
| ||
Example Usage Let's say you have a Location like this: 1234 Example Building > 2 > 12 The Location Type for each part is BUILDING_NUMBER BUILDING_NAME > FLOOR > ROOM If the Example INI settings below are used on the e911 report, the location will be formatted as: #1234 > Flr: 2 > Rm: 12 # Floors # Example: A location type Floor is named "123" # It would appear on the report as "Flr: 123" # The config option uses the name (all in caps) of the location type e911.type.FLOOR.match = '/(.*)/' e911.type.FLOOR.replace = 'Flr: $1' # Rooms # Prepend "Rm: " to all room numbers # The config option can also use the list ID of the location type e911.type.178.match = '/(.*)/' e911.type.178.replace = 'Rm: $1' # Buildings # Clear the building names e911.type.BUILDING.match = '/(.*)/' e911.type.BUILDING.replace = '' # Building Numbers # prepend the number symbol to all Building Numbers e911.type.BUILDING_NUMBER.match = '/(.*)/' e911.type.BUILDING_NUMBER.replace = '#$1' |
...