Telecom Procedural Letter Addressed to Distribution List
Ottawa, 29 March 2016
Our reference: 1011-NOC2016-0116
RE: Requests for information related to Telecom Notice of Consultation CRTC 2016-116 on the Establishment of a regulatory framework for next-generation 9-1-1 in Canada
Today, the Commission published Telecom Notice of Consultation CRTC 2016-116 to announce a consultation, which is to include an oral hearing, on the establishment of a regulatory framework for next-generation 9-1-1 services in Canada.
In order to assist the Commission in its consideration of the issues set out in the Notice of Consultation, Commission staff is requesting information from the large incumbent local exchange carriers (ILECs) and small incumbent local exchange carriers (SILECs) as well as public safety answering points (PSAPs). Questions specific to ILECS and SILECs (herein referred to as companies) are attached in Appendix 1, and questions specific to PSAPs are attached in Appendix 2. The responses to this request for information must be filed via My CRTC Account by 29 April 2016. Footnote 1
Responses should be provided in a single document, addressing requests for information, in order to facilitate accessibility and administrative processing. PSAPs may choose to coordinate, organize, and file, their responses in conjunction with other PSAPs who share their position, and similarly companies have the option to file their responses in conjunction with other companies. These responses will be published on the Commission’s website under the file number identified above.
Pursuant to subsection 37(2) of the Telecommunications Act (the Act), the Commission may require a person other than a Canadian carrier that is in possession of information that the Commission considers necessary for the administration of the Act, to submit the information to the Commission.
As set out in section 39 of the Act and in Broadcasting and Telecom Information Bulletin CRTC 2010-961, Procedures for filing confidential information and requesting its disclosure in Commission proceedings, persons may designate certain information as confidential. A person designating information as confidential must provide a detailed explanation on why the designated information is confidential and why its disclosure would not be in the public interest, including why the specific direct harm that would be likely to result from the disclosure would outweigh the public interest in disclosure. Furthermore, a person designating information as confidential must either file an abridged version of the document omitting only the information designated as confidential or provide reasons why an abridged version cannot be filed.
Should you have any questions regarding this letter, please contact Renée Doiron by email at email@example.com.
Original signed by
Director, Competition and Emergency Services Policy
c.c.: Renée Doiron, CRTC, 819-997-2755, firstname.lastname@example.org; James Ndirangu, CRTC 819-997-3670, email@example.com
- Bell Aliant Regional Communications, Limited Partnership and Télébec, Limited Partnership firstname.lastname@example.org
- Bell Canada email@example.com
- MTS firstname.lastname@example.org
- Northwestel email@example.com
- Saskatchewan Telecommunications firstname.lastname@example.org
- TELUS Communications Company email@example.com
- Amtelecom Telco GP Inc. firstname.lastname@example.org
- Brooke Telecom Co-operative Ltd. email@example.com
- Bruce Telecom firstname.lastname@example.org
- CityWest Telephone Corporation email@example.com
- Cochrane Telecom Services firstname.lastname@example.org
- CoopTel, coop de telecommunication email@example.com
- DMTS, a division of Bell Aliant firstname.lastname@example.org
- Executlink Telecom Inc. email@example.com
- Gosfield North Communication Co-operative Limited firstname.lastname@example.org
- Groupe Maskatel LP email@example.com
- Hay Communications Co-operative Limited firstname.lastname@example.org
- Huron Telecommunications Co-operative Limited email@example.com
- KMTS firstname.lastname@example.org
- La Cie de Téléphone de Courcelles Inc. email@example.com
- La Compagnie de Téléphone de Lambton Inc. firstname.lastname@example.org
- La Compagnie de téléphone de St-Victor email@example.com
- La Compagnie de telephone Upton Inc. firstname.lastname@example.org
- Landsdowne Rural Telephone Company Ltd. email@example.com
- Mornington Communications Co-operative Limited firstname.lastname@example.org
- Nexicom Telecommunications, a Division of Nexicom Inc. email@example.com
- Nexicom Telephones, a Division of Nexicom Inc. firstname.lastname@example.org
- North Frontenac Telephone Corporation Ltd. Fmantell6229@rogers.com
- North Renfrew Telephone Company Limited Trade email@example.com
- NorthernTel, Limited Partnership firstname.lastname@example.org
- O.N. Tel Inc. email@example.com
- People’s Tel Limited Partnership Stacey.firstname.lastname@example.org
- Quadro Communications Co-operative Inc. email@example.com
- Roxborough Telephone Company Limited firstname.lastname@example.org
- TBayTel email@example.com
- Téléphone de St-Éphrem inc. firstname.lastname@example.org
- Téléphone Milot Inc. email@example.com
- The Westport Telephone Company, Limited firstname.lastname@example.org
- Tuckersmith Communications Co-operative Limited email@example.com
- Wightman Telecom Ltd. firstname.lastname@example.org
Public Safety Answering Points
- Abbotsford Police, email@example.com
- Aeromedical Emergency Services Ltd., firstname.lastname@example.org
- Agence municipale de financement et de développement des centres d’urgence 9-1-1 du Québec email@example.com
- Alberta Emergency Management Agency firstname.lastname@example.org
- Bonnyville Regional Fire Authority, email@example.com
- Camrose Police Service, firstname.lastname@example.org
- Chatham Police, email@example.com
- City of Calgary, Public Safety Communications, firstname.lastname@example.org
- City of Edmonton 911 & Police, email@example.com
- City of Lethbridge, Public Safety Communications Centre, firstname.lastname@example.org
- City of Lloydminster 911 Centre, email@example.com
- City of Medicine Hat 911 Centre, firstname.lastname@example.org
- City of Red Deer Emergency Services, email@example.com
- DND Fire, firstname.lastname@example.org
- Durham Regional Police, email@example.com
- East Central 911 Call Answer Society, firstname.lastname@example.org
- E-Comm 9-1-1, email@example.com
- Espanola Police, firstname.lastname@example.org
- Foothills Regional Emergency Services Commission, email@example.com
- Gananoque Police/Fire, firstname.lastname@example.org
- Grande Prairie Fire Department, email@example.com
- Guelph Police, firstname.lastname@example.org
- Halton Regional Police, email@example.com
- Hamilton Police, firstname.lastname@example.org
- Hearst Communication Bureau, email@example.com
- Jasper Park 911 Centre, firstname.lastname@example.org
- Kawartha Lakes Police, email@example.com
- Kingston Police, firstname.lastname@example.org
- Kyetech Canada Inc., email@example.com
- London Police, firstname.lastname@example.org
- Manitoba EMO, email@example.com
- Manitoba Provincial PSAP, firstname.lastname@example.org
- Nelson City Police, email@example.com
- New Brunswick 9-1-1 Bureau, firstname.lastname@example.org
- NL911 Bureau Inc. kerrypower@NL911.ca
- Niagara Regional Police, email@example.com
- North Bay OPP, firstname.lastname@example.org
- North Bay Police, email@example.com
- Northern Communication Bureau, firstname.lastname@example.org
- Nova Scotia Emergency Management Office email@example.com
- Orangeville Police, firstname.lastname@example.org
- Orillia Fire, email@example.com
- Ottawa Police, firstname.lastname@example.org
- Owen Sound Police, email@example.com
- Parkland County Emergency Communications Centre, firstname.lastname@example.org
- Peel Regional Police, email@example.com
- Peterborough Police, firstname.lastname@example.org
- Prince Edward Island 9-1-1 Administration Office email@example.com
- Prince George RCMP, firstname.lastname@example.org
- Regional Emergency Services Fort McMurray, email@example.com
- Saanich Police, firstname.lastname@example.org
- Sarnia Police, email@example.com
- Sask911 firstname.lastname@example.org
- Sault Ste Marie Police, email@example.com
- St. Albert RCMP Detachment, firstname.lastname@example.org
- Strathcona County Emergency Services, email@example.com
- Strathroy Police, firstname.lastname@example.org
- Sudbury Regional Police, email@example.com
- Taber 9-1-1 Centre, firstname.lastname@example.org
- Thunder Bay Bureau, email@example.com
- Toronto Police, firstname.lastname@example.org
- Victoria Police, email@example.com
- Victoria RCMP, firstname.lastname@example.org
- Waterloo Regional Police, email@example.com
- Wheatland and District Emergency Medical Services, firstname.lastname@example.org
- Windsor Police, email@example.com
- Winnipeg Police Service PSAP, firstname.lastname@example.org
- Woodstock Police, email@example.com
- Yellowhead County Emergency Communications Centre, firstname.lastname@example.org
- York Police, email@example.com
- Yukon RCMP M Division Operational Communication Center, firstname.lastname@example.org
Appendix 1: Interrogatories for Large ILECs and Small ILECs
- Identify and describe the major network components, transmission facilities, databases and systems of your company’s current 9-1-1 network. For each major network component, transmission facility, database and system, provide the name of the vendor as well as an estimate for the remaining lifespan, taking into account the availability of replacement parts. Your response should be supported by network diagrams as appropriate.
- Has your company developed a plan to transition existing 9-1-1 networks to NG9-1-1 as defined in the NENA i3 architecture and specifications?Footnote 2
- If so, submit a copy of the plan or provide a detailed description of the plan.
- If not, explain why your company has not yet developed a plan, whether your company expects to develop a plan, and when it is expected to be completed.
- What are your company’s estimated timeframes, taking care to identify any major dependencies, to implement a NG9-1-1 network in your existing serving area:
- to support all existing 9-1-1 services (wireline, wireless, VoIP 9-1-1 services and Text with 9-1-1 for Canadians who have communication disabilities or who are Deaf or hard of hearing) using NG9-1-1 based network equipment, transmission facilities, systems and databases?
- to support future NG9-1-1 services (such as new methods of communication with 9-1-1 operators, and the transmission of new types of information such as pictures, video, and medical records to PSAPs) using NG9-1-1 based network equipment, transmission facilities, systems and databases?
- What possible challenges, if any, does your company face in transitioning to an NG9-1-1, and how does your company intend to deal with these challenges?
- Describe the current status of the evolution of your company’s current 9-1-1 network to NG9-1-1. More specifically, with respect to your company’s current 9-1-1 network:
- Identify which major network components, transmission facilities, databases and systems can already support NG9-1-1 or require minor to modest changes to support NG9-1-1 as defined in the NENA i3 specification. Your response should define the changes required and include estimated timeframes to implement these changes.
- Identify which major components, transmission facilities, databases and systems will be fully replaced in the long term or would require major changes to support NG9-1-1 as defined in the NENA i3 specification. Your response should define the changes required and include estimated timeframes to implement these changes.
- Identify any new network components, transmission facilities, databases and systems your company anticipates will need to be installed or added in order to transition to NG9-1-1 as defined in the NENA i3 specification? Your response should define the installations required and include estimated timeframes to deploy these installations.
Your responses to (a), (b), and (c) above should clearly identify any dependencies that your company must take into consideration in order for these changes to take place. Please provide network diagrams to support or illustrate your responses to (a), (b), and (c) above as appropriate.
- Describe the steps and transition process your company expects to undertake to implement NG9-1-1. At a minimum, indicate:
- whether your company expects to maintain both the current 9-1-1 and new NG9-1-1 networks in parallel. If so, for how long?
- the dependencies that your company has to take into consideration in determining how long you would have to maintain both the legacy 9-1-1 and NG9-1-1 networks in parallel.
- the major network components, transmission facilities, databases and systems of your current 9-1-1 networks your company expects to maintain, as well as the new ones to be added, during the various steps of the transition.
- the dependencies for each of the major network components, transmission facilities, databases and systems of your current 9-1-1 networks that your company expects will have to be maintained, as well as the new ones to be added, during the various steps of the transition.
- What are your company’s total expected capital and expense costs (separated by sunk and incremental costs) related to the transition to NG9-1-1? You response should indicate the annual costs, or if not available the costs in the short term (1-3years), mid-term (3-5 years), and long-term (5-10 years). Your response should provide supporting rationale and evidence to support your answer.
Appendix 2: Interrogatories for PSAPs
- Identify the communities your PSAP serves and the estimated number of residents in your service area. Provide maps if available.
- Identify and describe the secondary PSAPs that your PSAP has arrangements with. Further, provide the estimated number of residents served by each secondary PSAP.
- Identify the telecommunications service providers, including ILECs and small ILECs, on whom your PSAP currently relies for 9-1-1 network services. Further, identify and describe the specific telecommunications services that your primary PSAPs receives and from whom.
- Indicate and describe the number of PSAPs operating in your province, including both primary and secondary PSAPs.
- How is your PSAP funded? For example, is your PSAP funded by your municipal, provincial or territorial government and by what mechanism, such as municipal levies, are funds raised?
- Describe how decisions on service improvements or technical system upgrades are made for your PSAP.
- Identify and describe your PSAP’s current computer aided dispatch (CAD) software, 9-1-1 systems, 9-1-1 databases, and other PSAP 9-1-1 equipment, and estimate the remaining lifespan of each. Your response should be supported by the name of the vendors and network diagrams as appropriate.
- Has your PSAP started NG9-1-1 transition planning? If so, submit a copy of the plan, and if a written plan is not available, describe the plan. In addition, provide your estimated NG9-1-1 implementation costs, and indicate what progress your PSAP has made to secure funding for the implementation.
- What are your PSAP’s estimated timeframes, including major dependencies, to implement NG9-1-1:
- to support all existing 9-1-1 services (wireline, wireless, VoIP 9-1-1 services and Text with 9-1-1 for Canadians who have communication disabilities or who are Deaf or hard of hearing) using NG9-1-1 based CAD software, systems, databases, and other PSAP equipment?
- to support future NG9-1-1 services (such as new methods of communication with 9-1-1 operators, and the transmission of new types of information such as pictures, video, and medical records to PSAPs) using NG9-1-1 based CAD software, systems, databases, and other PSAP equipment?
- What possible challenges, if any, does your PSAP face in transitioning to NG9-1-1, and how does your PSAP intend to deal with these challenges?
- Describe the current status your PSAPs readiness for NG9-1-1. More specifically:
- What major CAD software, 9-1-1 systems, 9-1-1 databases, and other 9-1-1 equipment of your PSAP’s current 9-1-1 system can already support NG9-1-1 or require minor or modest changes to support NG9-1-1 as defined in the NENA i3 specification? Your response should define the changes required and include estimated timeframes to implement these changes. .
- What major CAD software, 9-1-1 systems, 9-1-1 databases, and other 9-1-1 equipment of your PSAP’s current 9-1-1 system will be fully replaced in the long term or would require major changes to support NG9-1-1 as defined in the NENA i3 specification? Your response should define the changes required and include estimated timeframes to implement these changes.
- What new CAD software, 9-1-1 systems, 9-1-1 databases, and other 9-1-1 equipment does your PSAP anticipate will be required in order to transition to NG9-1-1 as defined in the NENA i3 specification? Your response should define the installations required and include estimated timeframes to deploy these installations.
Your response to (a), (b) and (c) above should also identify the dependencies that your PSAP must take into consideration in order for these changes to take place, as well as network diagrams as appropriate.
- Does your PSAP need to review current arrangements with Secondary PSAPs and/or emergency responders in order to transition to a NG9-1-1 PSAP?
- Date modified: