Broadband Fund
Application Form Instruction Manual for Applicants (30 November 2022)

Download PDF (1.84 MB)

Version 3.0

Date updated: 30 November 2022

Notice for applicants: This manual may be updated. We will announce any updates in the Broadband Fund RSS feed.

Table of Contents

About this Call for Applications

This call for applications will close on 18 April 2023. You must ensure that your application has been completed and submitted by 5 p.m. Pacific Standard Time on that date.

Prior to submitting an application, you should review the CRTC Website, which contains resources to help you complete your application:

All required sections of the Online Application Form must be completed with the Application Workbook and all the required supporting documents attached. You can save your progress in the Online Application Form and the Application Workbook as you work. Therefore, we encourage applicants to begin working on their applications in advance of the deadline and to not wait until the last minute to submit their applications.

Should you have any questions of interpretation regarding these instructions, you can send the Broadband Fund team a message through our online contact form:

Contact the Broadband Fund team

Broadband Fund staff would like to acknowledge the contributions of our friend and colleague Demetra Langis, a Financial Analyst with the team since 2019, who we lost far too soon on November 6th, 2022. She will be dearly missed.

Manage My Applications

On this page you can choose to start a new application, resume work on an application in progress, and see what applications you have already submitted.

To note:

Application Workbook: The Application Workbook is supplied by the CRTC and must be used to provide the details of the project. All required sections must be completed in full according to the instructions provided in the Workbook and the Workbook MUST BE uploaded as part of the Application Form in Section B. Project Details. Information in the Application Workbook will take precedence if it conflicts with information provided elsewhere in your application. Applicants are advised not to attempt to edit the underlying logic of the Workbook as this may affect the CRTC’s ability to assess the data or may result in applicants not submitting all required information and therefore negatively affect your application’s eligibility and assessment. Applicants are also advised not to copy and paste values into the workbook unless the instructions on a particular sheet indicate that you may copy and paste information. The best way to avoid inadvertently impacting the formatting programmed into the Application Workbook is to use Microsoft Excel to complete the document.

Interactivity: The Online Application Form is interactive. The questions you are asked will depend on how you answered previous questions. You can return to previous responses and change them, which may change which questions appear on the following pages.

Required Fields: For items marked “(required)” you must provide an answer to these questions before you can move on to the next page in the form.

Group applications: When an application is being submitted on behalf of a partnership, joint venture or consortium, certain questions will require answers on behalf of individual members of the applicant group. Once a group entity application is selected you will not be able to change your selection to a single entity application. You will have to start a new application to make that change. The same is true if you wish to change from a single entity application into a group entity application.

Attachments: At the end of each section of the Online Application Form, you will be prompted to add a series of attachments to support the information you have provided in that section. Attachments should be uploaded according to the naming conventions provided. Note that the underscore is the only special character you may use when naming your documents.

Saving and Editing: You do not need to complete the application in a single session. You can save your work and return to where you left off to resume entering information.

Maximum character count: Each text box provided for additional information has a maximum character count. You must ensure that your response does not exceed the maximum character count. If it does, the system will cut off your response at the maximum count in order to submit your application. Note that the maximum character count includes spaces.

1. New Applications

Click “Start Application” to begin a new application. You will then be asked a few questions in order to set up the application form. There are multiple sections to the application, so ensure that you fill out all of the required sections.

2. Applications in Progress

You can save your work at any time and return to your application later. You can return to continue work on any unfinished applications by choosing “Resume” next to an existing application in the list. Once the application is complete you will be able to submit your application. The system will not accept applications that do not have all required fields completed and all required attachments uploaded.

Any applications that remain listed in this section at the time the call for applications closes WILL NOT be submitted to the Broadband Fund for funding consideration.

3. Submitted Applications

Applications listed in this section have been submitted for consideration. Your primary contact will receive a temporary confirmation number when it is submitted, and a final confirmation number at the time the call for applications closes.

If you would like to retain a copy of your application, use the “Download as PDF” button.

NOTE: You can modify a submitted application as long as the application deadline has not passed. To do so, choose “Modify” next to a submitted application. This will remove the application from the Submitted Applications list and move it to the Applications in Progress list, at which point you can modify it. Note that you MUST re-submit your application before the application deadline has passed in order for it to be considered for funding.

Start a New Application

The following information is required to create your application form template. You may have to answer these questions again later in the process. The questions also outline some of the basic eligibility requirements that must be met. Supporting information for each of these items will be requested later in the application process.

1. Call for Applications

If applicable, select from the drop-down list the call for applications to which you are applying.

2. Applicant

Select whether this application is being made on behalf of a:

  • Single entity applicant: A single corporation, provincial, territorial or municipal government entity, band council or Indigenous government that is responsible for this project, or;
  • Group entity applicant: A group made up of the entities listed above who have formed a partnership, joint venture or consortium that is responsible for this project.
    • NOTE: Corporations can be for-profit or not-for-profit, but must be incorporated at the federal or provincial/territorial level to be eligible.

If the applicant is a single entity:

  • Confirm that it is eligible to operate as a Canadian carrier pursuant to section 16 of the Telecommunications Act.
  • Indicate if it has experience both deploying and operating broadband infrastructure in Canada for a minimum of three years.

If the applicant is a group entity:

  • Confirm that at least one member of the partnership, joint venture or consortium is eligible to operate as a Canadian carrier pursuant to section 16 of the Telecommunications Act.
  • Indicate if the applicant or at least one member of the partnership, joint venture or consortium has experience both deploying and operating broadband infrastructure in Canada for a minimum of three years.

NOTE: For the purpose of the Broadband Fund, “deploying” broadband infrastructure is defined as constructing and implementing broadband networks or infrastructure through which broadband services will be delivered, and “operating” broadband infrastructure is defined as managing, monitoring, and controlling existing broadband networks or infrastructure through which broadband services are being delivered.

NOTE: If the applicant does not have the required experience, you must confirm that it has contracted another organization (Canadian corporation, government entity, or Band Council/Indigenous Government) that has the minimum three years of experience in both deploying and operating broadband infrastructure to assist with this project.

3. Project

Indicate the project name in the space provided. This will be used as an identifier title for your project.

NOTE: Applications for the main component of the Fund and applications that intend to serve satellite-dependent communities must be filed in separate applications. Due to Online Application Form and Application Workbook functionality constraints, a project that would draw from both the main component (e.g. a transport project) and the satellite component (e.g. a project to increase satellite transport capacity [operational costs]) must be submitted as two different projects; one for the main component and one for the satellite component. However, the CRTC would consider these two projects to be complementary projects, and therefore would not consider them to be improperly contingent on one another. When submitting the two different projects, applicants must ensure that they cross-reference one another in the project descriptions.

NOTE: Direct-to-Home (DTH) satellite access projects will not be considered in the third call for applications.

To be eligible for funding, you must confirm that your project (in addition to the other eligibility criteria detailed in the Application Guide):

You must also confirm that you will be investing your own funds in this project (amount to be confirmed later in the Application Form).

Complete the Assessment Criteria for your Application

If You are a Single Entity Applicant

An application by a single entity requires the following sections to be filled out:

  1. A. Single Entity Applicant Details: Contact information and financial information for the applicant. You will be asked to attach financial solvency information and documents showing the applicant’s legal status.
  2. B. Project Information: Detailed information about the project including technical descriptions. You will be asked to attach most supporting documents for your application in this form, including the Application Workbook, the Logical Network Diagram (LND), and mapping files.
  3. B1. Third-Party Funding: This form is only required if the project has funding from another source, aside from the Broadband Fund and the funds being invested by the applicant
    (e.g. funding from another government program or a community organization). One form is needed for each source of third-party funding. You must attach a funding letter or other proof that the funding has been awarded.
  4. C. Confidentiality and Declarations: This form provides applicants with an opportunity to claim confidentiality over parts of the application and to confirm all declarations listed in the Application Guide.

If You are a Group Entity Applicant

An application by a partnership, joint venture or consortium requires the following sections to be filled out:

  1. A. Group Entity Applicant Details: Contact information and financial information for the applicant. You will be asked to attach financial solvency information, documents showing the applicant’s legal status, experience, and roles and responsibilities among the members of the partnership, joint venture or consortium to this form.
  2. A1. Member Details: A form for each member of the partnership, joint venture or consortium, which includes the member’s contact details and financial information. You may be asked to attach documents demonstrating each group member’s eligibility to operate as a Canadian carrier, financial solvency, and legal status.
  3. B. Project Information: Detailed information about the project including technical descriptions. You will be asked to attach most supporting documents for your application in this form, including the Application Workbook, the Logical Network Diagram (LND), and mapping files.
  4. B1. Third-Party Funding: This form is only required if the project has funding from another source, aside from the Broadband Fund and the funds being invested by members of the partnership, joint venture or consortium (e.g. funding from another government program or a community organization). One form is needed for each source of third-party funding. You must attach a funding letter or other proof that the funding has been awarded.
  5. C. Confidentiality and Declarations: This form provides applicants with an opportunity to claim confidentiality over parts of the application and to confirm all declarations listed in the Application Guide.

NOTE: The Online Application Form will not allow you to submit incomplete sections or applications that are missing required attachments. Ensure that all necessary forms are filled out completely and that you have attached all the required supporting documents.

A. Single Entity Applicant Details

1. Applicant Details

Provide details about the applicant in this section.

2. Contact

Provide contact information for the applicant’s primary contact and for an alternate executive contact.

  • Primary contact: an authorized official – someone with authority to bind the organization to the commitments made in the application and to the resulting funding agreements if the project is selected.
  • Alternate contact: an additional contact who can be reached in case the primary contact is unavailable, preferably an executive level individual.

3. Legal Status, Carrier Status and Financial Solvency

3.1 CRTC Master Address Database (MAD) and Data Collection System (DCS)

If the applicant has a MAD number, provide it here.

If you provided a MAD number, you must indicate if you consent to the CRTC reviewing submissions made to the CRTC DCS, in order for it to verify the documentation provided by the applicant.

3.2 Legal Status

Applicants must be a legal entity to be eligible to apply. You will be asked to provide documents to show the legal status of the applicant.

If the applicant is a:

  • Band Council or Indigenous Government: space will be provided to indicate their Band Number or Band ID, if applicable.
  • Canadian Corporation: the jurisdiction in which the corporation is registered must be identified as Provincial/Territorial or Federal. For a Provincial/Territorial corporation you must specify the Province/Territory from a drop-down list. Enter the provincial Corporation Number, Business Identification Number or other appropriate registration number identifying the Corporation in the space provided.

You must upload any required supporting evidence at the end of this section, even if you provided a MAD number and consented to the CRTC reviewing submissions made to the CRTC DCS:

  • Evidence of the legal status of the applicant. Such evidence should include a copy of registration and key constituting documents, such as a certificate of incorporation, Canada Revenue Agency registration, and proof of registration of not-for-profit status or band number, if applicable.

3.3 Carrier Status

The applicant must be eligible to operate as a Canadian carrier pursuant to section 16 of the Telecommunications Act.

3.4 Financial Solvency

The applicant, except for provincial, territorial and municipal governments, must confirm that it, or each member of the applicant partnership, joint venture, or consortium, is financially solvent and reliable in accordance with the Generally Accepted Accounting Principles of Canada. Refer to section 14 of the Application Guide for definitions of “solvent” and “reliable.”

You must upload any required supporting evidence at the end of this section, even if financial solvency information is available in DCS:

  • A copy of independently prepared (including audited, review engagement, or notice to reader) financial statements (balance sheet, income statement, and cash flow statement, including financial statement notes and, if audited, the auditor’s report and opinions of the financial statements) for the last three calendar years. It is strongly recommended that applicants upload each fiscal year’s financial statements as separate upload files.

4. Experience

Indicate whether the applicant has three or more years of experience both deploying and operating broadband infrastructure in Canada and describe that experience in a few sentences, including information on where and how long the applicant has provided broadband services, and the number of customers currently served.

For the purpose of the Broadband Fund, “deploying” broadband infrastructure is defined as constructing and implementing broadband networks or infrastructure through which broadband services will be delivered, and “operating” broadband infrastructure is defined as managing, monitoring, and controlling existing broadband networks or infrastructure through which broadband services are being delivered.

If you do not have the necessary experience, provide contact information for the contractor who has experience in both deploying and operating broadband infrastructure in Canada for a minimum of three years and a description of the contractor’s experience. You must also indicate if the contractor will deploy and/or operate the broadband infrastructure.

NOTE: Experience in deploying and operating broadband infrastructure should be related to the project type. For example, the CRTC will assess applicants proposing a mobile wireless project based on their experience with deploying and operating mobile wireless broadband infrastructure in Canada.

You must upload any required supporting evidence at the end of this section:

  • Contract or other evidence that the contractor with experience both deploying and operating broadband infrastructure in Canada for a minimum of three years has agreed to provide services for the project.

5. Documents

Appendix 1(a) – Legal Status and Carrier Status. Appendix 1(a) documents must use the following naming convention: Appendix 1(a) – Document number – Legal Status and Carrier Status.

Appendix 2 – Financial Solvency. Appendix 2 documents must use the following naming convention: Appendix 2 – Document number – Financial Solvency.

Appendix 3 – Contractual Arrangement. Appendix 3 documents must use the following naming convention: Appendix 3 – Document number – Contractual Arrangement.

A. Group Entity Applicant Details

1. Applicant Details

Provide details about the applicant in this section. Details about the other members in the Group Entity will be provided in A1. Member Details.

1.1 Applicant Details

Space will be provided to indicate the applicant details.

1.2 Role

You must specify the applicant’s role in the project with respect to the network as one or more of the following: Owner, Deployment, Operator and/or Other. If you select Other, describe the role.

You must upload any required supporting evidence at the end of this section:

  • A description of the roles and responsibilities of the applicant and each member of the joint venture, partnership, or consortium, including ownership of assets, network builder, service provider, and dispute resolution mechanisms. For example, you must identify which entity will retain ownership of the network assets, which entity will be responsible for building the network, and which entity will be responsible for the network’s operation. Demonstrate this by filing the contractual arrangements, partnership agreements, or other legal documentation that creates the applicant entity and describes the various roles and responsibilities of each member.

2. Contact

Provide contact information for the applicant’s primary contact and for an alternate executive contact.

  • Primary contact: an authorized official – someone with authority to bind the organization to the commitments made in the application and to the resulting funding agreements if the project is selected.
  • Alternate contact: an additional contact who can be reached in case the primary contact is unavailable, preferably an executive level individual.

3. Legal Status, Carrier Status and Financial Solvency

3.1 CRTC Master Address Database (MAD) and Data Collection System

Identify if the applicant has a MAD number, and if so, provide the number.

If you provided a MAD number, you must indicate if you consent to the CRTC reviewing submissions made to the CRTC DCS, in order for it to verify the documentation provided by the applicant.

3.2 Legal Status

Applicants must be a legal entity to be eligible to apply. Applicants will be asked to provide evidence showing that the entity legally exists and is of the selected type.

If the applicant is a registered entity, indicate the jurisdiction in which it is registered. If the applicant is Provincial/Territorial, specify the Province/Territory.

For all applicants, space will be provided to indicate the Business Number.

You must upload any required supporting evidence at the end of this section, even if you provided a MAD number and consented to the CRTC reviewing submissions made to the CRTC DCS:

  • Evidence of the legal status of the applicant, including, where applicable, the legal relationship between the applicant’s constituent members. Such evidence should include a copy of registration and key constituting documents, such as a certificate of incorporation, Canada Revenue Agency registration, and proof of registration of not-for-profit status or band number.
  • The ‘Member details’ section of this application form must include information for each member of the group.

3.3 Carrier Status

You must indicate if the applicant is eligible to operate as a Canadian carrier pursuant to section 16 of the Telecommunications Act.

If the applicant is not eligible to operate as a carrier, this section is complete and you will be reminded that you must identify at least one member of the partnership, joint venture or consortium as eligible to operate as a Canadian carrier in the Member Details section.

3.4 Financial Solvency

The applicant, except for provincial, territorial and municipal governments, must confirm that it, or each member of the applicant partnership, joint venture, or consortium, is financially solvent and reliable in accordance with the Generally Accepted Accounting Principles of Canada. Refer to section 14 of the Application Guide for definitions of “solvent” and “reliable.”

Indicate if the applicant is financially solvent and reliable:

  • If the applicant is not financially solvent and reliable, this section is complete and you will be reminded that the applicant or each member of the partnership, joint venture or consortium must be financially solvent and reliable in accordance with the Generally Accepted Accounting Principles of Canada.
  • NOTE: It is strongly recommended that applicants upload each fiscal year’s financial statements as separate upload files.
  • NOTE: This information will also be requested in the Member Details form for each of the applicant’s members that are not a provincial, territorial, or municipal government entity.

You must upload any required supporting evidence at the end of this section, even if financial solvency information is available in DCS:

  • A copy of independently prepared (including audited, review engagement, or notice to reader) financial statements (balance sheet, income statement, and cash flow statement, including financial statement notes and, if audited, the auditor’s report and opinions of the financial statements) for the last three calendar years.
  • NOTE: This information will also be requested in the Member Details form for each of the applicant’s members that are not a provincial, territorial, or municipal government.

4. Experience

Indicate whether the applicant or at least one member of the partnership, joint venture or consortium has three or more years of experience both deploying and operating broadband infrastructure in Canada. If the applicant or one of its members has the experience you must identify the entity and describe that experience in a few sentences and include information on where and how long the broadband services were provided, as well as the number of customers they currently serve.

For the purpose of the Broadband Fund, “deploying” broadband infrastructure is defined as constructing and implementing broadband networks or infrastructure through which broadband services will be delivered, and “operating” broadband infrastructure is defined as managing, monitoring, and controlling existing broadband networks or infrastructure through which broadband services are being delivered.

If you do not have the necessary experience, provide contact information for the contractor who has experience in both deploying and operating broadband infrastructure in Canada for three or more years and a description of the contractor’s experience. Indicate if the contractor will deploy and/or operate the broadband infrastructure.

NOTE: Experience in deploying and operating broadband infrastructure should be related to the project type. For example, the CRTC will assess applicants proposing a mobile wireless project based on their experience with deploying and operating mobile wireless broadband infrastructure in Canada.

NOTE: Applicants must provide details of each group member’s experience deploying and operating broadband infrastructure in Canada in this section. The Online Application Form does not provide applicants with the opportunity to provide such details in the A1. Member Details section.

You must upload any required supporting evidence at the end of this section:

  • Contract or other evidence that the contractor with experience both deploying and operating broadband infrastructure in Canada for a minimum of three years has agreed to provide services for the project.

