The underlying systems for 911 calls today operate almost exclusively on analog technology, using an architecture of circuits and switches developed when the American Telephone & Telegraph Company was a regulated monopoly providing most of the nation's telephone service. Modern communications innovations such as digitization, packet switching, and Internet Protocol (IP) standards are alien concepts in an outdated system design that, critics maintain, "literally chokes off the use of all but the most rudimentary features of modern end-user devices and stifles the development of more specialized equipment and services." Systems for 911, unable to accommodate the latest advances in telecommunications technology, are increasingly out-dated, costly to maintain, and in danger of failure. Consumer expectations for accurate and timely response to 911 calls are based on the advanced features available on most communications devices, not on the reality of a faltering legacy system. The analog system cannot carry text messages, for example. Calls are delayed or dropped when analog and digital systems do not mesh. Information on the location of the call is lost because the digital details cannot be transmitted by the underlying telecommunications infrastructure or understood by the computers at Public Safety Answering Points (PSAPs). As summarized in a National Emergency Number Association (NENA) report, "Simply put, the 9-1-1 system has not kept up with technology and is badly in need of modernization." There is a general consensus that present and future digital communications for 911 services would be best supported by Next Generation 911 technology (NG9-1-1). The term NG9-1-1 is widely used to refer to the modernization of all parts of the 911 system, including hardware, software, data, and operational policies and procedures, all supported by multi-purpose emergency service networks. These IP-enabled networks rely on the same type of network connections as business and consumer access to the Internet and can share capacity with other users. A broadband connection built to a school, library, or hospital, can also reach a 911 call center. Deploying NG9-1-1 is seen as an integral part of national broadband policy. Network facilities dedicated to 911, or even exclusively to public safety, are not considered cost-effective. Future decisions about the technology, deployment, and funding of NG9-1-1 must therefore take into consideration the opportunities for sharing resources with other broadband initiatives. Implementing NG9-1-1 will require not only the development of an IP-enabled network and systems but will also entail changes in operational procedures, training, funding models, and state—and possibly federal—regulations and laws. The National Emergency Number Association (NENA) began planning for the future of 911 under the banner of NG9-1-1 in 2000. NENA started work on standards development for NG9-1-1 in 2003 and since then has taken the lead in defining, designing, and developing NG9-1-1 systems and solutions in partnership with other associations, as well as representatives from industry, government, and the public safety community. Support for NG9-1-1 now comes from a relatively broad base, including State and local managers for emergency communications and 911. Associations such as NENA, COMCARE, the National Association of Regulatory Utility Commissioners (NARUC), the Association of Public-Safety Communications Officials International, Inc. (APCO), and the National Association of State 911 Administrators (NASNA). Many other international, national, and state and local associations are also actively involved in supporting NG9-1-1. Alliances such as the 911 Alliance, the Alliance for Telecommunications Industry Solutions (ATIS), the Internet Engineering Task Force (IETF), and the E9-1-1 Institute, which provides support to the Congressional E9-1-1 Caucus. Corporations and other commercial organizations serving public safety and emergency communications. The Intelligent Transportation Systems (ITS) Public Safety Program and the National Highway Traffic Safety Administration (NHTSA) within the U.S. Department of Transportation (DOT). Notably, NENA and DOT have partnered to encourage the deployment of NG9-1-1. Among DOT's contributions in support of NG9-1-1 was the funding and supervision of five proof-of-concept pilots to test key components of NG9-1-1 in PSAPs. In addition to the pilots established by DOT, at least six states and the District of Columbia are reported to have IP-based networks for emergency communications that will support NG9-1-1 systems. The emergency communications network being tested is envisioned as IP-based, using standardized protocols, and providing a nationwide overlay of system links that can operate at the national, regional, tribal, state, or local level to best meet the needs of specific circumstances. A network overlay for 911 systems can, for example, facilitate interoperability and system resilience by bringing extra resources to devastated areas where 911 call centers are damaged or overwhelmed with calls. On a daily basis, it can provide foreign language assistance at any time, anywhere. Other benefits include better connections between 911 call centers, emergency responders, and alert and warning systems; more robust capacity; and the flexibility to receive calls for help in any format. This section summarizes how past federal 911 legislative and policy actions have established a base for the transition to IP-enabled systems. Three major laws supporting improvements in the handling of 911 emergency calls have been enacted since 1999. These and other laws support policy objectives and strategies that provide the base upon which future policy might be built. Analyzing the legislation as a continuum, these key goals emerge: equality of service and access to 911; mechanisms to improve funding for PSAPs and monitor collections and disbursements; federal leadership in developing better 911 capabilities; and transition to IP-enabled 911 systems. The major bills enacted into law are The Wireless Communications and Public Safety Act of 1999 ( P.L. 106-81 ), often referred to as the 911 Act. The Ensuring Needed Help Arrives Near Callers Employing 911 Act of 2004 ( P.L. 108-494 ), also titled the ENHANCE 911 Act of 2004. The New and Emerging Technologies 911 Improvement Act of 2008 ( P.L. 110-283 ), also titled the NET 911 Improvement Act of 2008. Provisions in other recently enacted laws have also contributed to the growing base of legislation in support of 911. The 21 st Century Emergency Communications Act, Title VI, Subtitle D, in the Department of Homeland Security Appropriations Act, 2007 ( P.L. 109-295 ) required that PSAPs be included as members of Regional Emergency Communications Coordination Working Groups established by the act. The Homeland Security Appropriations Act, 2007 ( P.L. 109-295 ) required the FCC to prepare a report on state, local, and tribal plans for backup service for 911 and E-911 when PSAPS are disabled. The Deficit Reduction Act ( P.L. 109-171 ), as amended by the Implementing Recommendations of the 9/11 Commission Act of 2007 ( P.L. 110-53 ) and the NET 911 Improvement Act of 2008, provided up to $43.5 million for grants for 911. The Implementing Recommendations of the 9/11 Commission Act of 2007 ( P.L. 110-53 ) included financial support of PSAPs as eligible uses for Urban Area Security Initiative and State Homeland Security Grant programs. The Food, Conservation, and Energy Act of 2008 ( P.L. 110-234 ) included language that authorized loans to improve 911 and other emergency communications capabilities in rural areas. To assist the effort to provide comprehensive 911 services nationwide, Congress in 1999 passed the Wireless Communications and Public Safety Act ( P.L. 106-81 ), often referred to as the 911 Act. This act mandated 911 as the national emergency number and provided for parity of wireless 9-1-1 services with the protections and authorizations already extended to wireline services. Among its provisions, the law required the FCC to work with the states and the many other affected parties to deploy comprehensive wireless enhanced 911 (W-E911) service. Enhanced 911 service provides 911 call centers with Automatic Number Identification (ANI) and Automatic Location Identification (ALI). Most wireline phone services provide ANI/ALI information. The 911 Act set the broad goal of facilitating "the prompt deployment throughout the United States of a seamless, ubiquitous, and reliable end-to-end infrastructure for communications, including wireless communications, to meet the Nation's public safety and other communications needs." The FCC had taken a first step toward adopting rules for wireless enhanced 911 in 1996, citing provisions of the Communications Act as the basis for its action. After Congress passed the 911 Act, the FCC plotted a course for reaching wireless in two phases. For Phase I, the wireless carriers were given a year to prepare for PSAP requests for Automatic Number Identification (ANI) and location-finder capabilities using technology existing at the time. By 2001, for Phase II, the carriers were to have identified and implemented new location-finder technologies (ALI). A 1999 FCC ruling established October 1, 2001, as the deadline for wireless carriers to meet guidelines for connecting 911 calls to PSAPs. Delays and complications in implementing rules for 911 prompted the FCC to commission a study to examine deployment of 911 services in general and the cause of problems with wireless 911 calls in particular. The report—known as the Hatfield Report, from its author, Dale N. Hatfield—was submitted to the FCC on October 15, 2002. Observations in the report that later became the basis for Congressional initiatives included The critical nature of location information in enhanced 911 in supporting first responders in emergencies. The "seriously antiquated" condition of the infrastructure that underlies 911 for both wireline and wireless emergency calls. The need for a national 911 office to act as a "champion" at the federal level. A follow-up study was published in 2007 with support from the 9-1-1 Alliance, an industry group. Congress responded to the issues raised by the 2002 Hatfield Report, the 9/11 Commission, and by others, with the Ensuring Needed Help Arrives Near Callers Employing (ENHANCE) 911 Act of 2004 ( P.L. 108-494 ). The act identified and addressed a number of concerns about the deployment of 911, including compliance, coverage in rural areas, and the use of fees levied by states and localities to help cover the cost of providing 911 services. In response to the Hatfield Report's call for a federal champion, the act created the E-911 Implementation Coordination Office (ICO) to be jointly administered by the National Telecommunications and Information Administration (NTIA) and the NHTSA. Among other responsibilities, the ICO was to oversee a grants program for the "implementation and operation of Phase II E-911 services." Although funds were authorized in the law, no appropriations were forthcoming until a sum was allocated by the Deficit Reduction Act of 2005. In FY2008, DOT budgeted $1.25 million for the operation of the ICO. In the 110 th Congress, both the House and Senate passed bills focused on ensuring access to 911 call centers for users of Voice Over Internet Protocol (VOIP) services, and improving the delivery of 911 services nationwide. These bills became the New and Emerging Technologies (NET) 911 Improvement Act of 2008 ( P.L. 110-283 ). The key provisions of the law are Duty to provide 911 and E-911 as established in the 1999 law extended to include IP-enabled voice services in accordance with existing FCC regulations at the time of passage of the act or as modified in the future. Parity of access to communications networks needed to complete 911 calls. Parity of protection from liability—provided for wireline and wireless carriers—extended to include communications through VOIP providers and other emergency service providers. National plan for migration to an IP-enabled 911 network, developed by the E-911 Implementation Coordination Office. Protection of the rights of states and other political subdivisions to levy fees on 911 services. Requirement that FCC report annually on collection of state fees and other levies on 911 and E-911 services. Prior to the passage of the 911 Act in 1999, the FCC had already established regulations for 911 compliance for a new category of service providers—wireless carriers. Similarly, the FCC had established requirements for VOIP—another new category of service provider—in advance of the passage of the NET 911 Improvement Act of 2008. The act confirmed the FCC's authority to require VOIP service providers to comply with 911 connectivity requirements established for wireline and wireless voice and to include VOIP calls in its regulatory and oversight activities for 911. In accordance with requirements to issue regulations covering parity of access and related technical needs and capabilities for VOIP calls, the FCC issued a Report and Order on October 21, 2008. Among the multiple factors and challenges of implementing NG9-1-1 are the costs of planning, replacing, and upgrading systems, and maintaining and operating these new systems. Policies and legislation intended to improve 911 service may need to address the substantial investments required to provide these improvements, including, for example, financial assistance in acquiring the needed technology. The twin policy goals of quality and equality may have bumped against the limits of the technologies currently in place. Significant new gains in accessibility and level of service appear to depend on implementing new technologies that are not supported by the current network architecture. An analysis of cost, value, and risk prepared for DOT, by the consulting firm Booz Allen Hamilton, found that capital and operating costs for improving the existing 911 system would be comparable to the cost of migrating to NG9-1-1 under several scenarios. Furthermore, several trends were identified that would provide additional value, primarily NG9-1-1 provides greater opportunities for cost savings and increased operational efficiencies than the current 911 environment. NG9-1-1 has greater potential to meet the public's expectations for accessibility than the current 911 environment. NG9-1-1 has greater scalability and flexibility than the current 911 environment. NG9-1-1 has greater potential to increase public and responder safety through inter-connectivity and interoperability than the current 911 environment. The costs to improve 911 through investments in infrastructure can be categorized by several major and distinct functions of 911. For the purposes of this analysis, four cost centers and typical sources of funding are summarized below. These are: devices, local networks, call centers, and interfaces with first responders. The cost of developing cell phones and other wireless devices that comply with FCC requirements for caller information for 911 calls are borne by the communications service providers and their suppliers, and by their customers. Some programs, primarily state and local, offer assistance to consumers to help cover the costs of owning and operating a wireless device. To accommodate the needs of enhanced 911, local networks that provide routers and other infrastructure invest in upgrades to their facilities. Expenditures by these networks for investments to route 911 calls may be reimbursed through a state's 911 fund or may be passed on to the PSAPs that purchase access to the lines. Charges to PSAPs for communications services tend to rise as more features are added by their local exchange. In some areas of the country there is little competitive pressure to upgrade these links; the lack of access to an up-to-date infrastructure is one reason why some areas of the country do not have enhanced 911 or even basic 911 services. The American Recovery and Reinvestment Act of 2009 (ARRA, P.L. 111-5 ) provided for grants for investments in broadband infrastructure. Public safety agencies are included under the act as potential beneficiaries of funding. The infusion of grant money to build broadband and IP-enabled networks will help to expand the potential reach of NG9-1-1. ARRA did not, however, address the long-term funding needs to develop and maintain a national NG9-1-1 system. The FCC's National Broadband Plan (also a requirement of the ARRA) did address in part the question of upgrading local networks to handle broadband transmission and of funding the deployment of broadband and NG9-1-1, as noted below, "Creating the Base for Change." To accommodate the information delivered through enhanced 911, PSAPs are required to invest in call-processing equipment, computers, databases, and other equipment. The capital for these investments may come from 911 or E-911 fees paid by subscribers into state 911 funds; the funds are also used for operating costs. State grants and local fund-raising initiatives are other sources for capital investment and operating costs. The final step in processing a 911 call is to relay information to emergency responders. After the point of interface into the local first responder network, the effectiveness of the 911 system depends on the capacity of the response network. The emergency communications networks for public safety are also often constrained by the capabilities of old equipment as well as other operational limitations, such as insufficient radio frequency spectrum and lack of communications interoperability among different first responder groups. The upgrading of these networks are often considered by state and local policy makers as separate from improvements in 911 systems although some states have used 911 funds to help pay for public safety communications networks. The federal grant program administered by the ICO awarded over $40 million in matching grants on September 25, 2009. Grants were available to all states, Washington, DC, Puerto Rico, and the U.S. Territories; however, not all states met eligibility requirements and some states chose not to apply. States receiving funds must use them within three years. Twenty-eight states, Puerto Rico, and American Samoa received grants. Grant funds may be used for purchases of hardware and software for enhanced 911 and IP-enabled systems, as well as training in connection with these investments, as identified in each plan submitted by a State. Grant funds may also be used to acquire alerting systems that can send warning messages to wireless devices. Through the laws that it has enacted, Congress has established the principle that 911 calls should provide the same level of information and responsiveness no matter what the communications device, the location of the call, or the physical abilities of the caller. Congressional actions and FCC regulations have sought to expand the capacity of the existing 911 infrastructure to accommodate more types of devices, to improve caller location information, to provide wireless support in more areas—with more precision—and to accommodate persons with disabilities. Private and public sector investments in IP-enabled systems support the twin goals of equality and quality. Only a digitized system with seamless IP-based connectivity can fully support the needs of groups that are currently poorly served by 911 systems, including those with disabilities, residents and travelers in rural areas, and workers and residents in high rise buildings. The current analog system, for example, can only support text messages to 911 in work-around arrangements; yet, text messaging is ideal for people with certain types of disabilities and many consider it to be a more viable means of communication than voice in times of high demand and widespread service outages, situations that often follow a disaster. Better information on the source of a call, made possible by IP technologies, might be a boon for rural and urban areas, where different technological problems lead to the same consequence: inadequate location identification for incoming 911 calls. The NET 911 Improvement Act of 2008 required the ICO to "develop and report to Congress on a national plan for migrating to a national IP-enabled emergency network capable of receiving and responding to all citizen-activated emergency communications and improving information-sharing among all emergency response entities." The plan was to have been delivered no more than 270 days after enactment of the bill, a late April 2009 deadline. The plan was to be developed in consultation with a broad range of representatives for public safety, persons with disabilities, equipment and service providers and others. Congress required in the NET 911 Improvement Act of 2008 that the National Plan "assess, collect, and analyze the experiences" of trial deployments such as those conducted for NG9-1-1 by the Department of Transportation. The various analyses of IP-based systems prepared as part of DOT's NG9-1-1 assessment provided the core of the ICO's national plan for migrating to IP-enabled 911. The national plan prepared by the ICO was required to describe positive steps to include 911 in the transition to IP-enabled technologies and to provide recommendations where congressional action could facilitate the process. The plan as submitted describes a number of steps for governance but it is not clear what role, if any, a federal department or agency will have in deploying the new technologies. The transition could occur through the combined efforts of states with little participation by the federal government. Based on the legislation calling for the 911 transition plan, Congress had expected the plan to make recommendations, including congressional actions, if needed. Instead, the plan reiterated DOT's framework for areas where action might be taken without providing specific guidance to Congress. The plan was presented on September 25, 2009, leaving no time for the ICO to develop more detailed plans for action before its authority ended on September 30. As an extension of its Emergency Medical Service (EMS) mission, the National Highway Traffic Safety Administration (NHTSA), within the U.S. Department of Transportation (DOT), has provided the bulk of federal support in assisting wireless E-911. In 2002, under the leadership of then-Secretary of Transportation Norman Y. Mineta, DOT created the Wireless E9-1-1 Steering Council to foster cooperation and dialog among key participants. In 2005, DOT announced plans to produce a national framework and deployment plan for an NG9-1-1 system, to be developed over a three-year period. The new initiative built on earlier wireless 911 projects within DOT. The NG9-1-1 program has been administered within the Research and Innovative Technology Administration (RITA), part of DOT's Intelligent Transportation Systems (ITS) program. Management of the program has been shared between the ITS Public Safety Program and NHTSA, with assistance from the consulting firm, Booz Allen Hamilton. DOT has published technical requirements and a concept of operations for NG9-1-1, has implemented a strategic outreach plan, has worked to develop and validate requirements for the NG9-1-1 system, has produced a system design document, and has developed a transition plan. In the concept of operations, DOT stated The primary goal of the NG9-1-1 System is to save lives, health, and property by improving emergency services access and response in the United States. The state of the NG9-1-1 System also has a major effect on transportation security, mobility, and efficiency. The major features of the envisioned NG9-1-1 System that support this goal are described as Quicker receipt of more robust information. Better and more useful information from any networked communications device. Geographic-independent call access, transfer, and backup among PSAPs and between PSAPs and other authorized emergency organizations. Increased coordination and partnerships within the emergency response community. Increased aggregation and sharing of data, resources, procedures, and standards to improve emergency response. Maximized use of available public capital and operating costs for emergency communications services. NHTSA continues its commitment to working with emergency responders and the 911 community. It plans to build on the relationships it has developed with local, state, federal, and private stakeholders to support the development of NG9-1-1. Among its immediate objectives is managing a national 911 resource center to support the development of new emergency access systems, including a model state 911 law and a compilation of NG9-1-1 standards. NENA has prepared a handbook that identifies six transition policy issues that could be could be considered starting points in the transition to NG9-1-1. NENA has urged that these issues be considered as part of a larger review of strategy and implementation plans. To this end, the handbook has listed proposed actions, implementation checklists, and other specific steps in support of each goal. The objectives are Establish a state-level organization to plan, coordinate, and implement a ubiquitous Next Generation 9-1-1 system. Provide sufficient resources to implement and operate the NG9-1-1 system. Modify and update current legislation, regulations, and tariffs to ensure a competitive E9-1-1 environment and a transition to a full NG9-1-1 system. Establish statewide Emergency Services IP networks (ESInets), and ensure that state and regional authorities recognize the need for statewide IP-enabled networks for NG9-1-1 and other emergency services. Verify that information delivered over Next Generation 9-1-1 Systems can be appropriately delivered to PSAPs and shared with emergency response organizations while conforming to applicable confidentiality, disclosure, and information retention statutes and rules. Assure that state and federal liability statutes cover all public and private entities involved in the end-to-end provisions of NG9-1-1 and emergency communications systems and services. To achieve these objectives and carry out the recommended activities, NENA has suggested the formation of regional, state, or multi-state working groups. The handbook has emphasized that decisions about delivering 911 services at the local level would remain with the PSAPs. The ESInets that the handbook has proposed would require a higher level of governance to assure functions such as coordination and interoperability. Although NG9-1-1 is being developed as an open standards/open interface system it is necessary to establish standards that assure full interoperability among all systems and system components. To this end, NENA has established a Certification and Accreditation program for NG9-1-1. To draw all stakeholders into the process, NENA sponsored its first Industry Collaboration Event, to test equipment and standards, in November 2009. The ARRA required the FCC to prepare a national broadband plan. Among the requirements for the plan, Congress specified that it should include a plan for use of broadband infrastructure and services in advancing consumer welfare, civic participation, public safety and homeland security, community development, health care delivery, energy independence and efficiency, education, worker training, private sector investment, entrepreneurial activity, job creation and economic growth, and other national purposes. The National Broadband Plan (NBP) was submitted to Congress on March 16, 2010. In line with instructions from Congress, the plan included a section on public safety broadband communications that covered NG9-1-1, the Emergency Alert System, broadband radio networks for first responders, cybersecurity, and protection of critical infrastructure. In most sections of the NBP, the FCC has recommended actions for Congress and for other agencies, as well as laying out new steps that the FCC could take. As regards NG9-1-1, the plan suggested that Congress might consider enacting a federal legal and regulatory framework for NG9-1-1. It requested that the FCC be given the authority to implement this framework. To help meet funding requirements, the report suggested that Congress might take actions to assure that fees collected to fund 911 services are not used for other purposes. The plan also recommended that Congress consider reauthorizing the ICO to "help ensure that NG9-1-1 is deployed in an interoperable and reliable fashion." The NBP requested that, by December 1, 2011, NHTSA prepare a report to identify the costs of deploying NG9-1-1 and sources of funding. The NBP specified that the report should detail costs for particular 911 requirements and specify how costs would be shared among PSAPs, broadband service providers, and third-party providers for NG9-1-1. The FCC proposed that the report also include a technical analysis and cost study of different delivery platforms, including VOIP. Based on the information compiled for the report, NHTSA should make recommendations to Congress for public funding, according to the FCC proposal. The plan also provided specific actions for the FCC to take. The NBP announced the FCC's intentions to address IP-based NG9-1-1 by refreshing a current proceeding on location technology and opening a new proceeding to address how NG9-1-1 can accommodate communications technologies, networks, and architectures beyond traditional voice-centric devices. The plan also recommended consideration of a national strategy for NG9-1-1 deployment and how it should meet consumer expectations; a Notice of Inquiry seeking comment on next-generation 911 deployment was released December 21, 2010. The Department of Homeland Security Appropriations Act, 2007 ( P.L. 109-295 ) provided for coordination of emergency communication grants, and for the formation of Regional Emergency Communications Coordination (RECC) Working Groups. The requirement to establish regional working groups responded in part to requests from the public safety community to include the second tier of emergency workers in planning for interoperable communications. Non-federal members of the RECC groups are to include first responders, state and local officials and emergency managers, and 911 call center personnel. The Department of Homeland Security (DHS) is the lead agency for the RECC plans and for other emergency communications planning initiatives, notably the National Infrastructure Protection Plan, FEMA Disaster Emergency Communications planning, and the National Emergency Communications Plan. As part of the grants process for interoperable communications, Congress required the preparation of a National Emergency Communications Plan (NECP). DHS issued the NECP in July 2008. The primary purpose of the plan is to provide an overarching strategy for emergency communications preparedness. To meet preparedness goals, the NECP provides guidelines and deadlines for emergency managers at all levels of government. The improvement of 911 systems and PSAP communications is among the plan's objectives for Disaster Communications Capabilities. Specifically, Initiative 7.2 of the NECP states that agencies with operational responsibilities "should evaluate the readiness posture of communications centers (e.g., Public Safety Answering Points)" for vulnerabilities. According to the plan, "System planning activities should account for the availability of alternative and backup communications solutions and redundant pathways (i.e., provided by different vendors) to support communications if primary capabilities become unavailable." A recommended first milestone for this initiative is for RECC Working Groups to work with state and local agencies to assess priority vulnerabilities that could weaken critical mission response. Later milestones that apply to PSAPs and 911 systems include Develop plans and procedures to enhance emergency 911 systems and PSAP communications. Identify alternate and/or backup capabilities in emergency communications plans defined by all federal, state, local, and tribal agencies. These goals for states to improve 911 systems are compatible with DOT's efforts with 911 and NG9-1-1; the DOT programs are referenced in the plan. Title VI of the Homeland Security Appropriations Act, 2007 ( P.L. 109-295 ). Title VI—the Post-Katrina Emergency Management Reform Act of 2006—reorganized the Federal Emergency Management Agency (FEMA), gave the agency new powers, and clarified its functions and authorities within DHS. Among the new initiatives required by the law was the creation of Regional Emergency Communications Coordination (RECC) Working Groups as part of ten Regional Offices. These groups could provide a platform for coordinating emergency communications plans among states and were intended to include representatives from many sectors with responsibility for public safety and security. The formation of the regional working groups, the RECCs, responded in part to requests from the public safety community to expand interoperable communications planning to include the second tier of emergency workers. Non-federal members of the RECC are to include first responders, state and local officials and emergency managers, and PSAPs. Additionally, RECC working groups are to coordinate with a variety of communications providers (such as wireless carriers and cable operators), hospitals, utilities, emergency evacuation transit services, ambulance services, amateur radio operators, and others as appropriate. The RECC Working Groups could play a part in forming future policies for the transition to NG9-1-1. The working groups could provide another opportunity for federal leadership in assisting 911, especially in coordinating the transition to IP-enabled emergency communications with the deployment of new broadband infrastructure. Broadband is generally used to refer to fast transmission speeds, and the National Broadband Plan (NBP) establishes benchmarks for minimum speeds for broadband services. The NBP also equates broadband with the characteristics of ubiquity, efficiency, and effectiveness. Much of the plan emphasizes the importance of having broadband access to the Internet to meet social and economic goals. IP-enabled networks for emergency communications require broadband infrastructure to operate effectively; however, they need not connect with the Internet. Using the Internet Protocol, an IP-enabled network provides applications that meet specific needs. An IP-enabled network for emergency communications has been defined as an "emergency communications network or system based on a secured infrastructure that allows secured transmission of information, using Internet Protocol, among users of the network or system." Such a network, if fully realized, could support many types of emergency communications needs, including first responder networks and emergency alerts. The NBP has discussed some of the ways that federal investment in broadband infrastructure might be leveraged for community and state broadband services and it has explored the impact of broadband technology on emergency communications services. The plan has recognized the common elements of broadband use in emergency communications but it has not explicitly addressed the possibility of unifying them as a common infrastructure project. In the NBP, the FCC has made recommendations that support the transition to NG9-1-1 but it has not provided a policy statement that captures the vision of shared capacity, with many applications riding on the same infrastructure. Others, however, have described the future as a grid (Global Information Grid, Department of Defense) or an Emergency Services Internet (ESInet, NENA). The implementation of IP-enabled NG9-1-1 embraces many complex and inter-related decisions about, for example, governance, standards and technology, funding, and leadership. Congress has addressed some of these issues in the context of existing 911 infrastructure and technology, and has recognized the need to plan for the transition to the next generation. This transition will, over time, present many new policy issues. Congressional policy goals for the future could include Addressing emergency communications needs and goals with a policy that recognizes the convergence of technologies, especially IP-based networks and standards, that will place first responder networks, 911 systems, and emergency alert systems on common, interoperable platforms. Identifying the federal role in implementing national policies for emergency communications without eroding state or local authority. Defining the role of the Department of Homeland Security, especially the Regional Emergency Communications Coordination Working Groups that it supports, in guiding policies to sustain and improve 911 as part of its Emergency Communications Plan. Reviewing the federal regulatory role in promoting competition in the provision of network services to PSAPs. Designating radio frequency spectrum to provide connectivity to PSAPS, for example by using wireless technologies such as microwave transmission in place of fiber-optic cables. Addressing the quality of interfaces with other emergency communications networks, especially the radio links to first responders, and their spectrum needs. Providing funding solutions. Establishing national guidelines or requirements for minimum levels of 911 service. Establishing a program to assure that the quality of 911 services improves steadily, nationwide. Emergency communications professionals in the public and private sector deem it essential that the full potential of a broadband emergency communications grid, what NENA calls the ESInet, be recognized and supported by policy makers at all levels of government. Appendix A. 911 Legislation and Policy This section provides further detail and documentation about 911 requirements enacted by Congress and related administrative activities. Equality of Service and Access to 911 Many of the FCC's regulatory efforts have supported this principle by requiring that different providers of voice communications services be able to provide 911 facilities with basic information about a caller, specifically call-back number (Automatic Number Information, ANI) and location (Automatic Location Identification, ALI). Equality of Access Devices The 911 Act assured that wireless carriers would have similar obligations and protections in transmitting 911 calls as the wireline common carriers. The NET 911 Improvement Act of 2008 extended these obligations and protections to include Voice Over Internet Protocol (VOIP). The Federal Communications Commission (FCC) is responsible for promulgating and enforcing regulations to assure that cell phone and VOIP calls, as well as those from wireline phones, convey required information to the appropriate Public Safety Answering Point (PSAP). Providing position information that locates cell phone or VOIP callers in a manner comparable to wireline information is one of the challenges for parity among devices. Another challenge is presented by connections to third-party service providers. For example, telematics systems installed in cars, such as OnStar; direct emergency calls automatically to a customer service operator who then places the call to 911, usually identifying the appropriate call center from a database. Video Relay Service for the hearing impaired is another example of an intermediary placing the call to a PSAP. Access to PSAP contact information for third-party service providers continues to be an issue of concern to companies that provide services that include contacting 911 for assistance. To address this concern, the National Emergency Number Association (NENA) maintains a registry of PSAP information that it makes available to validated call centers as well as PSAPs. The NET 911 Improvement Act of 2008 specifically authorized, but did not require, the FCC to compile a list of contact information of public safety answering points and make the information available where releasing it would benefit public safety. The NET 911 Improvement Act of 2008 also extended parity of protection to duly authorized emergency communications service providers that voluntarily offer these services. Equality of Coverage The location of a caller often determines the level of response from a PSAP. The likelihood of a 911 call being completed with accurate information depends on two essential components: the capacity of the network and systems to capture and deliver the needed information and the capability of the PSAP to receive it. Providing location information in rural areas, for example, can be difficult for wireless carriers, partly because of inadequate infrastructure. Reflecting concerns that some carriers would stop serving remote areas rather than invest in improving location identification capabilities, the ENHANCE 911 Act of 2004 directed the FCC to grant waivers to Tier III wireless carriers in situations where strict enforcement would decrease access to emergency services. The ENHANCE 911 Act of 2004 also required the FCC to study the situation of Tier III wireless carriers regarding the waiver process and to provide information on effective technologies for implementing Phase II of W-E911. The FCC submitted a detailed report in April 2005 but made no recommendations regarding technology. Improving Location Information In addition to problems in rural areas, noted above, high-density urban areas also have location problems, such as when a 911 call is made from inside a high-rise building. Even if wireless E-911 is in place at the appropriate PSAP, location identification can provide a street address but not a floor level. Location information is readily available for wireline phone subscribers, as most telephone service providers have identifiable addresses stored in their databases. (Many rural areas have invested in converting generic rural addresses, such as rural routes or post office boxes, into house-specific coordinates for 911 location information.) The Association of Public-Safety Communications Officials International, Inc. (APCO) conducted an independent test of the accuracy of location information received by PSAPs that indicated many failings in the provision of location information from wireless calls. Partially in response to the APCO study, the FCC opened a new proceeding and in November 2007 proposed rules for carriers to provide more accurate location information to PSAPs. Verizon, AT&T, and other carriers and industry groups questioned whether the FCC's ruling was technically feasible and recommended a 911 working group to develop and agree upon standards for location accuracy and other features of 911. The FCC withdrew the contested rules and in September 2008 sought comments on new service rules for location accuracy. The FCC has not issued a final ruling and ex parte comments continue to be posted. The NET 911 Improvement Act of 2008 directed the FCC to work with PSAPs, the industry, and the E-911 Implementation Coordination Office to improve standards and best practices for a number of goals related to location identification. The NET 911 Improvement Act of 2008 also requires that the National Plan identify location technologies for nomadic devices and for office buildings and multi-dwelling units. Improving PSAP Capabilities To meet anticipated new requirements for location information at the PSAP level, wireless carriers will need to improve the technology they use. PSAPs must also invest in technology in order to receive more detailed information. Guidance and assistance for these tasks are provided primarily at the state and local level. NENA and APCO are active in providing frameworks for decision-making, and technical reports. The Seventh National Reliability and Interoperability Council (NRIC), a federal advisory committee to the FCC, provided best practices and other analyses for PSAPs to improve 911 operations. It also urged the development of a common platform that would link 911 to an interoperable communications network based on Internet technologies. The FCC's February 2008 summit for 911 circulated a list of best practices for PSAPs. The 2009 summit for 911 discussed deployment and operational guidelines for next generation IP-enabled 911. To address PSAP needs, the National Plan required by the NET 911 Improvement Act of 2008 must contain "specific mechanisms for ensuring the IP-enabled emergency network is available in every community.... " Equality for the Disabled The NET 911 Improvement Act of 2008 has required the National Plan to identify solutions for providing 911 support and access to those with disabilities. The FCC currently enforces Title IV of the Americans with Disabilities Act ( P.L. 101-336 ) for access to telecommunications services. Requirements for wireless carriers to accommodate TTY calls to 911 have been part of the FCC regulations since rules were first promulgated in 1996. The FCC is endeavoring to improve 911 support provided through Internet-based forms of the Telecommunications Relay Service that allow persons with hearing and speech disabilities to communicate with hearing users of telephone services. Mechanisms to Improve Funding for PSAPs The ENHANCE 911 Act of 2004 provided a mechanism for funding 911 with a program of matching grants. Authorizations of up to $250 million annually for program activities and grants were established for fiscal years 2005 through 2009, with authority for authorizations set to expire on October 1, 2009. Despite the authorization, no appropriations were made, although some funding was provided through the Digital Transition and Public Safety Fund, created by the Deficit Reduction Act of 2005 ( P.L. 109-171 ). The National Telecommunications and Information Administration (NTIA) is responsible for administering distributions from the fund, as designated by Congress in the act. Up to $43.5 million was designated specifically for 911, payable from the proceeds of spectrum auctions that took place in early 2008. The Implementing Recommendations of the 9/11 Commission Act of 2007 authorized the NTIA to borrow against the $43.5 million from spectrum auction proceeds and included an amendment that favors Public Safety Answering Points not capable of receiving 911 calls. There are 91 counties in the United States where emergency calls are handled without the benefit of any 911 technology. The NET 911 Improvement Act of 2008 further amended the guidelines for grant eligibility by adding "migration to an IP-enabled emergency network" as a qualifying program for grant funds. The program will be administered by the NHTSA. In addition to establishing a grants program to help PSAPs install 911 systems, the ENHANCE 911 Act of 2004 provided a mechanism to penalize states and other jurisdictions that diverted fees collected for 911 to other purposes. This provision was in response to reports of abuses documented by CTIA - The Wireless Association in 2003; later abuses have also been documented. To discourage this practice, the ENHANCE 911 Act of 2004 structured its matching grants program to refuse federal grants to jurisdictions where funds collected for 911 were used for other purposes. As required in the act, the Government Accountability Office prepared a report about state and local 911 systems that included an analysis of surcharges and their uses. The NET 911 Improvement Act of 2008 established an annual requirement for the FCC to prepare a survey of the collection and disbursement of fees collected for 911 and by states and political subdivisions and to report if fees are diverted. The purpose of the reporting requirement is to "ensure efficiency, transparency, and accountability." The act also specifically allows states to collect a fee on VOIP services with the proviso that the fees must be used for 911 or E-911. Federal Funding for 911 in Rural Areas The Food, Conservation, and Energy Act of 2008 ( P.L. 110-234 ), referred to as the 2008 Farm Bill, included language that can provide loans to improve 911 and other emergency communications capabilities in rural areas. The provision amends the Rural Electrification Act lending authority to include "facilities and equipment to expand or improve in rural areas— "(1) 911 access; "(2) integrated interoperable emergency communications, including multiuse networks that provide commercial or transportation information services in addition to emergency communications services; "(3) homeland security communications; "(4) transportation safety communications; or "(5) location technologies used outside an urbanized area." The bill allows government-collected fees such as state and local fees for 911 to be used as surety against loans. It also permits loans to companies that will provide communications equipment, if local governments with jurisdiction are not allowed to acquire the debt. Funding for 911 by States and Communities A large share of the costs for implementing 911 services is covered by the telecommunications industry and by state and/or local taxes or surcharges assessed on wireline and wireless telephone bills. Most states have some form of 911 or E-911 fund that receives revenue from telephone bill surcharges and distributes it to various jurisdictions; some states also compensate telephone companies for 911-related expenses. Another source of funding, at the local or county level, is an increase in property taxes with the additional monies going to PSAPs. Call center operators also hold fund-raisers like fish fries and bake sales. Federal Leadership in Improving 911 Capabilities Language in support of a leadership role by a federal agency to guide 911 policy appears in each of the major bills that Congress has passed. The ENHANCE 911 Act of 2004, for example, stated Enhanced 911 is a high national priority, and it requires Federal leadership, working in cooperation with state and local governments and with the numerous organizations dedicated to delivering emergency communications services. The ENHANCE 911 Act of 2004 recognized the role of the U.S. Department of Transportation (DOT) in providing sustained support of 911 by making it a co-administrator of the E-911 Implementation Coordination Office (ICO). The FCC has also played a visible role in supporting 911, much of it through regulation. The Role of the FCC Charged in the 911 Act of 1999 to take positive steps to address the implementation of 911 services, the FCC has primarily played the role of regulator of wireless communications service providers, promulgating and enforcing regulations to provide ANI/ALI information. Beginning in 2003, the FCC has held occasional public forums to discuss 911 deployment and possible actions. After the establishment of the Public Safety and Homeland Security Bureau in 2006, the FCC took action on another requirement of the 911 Act: to "encourage each State to develop and implement coordinated statewide deployment plans, through an entity designated by the governor, and to include representatives of the foregoing organizations and entities in development and implementation of such plans." It has contacted each state governor and requested information about points of contact for emergency communications. As these are provided, the FCC posts them on a website established for that purpose. The 2007 appropriations bill for the Department of Homeland Security included a requirement that the FCC submit a report to Congress on the capacity, nationwide, for rerouting 911 calls when call centers are disabled by disaster. The law specified that the report would cover the "status of efforts of State, local, and tribal governments to develop plans for rerouting 911 and E911 services in the event that public safety answering points are disabled during natural disasters, acts of terrorism, and other man-made disasters." In the required report, the FCC focused on administrative mechanisms not system capacities, indicating that most states had some form of backup plan. The report did not explore the limitations of existing technology nor consider possible changes to improve backup capacity. The report was submitted to Congress in September 2007 but has not been made public. The Role of the E-911 Implementation Coordination Office The keystone of the ENHANCE 911 Act of 2004 was the mandate to establish a program "to facilitate coordination and communications between Federal, State, and local emergency communications systems, emergency communications personnel, public safety organizations, telecommunications carriers, and telecommunications equipment manufacturers and vendors involved in the implementation of E-911 services." The act designated the director of the National Telecommunications and Information Administration (NTIA) and the Administrator of the National Highway Traffic Safety Administration (NHTSA) to direct the program as co-administrators of an E-911 Implementation Coordination Office. The two offices were to develop a management plan to be submitted to Congress. Once the office was established, the co-administrators were required to report to Congress annually on activities "to improve coordination and communication with respect to the implementation of E-911 services." Absent funding from specifically-designated appropriations, the program as required by Congress was not established at the time. NHTSA, in conjunction with DOT's Intelligent Transportation Systems program, moved forward with the Next Generation 911 Initiative. Once funding became available as part of the Deficit Reduction Act, the NTIA moved to sign a memorandum with DOT and prepare regulations for the grants programs for public comment. The NET 911 Improvement Act of 2008 gave the ICO the new responsibility of creating a National Plan for the migration to IP-enabled emergency communications network to support 911 and other citizen-activated calls. Citizen-activated calls for help currently go to 911, to 311, to 211, and to other call centers in both the public and private sector. Transition to IP-Enabled 911 Systems: The NET 911 Improvement Act of 2008 The NET 911 Improvement Act of 2008 has required that the ICO "shall develop and report to Congress on a national plan for migrating to a national IP-enabled emergency network capable of receiving and responding to all citizen-activated emergency communications and improving information-sharing among all emergency response entities." The plan was to have been delivered in April 2009. The plan was to have been developed in consultation with a broad range of representatives for public safety, person with disabilities, equipment and service providers and others. Some of the requirements for the plan have been referenced in the preceding sections of this report. They are recapped below, organized by the policy goal that each provision would support. Equality Provide mechanisms to ensure that the IP-enabled emergency network is available in every community and is coordinated at the local, state, and regional level. Identify location technology for nomadic devices and for office buildings and multi-unit dwellings. Identify solutions for those with disabilities, steps to be taken, and a timeline for action. Analyze efforts to provide automatic location information and provide recommendations for necessary regulatory or legislative changes. Funding Identify barriers that must be overcome and funding mechanisms to address barriers. Transition to IP-Enabled Networks Outline the potential benefits of migrating to a national IP-enabled emergency network for citizen-activated calls. Include a proposed timetable, an outline of costs, and potential savings for the transition to IP technologies. Provide specific legislative language, if necessary, for achieving the plan. Provide recommendations on any legislative changes, including updating definitions, necessary to facilitate a national IP-enabled network. Assess, collect, and analyze information from trial deployments of IP-enabled emergency networks. Appendix B. Citizen-Activated Calls: 211 The term citizen-activated emergency call refers generally to calls placed by individuals seeking assistance in an emergency. These calls are differentiated from alerts sent by authorities to warn communities of potential danger or to provide instructions after a disaster. Citizen-activated calls for help currently go to 911, to 311, to 211, and to other call centers in both the public and private sector. The 311 code was created by the Federal Communications Commission (FCC) in 1997 to take non-emergency police calls as a means to reduce congestion on 911 lines. The 211 dialing code is reserved by the FCC on a provisional basis as a universal number for community information and referral. The 211 call centers support a variety of social service hot lines—including assistance in foreign-languages—and can also be used to provide information and guidance in emergency situations. A large part of the U.S. population has access to 211 call services but no state has statewide service. Many cities have adopted shared-service communications hubs handling 211 and 311 calls. Service levels and response times for all types of citizen-activated calls would benefit from a transition to IP-enabled networks and in many cases could share infrastructure with 911 networks Call Centers and Post-Disaster Response Call centers are identified as a pivotal link in an end-to-end network of emergency communications, information, response, and post-incident care. A report by the Wireless Emergency Response Team (WERT) discussed the valuable help provided to victims of the September 11, 2001, World Trade Center attack through call center services donated by BellSouth. Over 400 hotlines were established in New York City after 9/11, however, creating a confusing network for victims and volunteers. After Hurricane Katrina, call centers, including 211 call centers, were used to help locate displaced victims and direct them to shelters and social services. A post-hurricane evaluation by the Federal Emergency Management Agency (FEMA) after the 2005 season recommended that states establish 211 systems as part of their plans for response and recovery. A study of the role of 211 call centers during the Florida hurricane season of 2004 documented a number of ways that the call centers were of assistance: expanded the capacity of Emergency Operations Centers by providing trained information and referral specialists; offered additional access points for public information; managed information about the availability of services; identified unmet and emerging needs; helped prioritize and direct resources; provided reassurance and crisis support; helped mobilize and manage volunteers and donations; served as intake points for government agencies and non-profit organizations; offered sustained support for long-term recovery efforts. In addition to disaster recovery efforts, 211 call centers respond to a wide range of social service needs for information and counseling, such as parent support, suicide prevention, health information, traveler's aid, tracking and helping welfare clients, and housing assistance. Call Centers and Federal Policy In 2008, the Department of Homeland Security (DHS) awarded a grant to Texas A&M Research Foundation to study 211 calls, initiating what DHS calls the Public Needs Project. The objective of the research was to provide information for state call centers to develop systematic approaches to responding to calls after major disasters. The study was to analyze calls for assistance made to the 26 211 call centers in Texas during a four-month period before, during, and after Hurricanes Katrina and Rita. The study's conclusions could provide the basis for incorporating 211 call centers into federal planning for emergency response and funding for infrastructure. The target date to provide initial conclusions from the study was year-end 2009. The WERT report issued after the September 11 attacks urged that national planning for emergency preparedness and response include the mobilization of private-sector call centers to field calls for information and assistance for non-life-threatening needs. Call Centers and Congress Legislation introduced in the 111 th Congress includes two bills covering 211 call centers: S. 211 (Senator Clinton) and H.R. 211 (Representative Eshoo). Both would authorize funds and require improvements in the capacity of 211 help lines operated by nonprofit call centers. A question for the 111 th Congress might be whether federal funding for 211 call centers meshes with other goals that are expected to have priority, such as job creation and investment in infrastructure. Recommendations from the DHS study on 211 might advocate additional funding for 211 services because of their role in emergency response. This could provide a different viewpoint for Congress to evaluate funding programs. Appendix C. Grants Awards for 911 Programs Following is the list of award recipients of federal grants for 911 and related programs. 

