18
Request for Proposal – NENA Enhanced PSAP Registry and Census Request for Proposal (RFP) NENA Enhanced PSAP Registry and Census (EPRC)
Request for Proposal – NENA Enhanced PSAP Registry and Census
Request for Proposal (RFP)
NENA Enhanced PSAP Registry and Census (EPRC)
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 1 of 16 | TOC
I. Background 1
The National Emergency Number Association (NENA) is a standards development organization which 2
issues industry standards covering multiple aspects of emergency services. NENA also provides multiple 3
services to support 9-1-1 service operations. 4
One of those services is a database that contains critical information about US Public Safety Answering 5
Points (PSAPs, also called 9-1-1 centers). The primary purpose of the database is to permit PSAPs and 6
other users to obtain contact information about other/distant PSAPs, primarily during times of emergency 7
but also for administrative purposes. This database is currently limited to a single dimension search 8
capability across all fields in the database, but does not support the addition of multiple search criteria, 9
additional data fields, or the introduction of PSAP coverage area boundary polygons into the database. 10
This Request for Proposal (RFP) is being issued to collect information from interested industry 11
stakeholders for the purposes of helping NENA determine: 12
• What processes would be required to evolve the NENA PSAP Registry from its current structure 13
into a robust, geographic polygon-based search and data tool with modern, user friendly 14
interfaces and the capacity for expansion to include additional data fields, reporting mechanisms, 15
and interaction tools as required. This tool would be known as the NENA Enhanced PSAP 16
Registry and Census (EPRC). 17
• The basic structure, format, and organization of the proposed EPRC tool with regard to: 18
interfaces, hosting, management, and maintenance. 19
• The structure of and costs associated with the proposed solutions—both on an initial (set-up) 20
basis and on an ongoing (annual) basis. 21
• The timeline required to complete this effort—including phases, milestones, and benchmarks 22
that will support both intermediate project accomplishments and full-project roll-out. 23
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 2 of 16 | TOC
Table of Contents 24
I. Background 1 25
II. Purpose / Introduction / Objective 3 26
A. Purpose 3 27
B. Introduction 3 28
C. Objective 4 29
II. Instructions to respondents 4 30
A. Timeline 4 31
B. Point of Contact 5 32
C. Response Instructions 5 33
III. General Respondent Questions 5 34
A. Respondent Contact and General Information 5 35
B. Respondent Qualifications 5 36
C. Operational Model (After Initial Proposal) 6 37
IV. RFP Terms and Conditions 9 38
Attachment A: NENA EPRC Current and Proposed Data Fields 11 39
Criteria for Report Types 13 40
Attachment B: NENA EPRC Optional Features 11 41
42
43
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 3 of 16 | TOC
II. Purpose / Introduction / Objective 44
A. Purpose 45
The purpose of this Request for Proposal (RFP) is to solicit information from potential vendors able to 46
support the NENA Enhanced PSAP Registry and Census (EPRC). This will aid NENA in the process of 47
both program establishment and vendor selection. 48
NENA intends to gather information about vendor capabilities, approach, and experience relevant to 49
supporting the EPRC. Expected responses and the ground rules for this RFP are more fully described 50
below. 51
All vendors with relevant product offerings are strongly encouraged to respond to this RFP. 52
Respondents will receive direct notification from NENA of addenda or clarifications to this RFP, 53
or for the distribution of future solicitations, as they are published. 54
Respondents are encouraged to provide answers to any or all questions in this RFP so that NENA 55
may effectively evaluate all responses. 56
B. Introduction 57
Today’s 9-1-1 systems are limited in their ability to properly route wireless 9-1-1 calls, handle “out of area” 58
9-1-1 calls, and support notifications to PSAPs made from locations and/or companies located outside of 59
their borders. In each of these cases, a tool is needed to ensure that PSAPs or organizations are able to 60
direct 9-1-1 calls to the proper PSAP for the emergency, no matter where that emergency may be. 61
In addition, the 9-1-1 industry is hampered by a lack of an effective reporting and tracking tool for basic 62
PSAP related information that is important for matters of funding, statistics, reporting and trend 63
awareness. The absence of such information has hampered efforts to reclassify telecommunicators, 64
guide policy considerations like funding needs, and fully report on the challenges and opportunities facing 65
the US 9-1-1 system. 66
The NENA PSAP Registry was originally developed as a tool to assist the “out of area challenge.” By 67
maintaining a record of the 24x7 10-digit emergency phone lines for each of the PSAPs in the United 68
States, it was possible for any agency processing a call that was outside of their service area to “look-69
up” the number of the correct PSAP and either transfer the caller to the proper PSAP or relay the required 70
information. The Registry can be of particular utility for those PSAPs with a high volume of misrouted 71
calls from mobile phones. 72
Modern technology has brought about two more examples of why this registry tool is essential for Public 73
Safety. Many forms of “non-traditional” PSAPs have developed to handle specialized situations, ranging 74
from people in mental health crisis to human trafficking. These centers are often based in a single physical 75
location and occasionally become aware of events that require an emergency notification to a traditional 76
9-1-1 center. They must obtain the contact information for a possibly much distant PSAP and make a 77
voice notification to generate a law enforcement, medical, or fire department response. 78
The most dramatic example are the instances of a friend, family member, or other contact becoming 79
aware of a possible emergency involving a distant person. In these cases, the 9-1-1 call reaches the 80
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 4 of 16 | TOC
caller’s local PSAP, again far away from the actual location of the potential emergency. Responsibility 81
falls to the center that is reached to determine where the call is to be routed—even if the caller is in Miami 82
and the emergency is in Seattle. 83
The evolution toward Next Generation 9-1-1 also demands an EPRC. The increasingly connected and 84
dependent nature of 9-1-1 service systems means that agencies must have awareness of the boundaries, 85
organization, and contact information for a far greater number of PSAPs than in the past. Providing this 86
information in a more seamless and integrated manner through the EPRC will contribute to the 87
effectiveness of the nation’s entire 9-1-1 ecosystem. 88
Finally, there is a need to track additional data related to the PSAPs which is currently not maintained in 89
a single location. Beyond the operational capabilities of the EPRC, the intent is to add various data fields 90
that will be populated based on either survey result or user input. 91
Together, the ability to provide greater operational support through PSAP boundary polygons and more 92
significant supporting data will transform the NENA PSAP Registry into an essential tool for public safety 93
and a foundation of every PSAP’s toolkit. It will also support the evolution of 9-1-1, act as a tool for federal 94
and state advocacy, and myriad other projects and enhancements. 95
C. Objective 96
The NENA EPRC RFP Process will provide NENA with the necessary information to identify a vendor 97
partner to support the modernization of the PSAP Registry and all associated work. The results of this 98
RFP will also provide a framework for ongoing maintenance and support efforts, as well as guide the 99
update and revision process associated with the additional data that will be collected and maintained. 100
Timeline for the project and associated benchmarks, which will be developed in collaboration with a 101
vendor, will be essential elements of a winning proposal. This timeline should include 30-day reporting 102
periods, with clear objectives for each of the periods. 103
NENA's vision is that the RFP will result in a contract being awarded that supports the modernization of 104
the PSAP Registry and a minimum of a three-year period of ongoing hosting, maintenance, and related 105
tasks. 106
II. Instructions to respondents 107
A. Timeline 108
(calendar days unless otherwise specified) 109
T+0 days RFP published 110
T+21 days Due date for submission of Respondent Proposal 111
T+35 days Due date for NENA’s answers to Initial Respondents 112
T+63 days Due date for any requested follow-up information to NENA 113
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 5 of 16 | TOC
B. Point of Contact 114
The single point of contact for this RFP and the delivery point for responses and 115
correspondence is [email protected]. 116
C. Response Instructions 117
For the sections below, Respondents should answer the following questions in their response 118
and submit their responses to the online form at 119
https://911nena911.wufoo.com/forms/z76rs9n1q3ls38/. Additional submittals beyond the 120
limitations of the online form should be uploaded as attachments. 121
In the event of difficulty with the online submission process, Respondents should email 122
the Point of Contact. 123
III. General Respondent Questions 124
A. Respondent Contact and General Information 125
Respondents are asked to provide the following information where applicable: 126
1. Legal Name of the Entity 127
2. Type of Entity (Corporation, Academic, Foundation, etc.) 128
3. Name, Title and Contact Information of Primary Contact 129
4. Entity headquarters address 130
5. Location proposed for EPRC system server(s) 131
6. Brief History of the Entity, including date established (2 pages maximum) 132
7. Any brochures / literature, if relevant (10 pages maximum) 133
8. Any existing White Papers or publications that provide information relevant to this RFP 134
B. Respondent Qualifications 135
1. Describe Respondent’s capability to develop, administer and support a PSAP Registry 136
Product that will feature the geographic boundaries (polygons) of all US PSAPs, the 137
geographic boundaries (polygons) of other emergency and public safety related entities as 138
appropriate (e.g., Poison Control Centers, US Coast Guard Sector Centers, Utility 139
Companies, etc); capacity to add further relevant data fields; an interface that will permit 140
users to access the data; a permissions process that will support multiple types of users 141
ranging from the general public to system administrators, and the hosting and updating 142
services and processes associated with the registry. 143
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 6 of 16 | TOC
2. Respondent should describe a proposed process to obtain the information cited in the 144
previous question if they do not currently possess the required items. Please describe 145
how/if you would leverage the existing NENA PSAP Registry and other tools to acquire 146
the shape/boundary files, PSAP contact information, and other required information to 147
complete the database project. 148
3. Describe how respondent would assign staff/personnel to support the project and any 149
related costs. Respondent should have resources on staff with extensive knowledge of the 150
process and service that will be provided. 151
4. Describe respondent’s experience developing and providing similar geographic database 152
and reporting tools. 153
5. Respondent should describe the ongoing relationship between NENA and the respondent, 154
the expected updating and review process; the data validation process; and what effort 155
they would undertake to promote this product (if any). 156
6. Respondent should describe any plans or intentions to utilize the data obtained during the 157
course of this project for other projects or efforts separate from the NENA PSAP Registry 158
Effort and the financial implications of such other effort. (i.e., will a vendor not possessing 159
shape files propose utilizing shape files obtained through work with NENA for other 160
purposes). 161
7. Respondent should specifically identify the “owner” of the data going forward and describe 162
the process of data ownership transfer should the contract be terminated. 163
C. Operational Model (After Initial Proposal) 164
After the initial proposal period, NENA will contact Respondents who meet the initial qualifying criteria to 165
submit a demonstration of the proposed EPRC. This demonstration should be online and should display, 166
as closely as practical, what the end state web interface would look like for users, the interaction tool, 167
and the results of several solutions: 168
a) A 9-1-1 dispatcher searches for the primary 9-1-1 PSAP to serve the address 200 North 169
High Street, Columbus, Ohio. 170
b) A 9-1-1 Dispatcher searches for the appropriate PSAP to contact for a Medical Emergency 171
occurring in New York City. 172
c) A Suicide Crisis Text Line dispatcher searches for the community name “Nokomis” in Florida 173
as part of the attempt to track down the location of a teen who is threatening self-harm. 174
d) A 9-1-1 center in St. Louis, Missouri is attempting to search for the phone number of the 175
correct US Coast Guard Sector for a boat fire in the Mississippi River near the Gateway 176
Arch. 177
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 7 of 16 | TOC
e) A NENA staff employee is going to enter the results of a survey returned by mail from a 178
PSAP containing responses to the following data requests: 179
1. PSAP Name 180
2. PSAP County 181
3. PSAP County FIPS Code 182
4. PSAP Street Location 1 183
5. PSAP Street Location 2 184
6. PSAP Community 185
7. PSAP State 186
8. PSAP Zip Code 187
9. PSAP Zip Code Extension 188
10. PSAP 24 Hour Phone #1 189
11. PSAP 24 Hour Phone #2 190
12. Fax 191
13. PSAP Registry Contact Name 192
14. PSAP Registry Contact Title 193
15. Organization Associated With 194
16. PSAP Registry Contact Telephone Number 195
17. PSAP Registry Contact E-Mail Address 196
18. Wireline Type (primary or secondary) 197
19. Wireless Type (primary or secondary) 198
20. Service Communities Supported by this PSAP 199
21. PSAP Service Area Description 200
22. Governing Authority 201
23. Record Verification Date 202
24. Spatial Shape File for the PSAP (traditional service Area) 203
25. Spatial Shape File for the PSAP (wireless service area) 204
26. Spatial Shape Files for the PSAP service area by discipline 205
27. 9-1-1 Authority Contact Information 206
a. Name 207
b. Title 208
c. Mobile Number 209
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 8 of 16 | TOC
d. E-Mail Address 210
28. PSAP Outage Notification 211
a. Generic Email Address 212
b. 24/7/365 contact phone number 213
29. Shape Files of Non-PSAP Service Areas 214
a. US Coast Guard Sector offices 215
b. Poison Control Centers 216
c. Rail Control/Dispatch Centers 217
d. Pipeline Control Centers 218
e. HazMat Information Centers 219
f. Utility Emergency Notification Centers 220
30. PSAP Contact Phone Number—Non-Emergency 221
31. PSAP Supervisors Phone Number (24/7/365) 222
32. PSAP Contact Phone Number (Administrative Offices) 223
33. PSAP Mailing Address 224
34. PSAP Secondary Point of Contact (name, phone, mailing, email) 225
35. Types of services provided? 226
36. Agencies for whom those services are provided 227
37. Level of NG9-1-1 Progress (drop-down menu) 228
38. ESINet Relationship 229
39. Text Message Capability (SMS or RTT) 230
40. I-PAWS Capability & ID with FEMA 231
41. Approximate Number of personnel employed by agency (total) 232
42. Approximate Number of Personnel on Shift 233
43. Number of Physical Positions/Workstations 234
44. Employee Shift Schedule (drop down menu) 235
45. Approximate Hours of New Hire Training 236
46. Approximate Hours of Annual Refresh Training 237
47. Call answer protocols utilized (and if so-what vendor) 238
48. EMD Use & Certification? 239
49. Agency Certification? (drop down, button menu), e.g. CALEA, APCO P33 240
50. TERT Participant? 241
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 9 of 16 | TOC
51. Does the Agency Utilize tactical Dispatchers? 242
52. Estimated Number of 9-1-1 calls received per month (by source: Wireless, Wireline, 243
VOIP) 244
53. Estimated number of 10-digit calls received per month 245
54. Estimated number of alarm calls received per month 246
55. Estimated number of non-emergency calls received per month; 247
56. Busy Hour over the last year? (the time during a 24-hour period that received the most 248
calls on average) 249
57. Primary Back-Up PSAP Location 250
58. Primary Back-Up Agency (if agency is not functional) 251
252
Additionally, respondents should address the security of the EPRC and the processes they have 253
undertaken to ensure that information cannot be captured, corrupted, modified, or removed. 254
IV. RFP Terms and Conditions 255
A. THIS IS A REQUEST FOR PROPOSAL (RFP). The RFP is issued for information and planning 256
purposes. In evaluating the responses, NENA may notify the Respondents that it intends to enter 257
into a contractual relationship with the respondent it deems most in compliance with the needs of 258
NENA and the project as defined. 259
No Compensation. NENA will not provide compensation to any respondent to this RFP for any 260
expenses incurred by respondent for response preparation. Respondent submits its response at its 261
own risk and expense. All responses to this RFP and any supporting documentation will become 262
the property of NENA. 263
Public Information Act / Disclosure of Information. NENA considers all information, documentation 264
and other materials requested to be submitted in response to this RFP, to be of a non-confidential 265
and/or non-proprietary nature unless otherwise marked. 266
NENA may be required to provide access to certain submitted document in accordance with the 267
provisions of an Open Records Act. Respondents must clearly mark any portion of their response 268
document as proprietary and/or confidential. 269
Proprietary information, if any, should be minimized, and MUST BE CLEARLY MARKED. 270
Please segregate proprietary information from non-proprietary information. Please be advised that all 271
submissions become NENA property and will not be returned. By submitting a Response, 272
Request for Proposal – NENA Enhanced PSAP Registry and Census
May 22, 2018 | page 10 of 16 | TOC
respondents acknowledge and agree that NENA shall have no liability to the respondents or to any 273
other person or entity for disclosing information. 274
B. EVALUATION – This evaluation will be reviewed and evaluated by a designated team of NENA 275
staff and experts. 276
Attachment A: NENA EPRC Required and Optional Features
May 22, 2018 | page 11 of 16 | TOC
Attachment A: NENA EPRC Required and Optional Features
I. Required Features
A. Data Fields and Reports
All data fields listed in Attachment B must be included in the EPRC. The EPRC must have the capacity to produce
reports which include the following for each PSAP and its associated 9-1-1 Authority, as well as the fields
indicated in the “Report Type” columns of Attachment B (i.e. ”Online,” “Files,” Outage Reports,”
“Administrative”):
1) name
2) street address
3) contact email address
4) contact telephone number
5) PSAP ID
NENA will eventually require Attachment B items 41-58 to be placed into one of the four reports mentioned
above, but decisions as to their specific placement have not concluded.
B. Common Login Credentials
The EPRC should allow groups of users to use common IDs and passwords, rather than individual passwords, or
offer an alternative solution that reduces the burden on PSAP Administrators in provisioning and de-provisioning
access credentials to the EPRC. Respondents should also propose a methodology for maintaining current records
of users and allowing for the efficient de-provisioning of access to the EPRC.
The EPRC should also be able to produce a User Maintenance Report that allows Administrators to verify valid
users and identify former users who need to be de-provisioned.
C. Data Verification and Refresh Reports
The EPRC should have the capability to produce reports showing when the individual PSAP records were last
verified in order to facilitate the refresh of PSAP information.
D. EPRC Usage Reports
The EPRC should have the capability to produce reports showing the frequency of access by PSAPs, commercial
call centers, and across selected geographic areas (e.g. state-by-state).
Attachment A: NENA EPRC Required and Optional Features
May 22, 2018 | page 12 of 16 | TOC
II. Optional Features
A. Manual Routing
The EPRC should have the capability to access reports tallying instances of Manual Routing queries.
B. Geographic Reporting
The ERPC should allow users to access reports arranged by geographic boundaries (i.e. geofencing). It should
also allow reports to be generated based on state name, county name, or FIPS code.
C. Secure API
The EPRC should have the capability to access reports through an Application Programming Interface (API).
Attachment B: NENA EPRC Optional Features
May 22, 2018 | page 13 of 16 | TOC
Attachment B: NENA EPRC Current and Proposed Data Fields
Criteria for Report Types
Online. An online search for a PSAP that meets specific criteria in various fields of the database. Currently, all fields in the database are accessible, with some fuzzy logic on spellings. A major addition is the ability to search by Lat/Long data to find a PSAP shape file and the associated PSAP information.
Monthly Files. Four files in EXCEL form are produced monthly, by Western, Southeast, North Central, and Northeast regions for specific states for each. Potentially, a similar report for Canada may be a future option.
Outage reports. This portion of the project relates to carriers, 9-1-1 System Service Providers, and others being able to acquire PSAP and 9-1-1 Authority contact info to support outage and service impairment notifications to PSAPs and 9-1-1 Authorities. Separate email address and telephone numbers that are not associated with individuals require separate fields. This part is still in question and negotiation with the carriers and an ATIS committee, so this may or may not be a requirement for the PSAP Registry.
Administrative. A specific report for data records administration is needed, and an EXCEL spreadsheet of selected data fields that can be requested as needed, and then manipulated externally.
Item
Existing or
New Data Item/Field Online Files
Outage Reports
Admin Notes
1. Existing PSAP Name X X X X Functional Data
2. Existing PSAP County X X X X Functional Data
3. Existing PSAP County FIPS Code X X X X Functional Data
4. Existing PSAP Street Location 1 X X X Functional Data
5. Existing PSAP Street Location 2 X X X Functional Data
6. Existing PSAP Community X X X X Functional Data
7. Existing PSAP State X X X X Functional Data
8. Existing PSAP Zip Code X X X ? Functional Data
9. Existing PSAP Zip Code Extension X X X ? Functional Data
10. Existing PSAP 24 Hour Phone #1 X X ? X Functional Data
Attachment B: NENA EPRC Optional Features
May 22, 2018 | page 14 of 16 | TOC
Item
Existing or
New Data Item/Field Online Files
Outage Reports
Admin Notes
11. Existing PSAP 24 Hour Phone #2 X X ? X Functional Data
12. Existing Fax X X Functional Data
13. Existing PSAP Registry Contact Name X ? X Functional Data
14. Existing PSAP Registry Contact Title X ? X Functional Data
15. Existing Organization Associated With X X X X Functional Data
16. Existing PSAP Registry Contact Telephone Number
X ? X Functional Data
17. Existing PSAP Registry Contact E-Mail Address
X ? X Functional Data
18. Existing Wireline Type (primary or secondary)
X X X X Functional Data
19. Existing Wireless Type (primary or secondary)
X X X X Functional Data
20. Existing Service Communities Supported by this PSAP
X X X X Functional Data
21. Existing PSAP Service Area Description X X X X Functional Data
22. Existing Governing Authority Functional Data
23. NEW Record Verification Date X X X Functional
24. NEW Spatial Shape File for the PSAP (traditional service Area)
X X X Indicate populated
Functional Data
25. NEW Spatial Shape File for the PSAP (wireless service area)
X X X Indicate populated
Functional Data
26. NEW Spatial Shape Files for the PSAP service area by discipline
? ? ? ? Functional Data
27. NEW 9-1-1 Authority Contact Information Name Title Mobile Number E-Mail Address
X X X Functional Data
Attachment B: NENA EPRC Optional Features
May 22, 2018 | page 15 of 16 | TOC
Item
Existing or
New Data Item/Field Online Files
Outage Reports
Admin Notes
28. NEW PSAP Outage Notification Generic Email Address 24/7/365 contact phone number
X X X Functional Data
29. NEW Shape Files of Non-PSAP Service Areas
• US Coast Guard Sector offices
• Poison Control Centers
• Rail Control/Dispatch Centers
• Pipeline Control Centers
• HazMat Information Centers
• Utility Emergency Notification Centers
X
X Indicate populated
Functional Data
(This list is not complete
and will be developed in consultation with vendor)
30. NEW PSAP Contact Phone Number—Non-Emergency
X X X Informational
31. NEW PSAP Supervisors Phone Number (24/7/365)
X X X Informational
32. NEW PSAP Contact Phone Number (Administrative Offices)
X X X Informational
33. NEW PSAP Mailing Address X X X Information 34. NEW PSAP Secondary Point of
Contact (name, phone, mailing, email)
X X X Information
35. NEW Types of services provided? X X Information/ Functional
36. NEW Agencies for whom those services are provided
X X Information/ Functional
37. NEW Level of NG9-1-1 Progress (drop-down menu)
X Information/ Functional
38. NEW ESINet Relationship—Connection
X Information/ Functional (Will work
with vendor on this item)
39. NEW Text Message Capability (SMS or RTT)
X X Informational/ Functional
Attachment B: NENA EPRC Optional Features
May 22, 2018 | page 16 of 16 | TOC
Item
Existing or
New Data Item/Field Online Files
Outage Reports
Admin Notes
40. NEW I-PAWS Capability & ID with FEMA
X X Informational/ Function
41. NEW Approximate Number of personnel employed by agency (total)
Informational
42. NEW Approximate Number of Personnel on Shift
Informational
43. NEW Number of Physical Positions/Workstations
Informational
44. NEW Shift Schedule (drop down—8,10,12, hybrid)
Informational
45. NEW Approximate Hours of New Hire Training
Informational
46. NEW Approximate Hours of Annual Refresh Training
Informational
47. NEW Call Answer protocols utilized & if so-what vendor?
Informational
48. NEW EMD Use & Certification? Informational
49. NEW Agency Certification? (Drop Down, button menu)—CALEA, APCO P33
Informational
50. NEW TERT Participant? Informational
51. NEW Does the Agency Utilize tactical Dispatchers? (That respond to scene)
Informational
52. NEW Estimated Number of 9-1-1 calls received per month (by source: Wireless, Wireline, VOIP)
Informational
53. NEW Estimated number of 10-digit calls received per month
Informational
54. NEW Estimated number of alarm calls received per month
Informational
55. NEW Estimated number of non-emergency calls received per month;
Informational
56. NEW Busy Hour over the last year? (The time during a 24 hour period that received the most calls on average)
Informational
Attachment B: NENA EPRC Optional Features
May 22, 2018 | page 17 of 16 | TOC
Item
Existing or
New Data Item/Field Online Files
Outage Reports
Admin Notes
57. NEW Primary Back-Up PSAP Location
Informational/ Functional
58. NEW Primary Back-Up Agency (if agency is not functional)
Informational/ Functional