5. Documents

Appendix 1(a) – Legal Status and Carrier Status. Appendix 1(a) documents must use the following naming convention: Appendix 1(a) – Document number – Legal Status and Carrier Status.

Appendix 1(b) – Roles and Responsibilities of Members of Group. Appendix 1(b) documents must use the following naming convention: Appendix 1(b) – Document number – Roles and Responsibilities.

Appendix 2 – Financial Solvency. Appendix 2 documents must use the following naming convention: Appendix 2 – Document number – Financial Solvency.

Appendix 3 – Contractual Arrangement. Appendix 3 documents must use the following naming convention: Appendix 3 – Document number – Contractual Arrangement.

A1. Member Details

1. Member Information

Provide details about each member and their role in the project in this section.

1.1 Member Details

Indicate the member details in the space provided.

1.2 Role

You must specify the member’s roles in the project with respect to the network as one or more of the following: Owner, Deployment, Operator, and/or Other. If you select Other, describe the role.

NOTE: The Application Form does not provide applicants with the opportunity to provide details of the experience that each member has in deploying and operating broadband infrastructure in Canada. Applicants must provide details of each group member’s experience deploying and operating broadband infrastructure in Canada in the A. Group Entity Applicant Details section.

2. Legal Status, Carrier Status and Financial Solvency

2.1 CRTC Master Address Database (MAD) and Data Collection System

Identify if the member has a MAD number, and if so, provide the number.

If you provided a MAD number, you must indicate if you consent to the CRTC reviewing submissions made to the CRTC Data Collection System (DCS), in order to verify documentation provided by the applicant.

2.2 Legal Status

Each member must be a legal entity to be eligible to apply. You will be asked to provide documents to show the legal status of the member.

If the member is a:

  • Band Council or Indigenous Government: space will be provided to indicate their Band Number or Band ID, if applicable.
  • Canadian Corporation: the jurisdiction in which the corporation is registered must be identified as Provincial/Territorial or Federal. For a Provincial/Territorial corporation you must specify the Province/Territory from a drop-down list. Enter the provincial Corporation Number, Business Identification Number or other appropriate registration number identifying the Corporation in the space provided.

You must upload any required supporting evidence at the end of this section:

  • Evidence of the legal status of the member. Such evidence should include a copy of registration and key constituting documents, such as a certificate of incorporation, Canada Revenue Agency registration, and proof of registration of not-for-profit status or band number, if applicable.

2.3 Carrier Status

You must indicate if the member is eligible to operate as a Canadian carrier pursuant to section 16 of the Telecommunications Act.

If the member is not eligible to operate as a carrier, this section is complete and you will be reminded that you must identify the partnership, joint venture or consortium or at least one member of the applicant as eligible to operate as a Canadian carrier in that entity’s details section of the application.

2.4 Financial Solvency

The applicant, except for provincial, territorial and municipal governments, must confirm that it, or each member of the applicant partnership, joint venture, or consortium, is financially solvent and reliable in accordance with the Generally Accepted Accounting Principles of Canada. Refer to section 14 of the Application Guide for definitions of “solvent” and “reliable.”

You must indicate if the member is financially solvent and reliable.

  • If the member is not financially solvent and reliable, this section is complete and you will be reminded that the applicant or each member of the partnership, joint venture or consortium must be financially solvent and reliable in accordance with the Generally Accepted Accounting Principles of Canada.

You must upload any required supporting evidence at the end of this section, even if financial solvency information is available in DCS:

  • A copy of independently prepared (including audited, review engagement, or notice to reader) financial statements (balance sheet, income statement, and cash flow statement, including financial statement notes and, if audited, the auditor’s report and opinions of the financial statements) for the last three calendar years.
  • NOTE: This information will also be requested in the Member Details form for each of the applicant’s members that are not a provincial, territorial or municipal government.

3. Documents

Appendix 1 (a) – Legal Status and Carrier Status. Appendix 1(a) documents must use the following naming convention: Appendix 1(a) – Document number – Legal Status and Carrier Status.

Appendix 2 – Financial Solvency. Appendix 2 documents must use the following naming convention: Appendix 2 – Document number – Financial Solvency.

B. Project Details

1. Project Description

In this section you will be asked to provide general details about your project.

Provide a new project name if you wish to change the current project name. You may wish to change the name of the project if you copied application information in order to submit multiple applications. If you do not want to change the name of the project from the name initially indicated, then leave this field blank.

Provide a brief description of the type of project, the overall geography for the project, and the technology you intend to deploy. If you are proposing a transport project, briefly describe the current state of transport service in the area and why there is a need to upgrade the transport infrastructure in that area.

Provide information on the proposed project timeline. These dates are intended to assist the CRTC in forecasting how long it will take for the project to be completed once approved:

  • Identify the project start timeframe by indicating the number of months after the publication of the CRTC funding award decision construction for the project would commence.
  • Identify the project construction timeframe by indicating the number of years for construction to be completed and service to be operational in all proposed areas.
  • A space will be provided to describe the key dependencies or factors that will affect the start timeframe and construction timeframe. You must state all assumptions made as part of your forecast.
  • NOTE: For projects selected for funding, a detailed schedule will be determined as part of the Statement of Work following project selection.

Identify which provinces and/or territories will receive improved broadband service as a result of the project. If a project crosses a provincial or territorial boundary, you may identify more than one.

Applicants are reminded that projects cannot be contingent on one another, with one exception due to constraints with the application tools. If an applicant wishes to propose a project affecting a satellite-dependent community that would draw from both the main component (for example, a transport project) and the satellite component (a project to increase satellite transport capacity [operational costs]) of the Fund, it must submit two separate and complete project applications: one for the main component and one for the satellite component. In each application, reference the other application in the Project Description. The CRTC will consider the two projects to be complementary projects, and therefore not improperly contingent on one another.

You must upload any required supporting evidence at the end of this section:

  • The Application Workbook supplied by the CRTC must be used to provide the details of the project. All required sections must be completed in full according to the instructions provided in the Workbook.
  • If you are proposing a project affecting a satellite-dependent community that would draw from both the main component and the satellite component of the Fund, ensure that you submit two separate and complete project applications, each with its own separate, complete, and independent Application Workbook.

2. Project Type and Components

Identify if your project would draw from the main component of the Fund or if your project serves satellite-dependent communities. Note that applications for the main component of the Fund and applications that intend to serve satellite-dependent communities must be filed in separate applications.

If you wish to propose a project affecting a satellite-dependent community that would draw from both the main component (for example, a transport project) and the satellite component (a project to increase satellite transport capacity [operational costs]) of the Fund, ensure that you submit two separate and complete project applications: one for the main component and one for the satellite component.

2.1 Application for a project for the main component of the Fund

If you are applying with a project for the main component of the Fund, select the applicable project components (Transport and/or Mobile) and enter the associated data. Values must match the Application Workbook data. This data will be captured in the Dashboard Tab under Technical Summary in the Application Workbook.

  • Transport Component: Number of new points of presence (POPs) serving eligible communities; Number of upgraded POPs serving eligible communities; Number of new or upgraded POPs built along the route as part of this project; Confirmation that each new and upgraded POP along the route will offer wholesale open access service at one of the required service speeds, as well as retail open access service; Number of anchor institutions intended to be served; Number of communities to be served; and Number of households to be served.
  • Mobile Component: Whether the mobile network created by this project will offer LTE, LTE-A, or 5G service; Number of kilometres of eligible roads that have access to this generation of mobile service available as a result of this project; Confirmation that the project will provide mobile service using the specified technology to all roads intended to be served in eligible areas.

You must upload any required supporting evidence at the end of this section:

  • Any documentation, if available, providing evidence of support by anchor institutions intended to be served, for example, in the form of letters, contracts, or emails.

2.2 Application for the satellite component of the Fund

If you are applying for funding for a project that serves satellite-dependent communities, select the applicable project components and enter the associated data.

  • Transport capacity-increase project (operational costs): application for funding to cover annual operational costs, over a certain amount of time (for up to five years), to increase satellite transport capacity to satellite-dependent communities.
  • NOTE: The CRTC recognizes that operational funding is a necessity for satellite-dependent communities. Considering the general uncertainty regarding the availability of alternatives to conventional satellite services, including the availability of low earth orbit (LEO) satellite services, applicants are encouraged to apply for five years of operational funding. Note that the requested funding amount and/or duration, if approved by the CRTC, can be reduced in the future if it is no longer required.

Satellite-dependent Community Information:

  • Indicate how many satellite-dependent communities will be served by this project.
  • Indicate the number of households in the eligible communities that will have access to improved services as a result of this project.
  • Confirm that the applicant will commit to maintaining the service plans and prices proposed in the Application Workbook for the same amount of time that funding is provided for operational costs to increase transport capacity.

You must upload any required supporting evidence at the end of this section:

  • Comparator service plans and prices for satellite-dependent communities offered by a facilities-based service provider in Iqaluit, Nunavut.
  • A copy of the satellite transport capacity contract or memorandum of understanding with the satellite transport provider.

3. Technical Merit and Mapping data

3.1 Network Description and Technical Merit

At the end of this section you will be required to upload your Logical Network Diagram (LND). You must ensure that each element of the LND is clearly labeled and corresponds appropriately to the information that you provide in the Online Application Form and the Application Workbook. This will assist the CRTC in reconciling different sources of information.

For further details on the LND requirements, refer to the guidance provided below, following the Network Description guidance.