Summary: Today's 911 system is built on an infrastructure of analog technology that does not support many of the features that most Americans expect to be part of an emergency response. Efforts to splice newer, digital technologies onto this aging infrastructure have created points of failure where a call can be dropped or misdirected, sometimes with tragic consequences. Callers to 911, however, generally assume that the newer technologies they are using to place a call are matched by the same level of technology at the 911 call centers, known as Public Safety Answering Points (PSAPs). However, this is not always the case. To modernize the system to provide the quality of service that approaches the expectations of its users will require that the PSAPs, and state, local, and possibly federal emergency communications authorities invest in new technologies. As envisioned by most stakeholders, these new technologies—collectively referred to as Next Generation 911 or NG9-1-1—should incorporate Internet Protocol (IP) standards. An IP-enabled emergency communications network that supports 911 will facilitate interoperability and system resilience; improve connections between 911 call centers; provide more robust capacity; and offer flexibility in receiving and managing calls. The same network can also serve wireless broadband communications for public safety and other emergency personnel, as well as other purposes. Recognizing the importance of providing effective 911 service, Congress has passed three major bills supporting improvements in the handling of 911 emergency calls. The Wireless Communications and Public Safety Act of 1999 (P.L. 106-81) established 911 as the number to call for emergencies and gave the Federal Communications Commission (FCC) authority to regulate many aspects of the service. The most recent of these laws, the NET 911 Improvement Act of 2008 (P.L. 110-283), required the preparation of a National Plan for migrating to an IP-enabled emergency network. Responsibility for the plan was assigned to the E-911 Implementation Coordination Office (ICO), created to meet requirements of an earlier law, the ENHANCE 911 Act of 2004 (P.L. 108-494). Authorization for the ICO terminated on September 30, 2009. ICO was jointly administered by the National Telecommunications and Information Administration and the National Highway Traffic Safety Administration. The FCC has included recommendations for advancing NG9-1-1 as part of the National Broadband Plan it presented to Congress on March 16, 2010. It has proposed that the FCC take on an expanded role in assuring that NG9-1-1 services meet future consumer expectations for broadband-based communications. Congress may evaluate whether additional actions are needed on its part in order to support a cohesive policy for transitioning to NG9-1-1. Other types of citizen-activated emergency calls are handled in call centers. Increasingly many calls for assistance are placed by dialing 211. The number has been provisionally designated for community information and referrals. Service levels and response times for 211 calls would benefit from a transition to IP-enabled networks and in many cases could share infrastructure with 911 networks.