The information that you provide in this section should not contain any marketing information. It should assist the CRTC in understanding the technical functionality of the project in support of the eligibility and assessment criteria.

Applicants are reminded that the CRTC is placing increased emphasis, during the assessment phase, on resiliency, and will therefore use special increased weighting of the resiliency aspect of the Technical merit (2-P1) assessment criterion. You must explain in this section how your proposal includes an increased focus on resiliency (a Resiliency Project). Additional information, if more space is required, can be submitted in Appendix 11: Other Documents.

System Design Description (max 4000 characters)

  • This description should assist the CRTC in understanding and evaluating the high level technical design, end-to-end functionality, and capability of the system that you are proposing to build.
  • Describe the high level system design of the project, including a comprehensive explanation of the LND, key assumptions, and key technical dependencies. For example, provide a general description of the responsibilities of each of the network elements and how they interact with one another. You are encouraged to include key details about the forecasted number of subscribers, designed speeds, assumptions on typical and peak network utilisation, and planned quality of service objectives (latency, jitter, and packet loss).

Feasibility Description (max 2000 characters)

  • This description should assist the CRTC in ensuring that you have considered the most suitable technology to be deployed, the project’s ability to meet the minimum capacity requirements of the Broadband Fund, and how those technologies overcome any specific limitations or constraints related to the geographic area.
  • Describe how the chosen technologies will meet the minimum capacity requirements, provide the proposed coverage, and deliver the proposed services submitted in the application.
  • Outline any limitations with the proposed technology.
  • Identify any project dependencies beyond those included in the system design description. If applicable, provide details on how these dependencies will be addressed in an efficient and timely manner. You are reminded that your project will be assessed on its own merit and cannot be contingent on the successful funding of another project.
  • NOTE: If applicable, provide specific descriptions for each component in your project (transport, and/or mobile and/or satellite transport capacity [operational costs]).

Scalability Description (max 2000 characters)

  • This description should assist the CRTC in evaluating the scalability of the project beyond what is initially being proposed.
  • Describe any future intentions to provide, as applicable to the project type, higher speeds, greater capacity, and improved quality of service. Provide details on how you plan to scale to serve more clients and/or a larger coverage area following project completion.
  • For transport and mobile projects, details to scale for the five years following project completion will be considered of higher quality. For projects applying for satellite transport capacity (operational costs), include plans covering the duration of the requested operational funding, as well as any plans immediately following the planned end of that funding.
  • NOTE: If applicable, provide specific descriptions for each component in your project (transport and/or mobile and/or satellite transport capacity [operational costs]).

Sustainability Description (max 2000 characters)

  • This description should assist the CRTC in ensuring that your project will remain useable and serviceable into the future and that you have considered the risks and customer impacts associated with maintenance, robustness, and upgradeability.
  • Describe the viability of your project’s proposed technologies, including whether the project proposes to make use of current and widely adopted technologies, the end of life expectancy of those technologies, and how the technologies will complement and/or replace the current infrastructure. Where available, include details specific to the vendor and the equipment selected.
  • NOTE: If applicable, provide specific descriptions for each component in your project (transport and/or mobile and/or satellite transport capacity [operational costs]).

Resiliency Description (max 2000 characters)

  • This description should assist the CRTC in ensuring that the risks inherent in your design have been evaluated and mitigated. The CRTC will also evaluate the inherent resilience of the proposed network and/or how the project would improve the resilience of existing infrastructure.
  • Describe your project’s potential points of failure and key remediation plans that you plan on implementing.
  • Describe key redundant network elements in your design. For example, what is planned to mitigate or eliminate the risk of equipment failure?
  • Explain your network’s ability to maintain an acceptable level of service during network failures and challenging conditions, including physical failures such as fibre cuts, equipment malfunction, adverse weather, or other unforeseen circumstances. For example: What happens if a key piece of equipment fails? What happens in the case of power loss?
  • Provide information on response and repair plans. For example, how do you plan to respond to problems? What is your planned mean time to respond, recover and/or repair?
  • NOTE: If applicable, provide specific descriptions for each component in your project (transport and/or mobile wireless and/or satellite transport capacity [operational costs]).

You must upload any required supporting evidence at the end of this section.

Resiliency Focused Project Justification

If you have indicated that your project has put an additional and concentrated focus on increasing the resiliency of existing telecommunications infrastructure, you must clearly demonstrate in this section how the project is improving resiliency to a geographic area or to an existing network, while still meeting all project eligibility criteria for the project type for which you are applying.

Clearly demonstrate how your project will increase the resiliency of existing telecommunications infrastructure by building high-capacity transport infrastructure that, for example:

  • While upgrading or building transport POPs in eligible communities or while providing wireless coverage on eligible major transportation roads, builds a redundant data path for existing transport infrastructure by (a) introducing geographic redundancy; or (b) creating a transport ring or loop; or
  • Builds high-capacity transport infrastructure to establish a new or upgrade an existing POP in an eligible transport community that is also a satellite-dependent community, thereby reducing or eliminating the community’s reliance on satellite transport capacity; or
  • Replaces less resilient transport infrastructure with more resilient transport infrastructure, for example by introducing fibre optic transport where only microwave transport exists, when upgrading the capacity at a POP in any eligible transport community.

Logical Network Diagram

The Logical Network Diagram (LND) should clearly identify the following information as well as provide a clear relation to the map data and the Application Workbook. Multiple diagrams may be submitted.

  • Identify project sites including project interconnection points, access points (wireline, fixed wireless and mobile wireless), POPs, Transport Transit Sites, Anchor Institution Sites and Satellite Earth stations as applicable. The Site ID provided in the Application Workbook must be referenced on the LND.
  • For each site identified above, identify all major network elements from the Application Workbook – Eligible Equipment List. The manufacturer/model provided in the Application Workbook must be referenced on the LND.
  • Identify all Routes connecting sites above. Show link speed, types (fiber, copper, wireless) and network paths. The Route ID provided in the Application Workbook must be referenced on the LND.
  • Include capacity (up/down) for each link and overall network.
  • Identify sections of the network that currently exist, are to be built, and/or will be upgraded.
  • Identify network resiliency capabilities; the diagram must clearly indicate which sections of the network are to provide resiliency.
  • Identify open access points (if applicable).
  • Provide a legend with icons and colours.

3.2 Mapping Data

Note: For more detailed instructions and guidance on using the CartoVista tools visit the CartoVista support website directly.

Viewing the eligibility data

From the Call 3 Eligibility Map launch page, click the map thumbnail to open the CartoVista Call 3 Eligibility Map in a new tab. The map shows eligible transport communities, satellite-dependent communities, and eligible roads for the third call for applications.

CartoVista interactive panes

CartoVista has four main panes: A) the map interface pane, B) the search and information pane,
C) the legend pane, and D) the data and selection pane.

Figure 1. Full-screen view of CartoVista and identifiers for the interactive panes.
Figure 1 : Full-screen view of CartoVista and identifiers for the interactive panes.

A. Map interface pane

The map interface is where you can view and interact with the map. You can click and drag within the map interface to pan around the map, or use your scrollbar to zoom in and out.

The toolbar in the top left corner of the map interface contains mapping tools that can be used to interact, control and select objects within the map interface. Each of these tools will be explained in the subsequent section.

Mapping tools

Figure 2. Mapping tools.
Figure 2 : Mapping tools.
Figure 2. Outils de cartographie.
Navigation
Initial extents Initial extents: Return to the initial view of the map.
Previous/Next View Previous/Next View: Return to the previous/next view of the map.
Pan: Grab and drag to move around the map.
Zoom in/out Zoom in/out: Click on the map to display a closer/wider view of the map. You can also draw a rectangle on the map to closely define the area you want to zoom to. In addition, you can use the mouse scroll wheel to zoom in (scroll towards the top).
Measure
Ruler Ruler: Define a path on the map to calculate the distance between 2 locations and the cumulative distance along the whole line. When you are done, double-click to end.
Search
Info: Click on a specific point on the map. The information for all the features intersecting with that location will be displayed in the Information panel (B). In addition, an icon will be displayed where you clicked to identify the map feature(s) for which information is available.
Selection
Selection, Rectangular selection

Selection: By clicking the dropdown, access the selection menu and select the layer you want to query and a selection tool (see below). The selected features will be highlighted on the map and their rows will be displayed in the Selection panel (D). If you wish to expand the current selection, use the SHIFT or CONTROL key while selecting more map features on the map or in the data panel.

Rectangular selection: Draw a rectangle on the map to select multiple features. The rectangle width and height are displayed as an info tip as you draw.

Simple selection Simple selection: Select a single map feature.
Circular selection Circular selection: Draw a circle on the map to select multiple features. The circle radius is displayed as an info tip as you draw.
Polygonal selection Polygonal selection: Draw a free form polygon on the map to select multiple features and double-click to end.
Unselect all Unselect all: Unselect all map features.

B. Search and information pane

Search: Locate a specific map feature using that feature's attribute and typing it into the search bar. Use the dropdown list to select the layer you want to search.

Information: Access information about the map features that intersect with a specific point on the map and display the coordinates. This information is displayed once you click on the map with the Info tool (see Mapping Tools).

Figure 3. Search and information pane showing the list of Eligible Transport Communities. Navigate to the layers dropdown menu by clicking the down arrow to the right of “Eligible Transport Communities”.
Figure 3. Search and information pane showing the list of Eligible Transport Communities. Navigate to the layers dropdown menu by clicking the down arrow to the right of “Eligible Transport Communities”.

C. Legend pane

Legend: View the symbols that identify the features found on the map or use the checkboxes to display or hide a layer in the map interface. The legend pane also allows you to turn layers on the map on or off by toggling the checkboxes beside each layer.

Figure 4. Legend pane showing the symbols, layer titles, and display/hide checkboxes.
Figure 4. Legend pane showing the symbols, layer titles, and display/hide checkboxes.

D. Data and selection pane

Figure 5. Data and selection pane pointing out the layers dropdown list and the data and selection tools.
Figure 5. PData and selection pane pointing out the layers dropdown list and the data and selection tools.

Data: View the data set for each layer of the map. Select the layer of interest from the layers dropdown list (highlighted in red in the top left corner of the Data and Selection pane). The Data panel's tab indicates the total number of features of the current layer between the brackets.

Selection: View the list of selected map features. The Selection panel’s tab indicates the total number of features that are selected between the brackets.

Data and selection tools

The data and selection tools can provide additional information, adjust the settings, and be used to export the data. The data and selection tools are located in the top right corner, highlighted in red in Figure 5 above and are described below.

 

Figure 6. Data and selection tools.

Copy data to the clipboard.

Copy data to the clipboard.

Show or hide the data statistics.

Show or hide the data statistics.

Clear all filters for the current layer.

Clear all filters for the current layer.

Export the data to a spreadsheet. You need to specify a file as the output.

Export the data to a spreadsheet. You need to specify a file as the output.

Access the Data Settings.

Access the Data Settings.

Selecting and exporting data for use in the Application Workbook

CartoVista can be used to help fill out the yellow Eligible Transport, Mobile Roads, and Satellite Geography tabs of the Application Workbook.

Selecting the data

  1. Use the navigation mapping tools to navigate to the desired project area within the map interface pane.
  2. Click the dropdown arrow in the selection tool button, which will display other selection tool options and a “From:” layer dropdown menu.
  3. Click the “From:” dropdown menu to select the layer from which you are selecting objects.
  4. When selecting multiple objects at once, use the rectangular, circular, or polygonal selection tools.

Note: It is only possible to select objects and export data from one layer at a time.

Figure 7. Dropdown menu displaying other selection tool options and a “From:” layer dropdown menu. Navigate to this menu by clicking the dropdown arrow in the selection tool button.
Figure 7. Dropdown menu displaying other selection tool options and a “From:” layer dropdown menu. Navigate to this menu by clicking the dropdown arrow in the selection tool button.

Export the Data

  1. The selected data will be displayed in the selection tab in the data and selection pane.
  2. Use the data and selection tools to export the data to a spreadsheet.
Use the exported data in the Application Workbook

The exported spreadsheet data from CartoVista can be used to fill out the first columns of the ‘Eligible Transport’ tab, the ‘Mobile Roads’ tab, and the ‘Satellite Geography’ tab in the Application Workbook.

Figure 8. ‘Eligible Transport’ tab in the Application Workbook.
Figure 8. ‘Eligible Transport’ tab in the Application Workbook.
Figure 9. ‘Mobile Roads’ tab in the Application Workbook.
Figure 9. ‘Mobile Roads’ tab in the Application Workbook.
Figure 10. ‘Satellite Geography’ tab in the Application Workbook.
Figure 10. ‘Satellite Geography’ tab in the Application Workbook.

Create your Maps

The eligibility data and mapping templates for the layers you are required to submit with your application can be downloaded from the Call 3 Eligibility Map page. The data and templates are packaged according to the format that is most easy for you to use. If you are using GIS software that works with Esri’s .shp format or MapInfo’s .tab format, do not download or submit your data in Google’s .kml/.kmz formats. Only download the .kml/.kmz format if you must use Google Earth Pro to complete the mapping component of your application. If you plan to submit multiple projects, ensure that each project has a unique name and note that the underscore is the only special character you may use when naming your files.

If you must use Google Earth Pro, note the following:

  • Change the default Lat/Long format to decimal degrees format by clicking Tools -> Options, then selecting the “Decimal Degrees” radio button under “Show Lat/Long”.
  • When first opening files in Google Earth Pro, the files will appear in the “Temporary Places” folder. To save your mapping data, make sure to right-click on your file and click Save to My Places. Saved files can then be found in the “My Places” folder.
  • If you plan to submit multiple projects, save the map templates file to the “My Places” folder. Then, right-click on the file and click Rename. Finally, click File -> Save -> Save Place As and note the save location.
  • If you are returning to the same project file to edit it, open the project file from the above-noted save location by double-clicking the .kml/.kmz file.

Download Before Beginning

Note: Ensure that you download the correct format of the map templates and eligibility data for your particular GIS software. Please note that Esri’s .shp format has a 10 character limit for their attribute fieldnames. The mapping between the shortened Esri fieldnames and the full length Application Workbook fieldnames are available in the README.txt file inside the zip download for shapefiles.

The following instructions are for a Transport-Mobile Project in which there are both Transport and Mobile Components. If the proposed project is a Transport-only Project or a Mobile-only Project, follow the instructions for those individual components.

Set up your workspace

  1. Open the map templates and eligibility data files in GIS software
  2. Locate the community or area that the proposed project intends to serve in the map interface

How to Create Mapping Data for a Transport-Mobile Project

A. Create your Transport Component

The transport component of the proposed network must include the following layers:

The layers should be named as below, including the underscore. Applicants are free to add unique identifiers after the underscore (e.g. Sites_Project123).

  1. Sites_
  2. Routes_

1. Sites_ Layer (Transport Component)

The Transport ‘Sites_’ layer must contain points that display the POPs, project interconnection points, Transit Sites, Anchor Institutions, and all other sites related to the transport component of the proposed network. If you chose to include existing facilities in the network, the attribute name needs to identify it as existing (e.g. by adding “_Existing” to the Site ID).

Note: the ‘Sites_’ layer must contain point objects only.

Ensure that you have downloaded and brought in the Eligible Transport Communities eligibility data for use in the GIS Software. To create the Transport ‘Sites_’ layer create a point and place it on the map, following the geographic eligibility criteria as outlined in Section 6.13 (a) of the Application Guide, if applicable for that site. When the point is placed, you must also supply the attribute information for the site you just created. If you are using Google Earth Pro, ensure that the ‘Sites_’ folder is selected before placing a placemark and use the Name field to add the attribute information. If you added a placemark outside of the ‘Sites_’ folder, drag and drop the placemark into the ‘Sites_’ folder.

The text in the Site ID attribute field must match the ‘Site ID’ identified in the ‘Site List’ tab in the Application Workbook.

Figure 11. Example mapping data displaying four sites for a Transport-Mobile Project. In this example you can see three POPs (labelled POP1, POP2, and POP3) and the project interconnection point (labelled PIP).
Figure 11. Example mapping data displaying four sites for a Transport-Mobile Project. In this example you can see three POPs (labelled POP1, POP2, and POP3) and the project interconnection point (labelled PIP).
Figure 12. ‘Site ID’ column from the ‘Site List’ tab in the Application Workbook for the mapping data example above. Note that the Site ID attribute in the mapping data matches the ‘Site ID’ in the ‘Site List’ tab in the Application Workbook.
Figure 12. ‘Site ID’ column from the ‘Site List’ tab in the Application Workbook for the mapping data example above. Note that the Site ID attribute in the mapping data matches the ‘Site ID’ in the ‘Site List’ tab in the Application Workbook.

2. Routes_ Layer (Transport Component)

The Transport ‘Routes_’ layer must contain lines that display the wired and wireless Network Paths such as Fiber Routes or Microwave Links between sites related to the transport component of the proposed network.

Note: the ‘Routes_’ layer must contain line objects only.

To create the Transport ‘Routes_’ layer, create a line on the map. When the line is placed, you must also supply the attribute information for the route you just created. If you are using Google Earth Pro, use the Name field to add the attribute information. The Transport ‘Routes_’ layer should connect transport sites. The example below shows how Route1 connects the project interconnection point and POP1, Route2 connects POP1 and POP2, and Route3 connects POP2 and POP3. If you choose to include existing routes in the network, the attribute name needs to identify it as existing (e.g. by adding “_Existing” to the Route ID).

Figure 13. Example mapping data displaying three routes that connect the sites.
Figure 13. Example mapping data displaying three routes that connect the sites.

The text in the Route ID attribute field must match the ‘Route ID’ identified in the ‘Route List’ tab in the Application Workbook. Ensure that the ‘Start Site ID’s and ‘End Site ID’s exist in the ‘Site ID’ column in the ‘Site List’ tab of the Application Workbook.

Figure 14. ‘Route ID’ column from the ‘Route List’ tab in the Application Workbook for the mapping data example above. Note that the Route ID attribute in the mapping data matches the ‘Route ID’ in the ‘Route List’ tab in the Application Workbook.
Figure 14. ‘Route ID’ column from the ‘Route List’ tab in the Application Workbook for the mapping data example above. Note that the Route ID attribute in the mapping data matches the ‘Route ID’ in the ‘Route List’ tab in the Application Workbook.

B. Create your Mobile Component

The mobile component of the proposed network must include the following layers:

The layers should be named as below, including the underscore. Applicants are free to add unique identifiers after the underscore (e.g. MobileSignals_Project123).

For combination projects like Transport-Mobile projects, you can use the same Site_ and Routes_ layer for features of both the mobile and transport components.

  1. Sites_
  2. Routes_ (if applicable)
  3. MobileSignals_
  4. MobileRoads_

1. Sites_ Layer (Mobile Component)

For Transport-Mobile Projects, add your mobile sites to the Transport ‘Sites_’ layer. The layer must contain points to display the Mobile Wireless Access Points, project interconnection points, and all other sites related to the mobile component of the proposed network. If you chose to include existing facilities in the network, the attribute name needs to identify it as existing (e.g. by adding “_Existing” to the Site ID).

Note: When creating a Mobile-only Project, create a ‘Sites_’ layer using the map templates to display the sites related to the mobile component of the proposed network. The ‘Sites_’ layer must contain point objects only.

To create the Mobile ‘Sites_’ layer, create a point and place it on the map. When the point is placed, you must also supply the attribute information for the site you just created. If you are using Google Earth Pro, ensure that the ‘Sites_’ folder is selected before placing a placemark and use the Name field to add the attribute information. If you added a placemark outside of the ‘Sites_’ folder, drag and drop the placemark into the ‘Sites_’ folder.

The text in the Site ID attribute field must match the ‘Site ID’ identified in the ‘Site List’ tab in the Application Workbook.

Figure 15. Example mapping data displaying six sites for a Transport-Mobile Project. In this example you can see three POPs (labelled POP1, POP2, and POP3), the project interconnection point (labelled PIP), a transit site (labelled TransitSite1), and a tower (labelled Tower1).
Figure 15. Example mapping data displaying six sites for a Transport-Mobile Project. In this example you can see three POPs (labelled POP1, POP2, and POP3), the project interconnection point (labelled PIP), a transit site (labelled TransitSite1), and a tower (labelled Tower1).
Figure 16. ‘Site ID’ column from the ‘Site List’ tab in the Application Workbook for the mapping data example above. Note that the Site ID attribute in the mapping data matches the ‘Site ID’ in the ‘Site List’ tab in the Application Workbook.
Figure 16. ‘Site ID’ column from the ‘Site List’ tab in the Application Workbook for the mapping data example above. Note that the Site ID attribute in the mapping data matches the ‘Site ID’ in the ‘Site List’ tab in the Application Workbook.

2. Routes_ Layer (Mobile Component, if applicable)

For Transport-Mobile Projects, add your mobile routes to the Transport ‘Routes_’ layer. The layer must contain lines to display the wired/wireless Network Paths such as Fibre Routes or Microwave Links between all sites related to the mobile component of the proposed network.

Note: When creating a Mobile-only Project, create a ‘Routes_’ layer using the map templates to display the routes related to the mobile component of the proposed network. The ‘Routes_’ layer must contain line objects only.

To create the Mobile ‘Routes_’ layer, create a line on the map. When the line is placed, you must also supply the attribute information for the route you just created. If you are using Google Earth Pro, use the Name field to add the attribute information. The Mobile ‘Routes_’ layer should connect mobile sites or sites that are necessary to provide mobile service. If you choose to include existing routes in the network, the attribute name needs to identify it as existing (e.g. by adding “_Existing” to the Route ID).

The text in the Route ID attribute field must match the ‘Route ID’ identified in the ‘Route List’ tab in the Application Workbook. Ensure that the ‘Start Site ID’s and ‘End Site ID’s exist in the ‘Site ID’ column in the ‘Site List’ tab of the Application Workbook.

Figure 17. Example mapping data displaying five routes that connect the sites.
Figure 17. Example mapping data displaying five routes that connect the sites.
Figure 18. ‘Route ID’ column from the ‘Route List’ tab in the Application Workbook for the mapping data example above. Note that the Route ID attribute in the mapping data matches the ‘Route ID’ in the ‘Route List’ tab in the Application Workbook.
Figure 18. ‘Route ID’ column from the ‘Route List’ tab in the Application Workbook for the mapping data example above. Note that the Route ID attribute in the mapping data matches the ‘Route ID’ in the ‘Route List’ tab in the Application Workbook.

3. MobileSignals_ Layer

The ‘MobileSignals_’ layer should contain polygons showing mobile signal propagation, representing the proposed cellular coverage.

Terrain-based propagation models are preferred, but not required. If you do not have access to propagation modelling software, provide 2D vector shapes that best represent the proposed cellular coverage. Import the coverage polygon into the GIS software you are using.

Note: The ‘MobileSignals_’ layer should be provided as a vector layer and not a raster (.png, .jpg, .gif, .bmp, .tiff, etc.).

Figure 19. Example mapping data displaying a mobile signal propagation polygon and proposed network.
Figure 19. Example mapping data displaying a mobile signal propagation polygon and proposed network.

4. MobileRoads_ Layer

The ‘MobileRoads_’ layer should contain lines representing only the eligible road segments that the proposed cellular coverage will serve.

Ensure that you have downloaded and brought in the Eligible Roads eligibility data for use in the GIS Software. Create the ‘MobileRoads_’ layer by clipping the Eligible Roads layer by the ‘MobileSignals_’ polygons created above.

Note: The ‘MobileRoads_’ layer must contain line objects only and should only contain the eligible roads under the proposed cellular coverage.

If you are using Google Earth Pro, copy the eligible road segments to be served to the ‘MobileRoads_’ folder by right-clicking on the Eligible Road and clicking copy. Multiple road segments may be brought into the ‘MobileRoads_’ folder by using the SHIFT or CTRL keys to select multiple objects, dragging, and dropping the segments into the ‘MobileRoads_’ folder.

Figure 20. Example mapping data showing the Eligible Roads layer, the selection by the clipping tool, and the clipped Eligible Roads layer.
Example mapping data showing the Eligible Roads layer, the selection by the clipping tool, and the clipped Eligible Roads layer.
Example mapping data showing the Eligible Roads layer, the selection by the clipping tool, and the clipped Eligible Roads layer.
Example mapping data showing the Eligible Roads layer, the selection by the clipping tool, and the clipped Eligible Roads layer.

How to Create Mapping Data for a Satellite Project

A. Create your Satellite Component

The satellite operational expenses component of the proposed network must include the following layers:

  1. Sites_ (i.e. Earth Stations)

1. Sites_ Layer

The Satellite ‘Sites_’ layer must contain points that display the Earth Stations.

Note: The ‘Sites_’ layer must contain point objects only.

Ensure that you have downloaded and brought in the Satellite-dependent Communities eligibility data for use in the GIS Software. To create the ‘Sites_’ layer create a point and place it on the map, following the geographic eligibility criteria as outlined in Section 6.1.3 (j) of the Application Guide. When the point is placed, you must also supply the attribute information for the site you just created. If you are using Google Earth Pro, ensure that the ‘Sites_’ folder is selected before placing a placemark and use the Name field to add the attribute information. If you added a placemark outside of the ‘Sites_’ folder, drag and drop the placemark into the ‘Sites_’ folder.

If you chose to include existing facilities in the network, the attribute name needs to identify it as existing (e.g. by adding “_Existing” to the Site ID).

The text in the Site ID attribute field must match the ‘Site ID’ identified in the ‘Site List’ tab in the Application Workbook.

Figure 21. Example mapping data displaying one site for a Satellite Project.
Figure 21. Example mapping data displaying one site for a Satellite Project.
Figure 22. ‘Site ID’ column from the ‘Site List’ tab in the Application Workbook for the mapping data example above. Note that the Site ID attribute in the mapping data matches the ‘Site ID’ in the ‘Site List’ tab in the Application Workbook.
Figure 22. ‘Site ID’ column from the ‘Site List’ tab in the Application Workbook for the mapping data example above. Note that the Site ID attribute in the mapping data matches the ‘Site ID’ in the ‘Site List’ tab in the Application Workbook.

Mapping Data Checklist

A. Transport-only Project

Layers:

  • Sites_ (point objects only)
  • Routes_ (line objects only)

Attributes match Application Workbook IDs:

  • Site IDs match the ‘Site IDs’ in the ‘Site List’ tab in the Application Workbook
  • Route IDs match the ‘Route IDs’ in the ‘Route List’ tab in the Application Workbook
  • Start Site IDs and End Site IDs exist in the ‘Site List’ tab in the Application Workbook

B. Mobile-only Project

Layers:

  • Sites_ (point objects only)
  • Routes_ (if applicable, line objects only)
  • MobileSignals_ (polygon objects only)
  • MobileRoads_ (line objects only)

Attributes match Application Workbook IDs:

  • Site IDs match the ‘Site IDs’ in the ‘Site List’ tab in the Application Workbook
  • Route IDs (if applicable) match the ‘Route IDs’ in the ‘Route List’ tab in the Application Workbook
  • Road IDs match the ‘Eligible Road IDs’ in the ‘Mobile Roads’ tab in the Application Workbook

C. Transport-Mobile Project

Layers:

  • Sites_ (point objects only)
  • Routes_ (line objects only)
  • MobileSignals_ (polygon objects only)
  • MobileRoads_ (line objects only)

Attributes match Application Workbook IDs:

  • Site IDs match the ‘Site IDs’ in the ‘Site List’ tab in the Application Workbook
  • Route IDs match the ‘Route IDs’ in the ‘Route List’ tab in the Application Workbook
  • Start Site IDs and End Site IDs exist in the ‘Site List’ tab in the Application Workbook
  • Road IDs match the ‘Eligible Road IDs’ in the ‘Mobile Roads’ tab in the Application Workbook

D. Satellite Project

Layers:

  • Sites_ (point objects only)

Attributes match Application Workbook IDs:

  • Site IDs match the ‘Site IDs’ in the ‘Site List’ tab in the Application Workbook

4. Community Consultation Information

Using the List of Affected Communities template, provide a list of every community affected by the proposed project as identified in the Map of Communities and OLMCs. Instructions on how to use the Map of Communities and OLMCs are provided below.

Confirm that the applicant has consulted, or attempted to consult, with each community affected by this project.

Indicate if any of the communities affected by this project are an Official Language Minority Community (OLMC) or an Indigenous community. This information must correspond to the information provided in the List of Affected Communities template.

If the proposed project affects Indigenous communities, provide evidence of meaningful engagement with those affected communities. In order to be meaningful, engagement should be undertaken early, openly, and respectfully. Affected communities must be given the opportunity to learn about the project and communicate any concerns they may have. Demonstrated responsiveness to those concerns and evidence of collaboration with affected communities will be viewed favorably. (Maximum 7000 characters. Evidence can also be provided through an uploaded document, although the applicant should indicate if this is the case).

Indicate if the project presents a risk of an adverse impact to any established or asserted Aboriginal or treaty rights. Provide a description of the established or asserted Aboriginal or treaty rights that may be affected and how the applicant has consulted or will consult with affected Indigenous communities to address any potential adverse impacts. If the project does not present a risk of adverse impact to any established or asserted Aboriginal or treaty rights, provide evidence demonstrating how this consideration was informed. (Maximum 7000 characters).

NOTE: Applicants should consult Crown-Indigenous Relations and Northern Affairs Canada for more information on Indigenous communities. Applicants should also consult the Aboriginal and Treaty Rights Information System (ATRIS) to identify whether there are any treaties, claims, or assertions in a proposed project area, as well as whether any consultation protocols are in place.

Confirm that the applicant will undertake and provide evidence of any appropriate consultation that may be necessary with regard to any Aboriginal or treaty rights affected by this project, whether those rights and impacts are known now or become known in the future.

Upload any required supporting evidence at the end of this section:

  • A list of the communities affected by the project, including whether they include Indigenous communities or OLMCs, using the List of Affected Communities template and the Map of Communities and OLMCs provided in the application package.
  • Evidence of community consultation or attempted consultation, which may be in many forms. Consultation may be carried out through, for example, a telephone call, a virtual meeting, an in-person meeting, a notification letter, and a presentation made to community representatives, and such consultation should be documented. Community support may be demonstrated through, for example, a letter of support from community representatives, a resolution from a local governing body such as a municipal or a Band Council resolution, evidence of a community benefit agreement, the use of local companies during the project implementation, an agreement to train community residents, and investment by the community in the project.

4.1 Instructions on using the Map of Communities and OLMCs

Note: For more detailed instructions and guidance on using the CartoVista tools, visit the CartoVista support website directly.

Community consultation - Background

To be eligible for funding, an applicant must provide evidence that it has consulted or attempted to consult with all communities affected by the proposed project. Consultations can be direct or through community representatives. For example, in the case of Indigenous communities, they can be at the band council or Indigenous government level.

Applicants can use the provided Map of Communities and OLMCs to determine which communities may be affected by a proposed project. The instructions for using this map are provided below. To meet the Community consultation (1-P3) eligibility criterion, applicants must consult or attempt to consult with each community affected by the proposed project and provide evidence in the form of the following:

  • the List of Affected Communities, which is provided on the landing page of the Broadband Fund Application Form;
  • copies of all notification letters sent to affected communities and/or groups, demonstrating that each community and/or group has had a meaningful opportunity to discuss the project with the applicant; and
  • any responses received or any evidence (e.g. minutes from meetings or phone calls) demonstrating meaningful engagement or consultation with affected communities and/or groups, particularly with affected Indigenous communities and/or groups.

Applicants should note that the Map of Communities and OLMCs will not indicate whether a community is Indigenous. To determine if Indigenous groups may be affected by a proposed project, applicants should consult the Aboriginal and Treaty Rights Information System (ATRIS).

Applicants should also note that the Map of Communities and OLMCs lists all communities in Canada and not eligible areas for the various eligible project types. To determine which areas are eligible for funding, applicants must consult the Call 3 Eligibility Map.

Viewing the community data

From the Community consultation process and Indigenous and treaty rights page, click on the map thumbnail to open the Map of Communities and OLMCs. This will open CartoVista in a new tab.

CartoVista interactive panes

CartoVista has four main panes: A) the map interface pane, B) the search and information pane, C) the legend pane, and D) the data and selection pane.

Figure 23. Full-screen view of CartoVista and identifiers for the interactive panes.
Figure 23 : Full-screen view of CartoVista and identifiers for the interactive panes.

A. Map interface pane

The map interface is where you can view and interact with the map. You can click and drag within the map interface to pan around the map, or use your scrollbar to zoom in and out.

The toolbar in the top left corner of the map interface contains mapping tools that can be used to interact with, control, and select objects within the map interface. Each of these tools will be explained in the next section.

Mapping tools

Figure 24. Mapping tools
Figure 24 : Mapping tools, Navigation, Measure, Search, Selection
Outils de cartographie.
Navigation
Initial extents Initial extents: Return to the initial view of the map.
Previous/Next view Previous/Next view: Return to the previous/next view of the map.
Zoom in/out Zoom in/out: Click on the map to display a closer/wider view of the map. You can also draw a rectangle on the map to closely define the area you want to zoom to. In addition, you can use the mouse scroll wheel to zoom in (scroll towards the top).
Pan: Grab and drag to move through the map.
Measure
Ruler Ruler: Define a path on the map to calculate the distance between two locations and the cumulative distance along the whole line. When you are done, double-click to end.
Search
Info: Click on a specific point on the map. The information for all the features intersecting with that location will be displayed in the Information pane (B). In addition, an icon will be displayed where you clicked to identify the map feature(s) for which information is available.
Selection
Selection, Rectangular selection

Selection: By clicking on the dropdown, access the selection menu and select the layer you want to query from and a selection tool (see below). The selected features will be highlighted on the map and their rows will be displayed in the Selection pane (D). If you wish to expand the current selection, use the SHIFT or CONTROL key while selecting more map features on the map or in the Data pane (D).

Rectangular selection: Draw a rectangle on the map to select multiple features. The rectangle width and height are displayed as an info tip as you draw.

Simple selection Simple selection: Select a single map feature.
Circular selection Circular selection: Draw a circle on the map to select multiple features. The circle radius is displayed as an info tip as you draw.
Polygonal selection Polygonal selection: Draw a free form polygon on the map to select multiple features and double-click to end.
Unselect all Unselect all: Unselect all map features.

B. Search, information, and layer control pane

Search: Locate a specific map feature using that feature’s attribute and type it into the search bar. Use the dropdown list to select the layer you want to search.

Information: Access information about the map features that intersect with a specific point on the map and display the coordinates. This information is displayed once you click on the map with the Info tool (see the Mapping tools figure above).

Layer control: Manage the visibility, labelling, and opacity of each map layer.

Figure 25. Layer control pane showing the layer titles, display/hide checkboxes, and opacity controls
Figure 25 : Layer control pane showing the layer titles, display/hide checkboxes, and opacity controls

C. Legend pane

Legend: View the symbols that identify the features found on the map or use the checkboxes to display or hide a layer in the map interface.

Figure 26. Legend pane showing the symbols, layer titles, and display/hide checkboxes
Figure 26 : Legend pane showing the symbols, layer titles, and display/hide checkboxes

D. Data and selection pane

Figure 27. Data and selection pane showing the Layers dropdown list location and the Data and selection tools location.
Figure 27. Data and selection pane showing the Layers dropdown list location and the Data and selection tools location.

Data: View the data set for each layer of the map. Select the layer of interest from the Layers dropdown list (highlighted in red in the top left corner of the Data and selection pane). The Data tab indicates the total number of features of the current layer in parentheses.

Selection: View the list of selected map features. The Selection tab indicates the total number of features that are selected in parentheses.

Data and selection tools
The data and selection tools can provide additional information, adjust the settings, and be used to export data. The data and selection tools are located in the top right corner, highlighted in red in Figure 27 above and are described below.

Figure 28. Data and selection tools.

Copy data to the clipboard.

Copy data to the clipboard.

Clear all filters for the current layer.

Clear all filters for the current layer.

Export the data to a spreadsheet. You need to specify a file as the output.

Export the data to a spreadsheet. You need to specify a file as the output.

Access the Data Settings.

Access the Data Settings.

5. Summary of Project Costs

Provide a summary of the project costs in this section. These values must match the amounts listed in the Dashboard Tab under Technical Summary in the Application Workbook.

NOTE: Applicant investment must be a value greater than zero in order to be eligible for funding. Similarly, the total amount of funding requested cannot exceed the total eligible costs for the project.

In the event of any data discrepancy between this section and the Application Workbook, the Application Workbook data will be used.

You must upload the following documents at the end of this section:

  • High-level business marketing plan including a business overview outlining the demographic, economic and social factors of the area, a brief market analysis listing the size of the target market and existing competitors, and a brief sales and marketing plan outlining the plan to increase customers in the project’s geographic area. Include all supporting evidence and assumptions. Note that the financial statement tab in the Application Workbook provides the financial forecast for the project, therefore you do not need to include this in your business plan. For instructions on how to create elements of a business marketing plan, visit the BDC website.
  • Risk assessment and mitigation plan for the identified risks of the project, including the (i) risk of the applicant not completing the construction, (ii) environmental risk in the build (e.g. trench digging), and (iii) pricing risks in the supply of services and wholesale transport expenses, and (iv) if the applicant submits multiple applications for funding, an indication of whether the applicant can successfully implement all, or only a subset of, submitted applications within proposed timelines if more than one application is selected for funding.
  • If you are relying on credit to provide your investment in the project, provide a letter from your Chief Financial Officer/Chief Administrative Officer/Treasurer, a letter from a financial institution, or a Council Resolution of budget allocations to support your commitment of the investment amount you are proposing.

6. Documents

Appendix 4 – Application Workbook. Appendix 4 documents must use the following naming convention: Appendix 4 – Document number – Application Workbook.

Appendix 5a – Consultation Documents. Appendix 5a documents must use the following naming convention: Appendix 5a – Document number – List of Affected Communities.

Appendix 5b – Consultation Documents. Appendix 5b documents must use the following naming convention: Appendix 5b – Document number – Consultation.

Appendix 6a – Investment Documents. Appendix 6a documents must use the following naming convention: Appendix 6a – Document number – Business Marketing Plan.

Appendix 6b – Investment Documents. Appendix 6b documents must use the following naming convention: Appendix 6b – Document number – Risk Assessment and Mitigation Plan.

Appendix 6c – Investment Documents. Appendix 6c documents must use the following naming convention: Appendix 6c – Document number – Other Investment Documents.

Appendix 7 – Logical Network Diagram. Appendix 7 documents must use the following naming convention: Appendix 7 – Document number – Logical Network Diagram.

Appendix 8 – Satellite capacity agreements. Appendix 8 documents must use the following naming convention: Appendix 8 – Document number – Gateway Site Ownership or Lease Agreement.

Appendix 9 – Mapping data. Appendix 9 documents must use the following naming convention: Appendix 9 – Document number – Coverage Map.

Appendix 10 – Comparator services. Appendix 10 documents must use the following naming convention: Appendix 10 – Document number – Rates Brochure.

Appendix 11 – Other Documents. Appendix 11 documents must use the following naming convention: Appendix 11 – Document number – Other Documents.

B1. Third-Party Funding

If the project will receive funding or in-kind contributions from other sources, including other government funding programs or community grants, provide information on each source and the amount that was, or will be provided, or the value of the in-kind contribution.

You must manually add this section by clicking on the “Add Third-Party Funding Information” button at the bottom of the “Sections” section. You can add multiple versions of this section to accommodate multiple sources of third-party funding.

1.1. Funding Source

Name of funding program or source

Provide details of the source of funding

  • If you select Provincial or Territorial Government, select the jurisdiction from a drop-down list.
  • If you select Municipal government, select the jurisdiction from a drop-down list.
  • If you select Other, you will be provided with a space to provide further details.

All applicants will be required to indicate the Confirmed Funding Amount.

You must upload any required supporting evidence at the end of this section:

  • For each source of funding that has been secured, provide a written declaration in the form of a general letter, a letter of intent, or a service level agreement from the funding source detailing the extent of support that will be provided, regardless of whether that source is dedicating a specific amount of monetary support or an in-kind contribution (with an estimated monetary value of the in-kind contribution).

1.2. Contact Details for Source of Funding

Provide the contact information for the entity providing the funding in the space provided.

2. Documents

Appendix 12 – Third-Party Funding Document(s): Appendix 12 documents must use the following naming convention: Appendix 12 – Document number – Third-Party Funding Document.

C. Confidentiality and Declarations

The applicant must complete the confidentiality and declarations sections below.

1.1 Confidentiality

For the reasons set out in Telecom Regulatory Policy 2018-377 (paragraphs 405 to 408), the CRTC determined that applicants will be permitted to file their applications confidentially. The CRTC may, at its discretion, disclose certain application information in its funding decisions and in public reports, as necessary, to identify and describe the approved project and the broad reasons for its selection, including the name of the funding recipient, the number of households served, the amount of funds awarded, the geographic area(s) of the project, the technology implemented, and assessment criteria and selection considerations that supported the selection of the project. Consistent with previous funding decisions, the CRTC does not expect to disclose specific information concerning applications that are not selected.

The CRTC will not disclose, and will retain in confidence, financial, commercial, or technical information included in the application that is consistently treated by the applicant as confidential. This includes information such as (i) the applicant’s financial statements; (ii) projected revenues and expenses for the proposed project; (iii) detailed costing of the project; (iv) detailed network information; (v) detailed technical descriptions of the service and network design, including logical network diagrams, logical paths, supporting assumptions, and technical dependencies; (vi) equipment and facilities lists; and (vii) details of provisioning assumptions as filed in the application.

If the applicant objects to the disclosure of other information that would not be captured within the above list, the Online Application Form will enable the applicant to request confidentiality in respect of any such information, even if its project is selected for funding. Therefore, you must select one of the following options:

  • The Applicant requests that their application be treated as confidential to the extent provided for in the Application Guide.
  • The Applicant requests that their application be treated as confidential to the extent provided for in the Application Guide, subject to the following. The Applicant understands that the information outlined above will not be disclosed as part of a positive funding decision or in public reports but objects to disclosure of other information that would not be captured within information provided above.
    • If the applicant objects, list the specific information that it considers confidential (which is not already identified by the Commission above) and provide reasons, as well as any supporting documents, why the disclosure of such information in a funding decision or in public would not be in the public interest, including why the specific direct harm that would be likely to result from such disclosure would outweigh the public interest.

1.2 Declarations

The applicant must confirm all of the declarations on this page.

1.3 Declaration of the Applicant or its Designated Representative

The applicant must complete all declarations on this page.

Appendix 1: Checklist of Attachments

A. Applicant Details

Appendix 1(a) – Legal Status and Carrier Status

  • Evidence of the legal status of the applicant in a format acceptable to the CRTC (see the guidance for section A.3).

Appendix 1(b) – Member’s Roles and Responsibilities

  • A description of the roles and responsibilities of the applicant and each member of the joint venture, partnership, or consortium, including ownership of assets, network builder, service provider, and dispute resolution mechanisms.

Appendix 2 – Financial Solvency

  • A copy of independently prepared (including audited, review engagement, or notice to reader) financial statements (balance sheet, income statement, and cash flow statement, including financial statement notes and, if audited, the auditor’s report and opinions of the financial statements) for the last three calendar years.

Appendix 3 – Contractual Arrangement

Contract or other evidence that the contractor with experience deploying and operating broadband infrastructure in Canada for a minimum of three years has agreed to the project.

B. Project Details

Appendix 4 – Application Workbook

  • The Application Workbook is supplied by the CRTC and must be used to provide the details of the project according to the instructions provided in the Workbook.

Appendix 5(a) – List of Affected Communities

  • Using the provided template, provide a list that identifies each community affected by the proposed project; the location of affected communities; whether affected communities are Indigenous communities or OLMCs; and a brief description of consultation efforts.

Appendix 5(b) – Consultation documents

  • Evidence of community consultation in an acceptable format to the CRTC (see the guidance for section B.4).
  • Evidence of support by anchor institutions intended to be served, for example, in the form of letters, contracts, or emails.

Appendix 6(a) – Business Marketing Plan

  • High level business marketing plan including a business overview outlining the demographic, economic and social factors of the area, a brief market analysis listing the size of the target market and existing competitors, and a brief sales and marketing plan outlining the plan to increase customers in the project’s geographic area. Include all supporting evidence and assumptions. Note that the financial statement tab in the Application Workbook provides the financial forecast for the project, therefore you do not need to include this in your business plan. For instructions on how to create elements of a business marketing plan, visit the BDC website.

Appendix 6(b) – Risk Assessment and Mitigation Plan

  • Risk Assessment and Mitigation Plan for the identified risks of the project, including the (i) risk of the applicant not completing the construction, (ii) environmental risk in the build (e.g. trench digging), (iii) pricing risks in the supply of services and wholesale transport expenses, and (iv) if the applicant submits multiple applications for funding, an indication of whether the applicant can successfully implement all, or only a subset of, submitted applications within proposed timelines if more than one application is selected for funding.

Appendix 6(c) – Other Investment documents

  • All other investment documents (e.g. Financing Document).
  • If you are relying on credit to provide your investment in the project, provide a letter from your Chief Financial Officer/Chief Administrative Officer/Treasurer, a letter from a financial institution, or a Council Resolution of budget allocations to support your commitment of the investment amount you are proposing.

Appendix 7 – Logical Network Diagram(s)

  • LND must be clearly labeled and correspond appropriately to the information in the Online Application Form and the Application Workbook.

Appendix 8 – Satellite Capacity Agreements

  • A copy of the satellite transport capacity contract or memorandum of understanding with the satellite transport provider.

Appendix 9 – Mapping Data

  • At the end of this section you must upload the mapping data for your project. Indicate the file format of your data and provide a list of the layers included in your map data.

Appendix 10 – Comparator Services

  • Comparator Service plans and prices for satellite-dependent communities offered by a facilities-based service provider in Iqaluit, Nunavut.

Appendix 11 – Other Documents

C. Third-Party Funding

Appendix 12 – Third-Party Funding documents

  • For each source of funding that has been secured, a written declaration detailing the extent of support that will be provided.
Date modified:
Top