SF50_Amendment_No_009.pdf

1. CONTRACT ID CODE PAGE OF PAGES

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1 23

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

009 03/24/2016

6. ISSUED BY CODE 00004 7. ADMINISTERED BY (If other than Item 6)

CODE

Department of the Interior, Interior Business Center Acquisition Services Directorate, 381 Elden Street, Herndon, Virginia 20170

Same as block 6 Attn: Terrie L. Callahan, terrie_callahan@ibc.doi.gov 703-964-3596

8. NAME AND ADDRESS OF CONTRACTOR (No. Street, county, State and ZIP: Code) (✔) 9A. AMENDMENT OF SOLICITATION NO.

D15PS00295

To all prospective offerors x 9B. DATED (SEE ITEM 11)

01/13/2016

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning one (1) copy of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATA SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and data specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(✔) A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET

FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER Specify type of modification and authority)

E. IMPORTANT: Contractor is not, X is required to sign this document and return __1__ copies to the issuing office with proposal submission .

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

This amendment provides a second set of responses (26P through 35P and reissues response 22P and 206) to additional clarification questions received as a result of the Pre-Proposal Conference held on March 10, 2016, and hereby makes changes to the RFP. Some of those changes are as a result of the clarification questions and are as indicated in the attached Questions and Answers. The shade method has been used to identify the lines of text/data that has changed. Some pages are being replaced due to a shift in text only and may not reflect shading on those pages which do not have changes.

Except at provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print) 16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

Terrie L. Callahan

15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED

(Signature of person authorized to sign)

BY _____________________________________________

(Signature of Contracting Officer)

03/24/2016

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV. 10-83)

PREVIOUS EDITION UNUSABLE Computer Generated Prescribed by GSA

FAR (48 CFR) 53.243

Solicitation No. D15PS00295 – FirstNet Nationwide Public Safety Broadband Network

(NPSBN)

Second Set of Pre-Proposal Conference Questions and Answers (26P through 35P) attached, page 1 through 10

Remove and replace the following RFP pages:

Section Remove Pages Insert Pages Section F i, F-3, F-4 i, F-3, F-4 Section J, Attachment J-19 i, J-19 – 3 i, J-19 – 3

Section L L-9, L-10, L-19, L-23 L-9, L-10, L-19, L-23, L-23.1 Section M M-8 M-8

All other terms and conditions remain unchanged.

Solicitation No. D15PS00295 – Section F Deliverables and Performance

Page i Amendment 009

Table of Contents F Deliverables and Performance ............................................................................................................... F-1

F.1 FAR 52.252-2 Clauses Incorporated by Reference (FEB 1988) ..................................................... F-1

F.2 Term of the Contract and Task Orders ......................................................................................... F-1

F.2.1 Day 1 Task Order Period of Performance ........................................................................ F-1

F.3 Place of Performance .................................................................................................................... F-2

F.4 Meetings, Reports, and Other Deliverables .................................................................................. F-2

F.4.1 Proposed Deliverables ..................................................................................................... F-2 F.4.2 FirstNet-Required Deliverables ........................................................................................ F-2 F.4.3 Orientation Briefing ....................................................................................................... F-12

F.5 Other Performance Requirements ............................................................................................. F-12

F.5.1 Productive Direct Labor Hours ....................................................................................... F-12 F.5.2 Legal Holidays ................................................................................................................ F-12

F.6 Notice to the Government of Delays .......................................................................................... F-13

F.7 Subcontracting Plan Reports....................................................................................................... F-13

List of Tables Table 1 Federal Acquisition Regulation Clauses Incorporated by Reference ............................................ F-1 Table 2 Coverage Maps .............................................................................................................................. F-3 Table 3 Network Statistics ......................................................................................................................... F-4

Page F-3 Amendment 009

Broadband Network (NPSBN) in such state or territory. The plan must include elements that are required of FirstNet by the Act, elements states and territories will need for the governor’s decision, and elements that the Federal Communications Commission will require to assess state-deployed Radio Access Networks (RANs).

The plan for each state and territory shall be delivered using the Web-based delivery tool outlined in Section J, Attachment J-18, Delivery Mechanism Objectives for State Plans, according to the proposed Initial Operational Capability (IOC)/Final Operational Capability (FOC) milestones established in Section J, Attachment J-8, IOC/FOC Target Timeline.

Delivery date for these deliverables is to be proposed by the Offeror.

F.4.2.2 Coverage and Capacity

The Contractor shall provide the following coverage and capacity deliverables post contract award. If the Offeror’s solution includes non-Band 14 RAN, include the non-Band 14 coverage maps and associated network statistics, as noted below.

F.4.2.2.1 Coverage, Population, and Capacity Maps

Within 30 days of contract award, the Contractor shall submit an updated package of coverage, population, and capacity maps and network statistics—as defined in Table 2 Coverage Maps and Table 3 Network Statistics for each of the 56 states and territories. The Contractor shall also update the proposed Coverage and Capacity Template provided in Section J, Attachment J-17, including completion of the “Site Summary Tab,” noting site locations nationwide. The Contractor shall note changes that have occurred subsequent to the proposal submission in the updated package and Coverage and Capacity Template.

Table 2 Coverage Maps

Level Band Phase Number of Maps Required

Format Submittal Method

Nationwide Non-Band

IOC-1, IOC-2,

IOC-3, IOC-4,

IOC-5, and FOC

Six (6) maps of each file type, depicting coverage by technology: Long Term Evolution

(LTE), 3G, 2G,

and roaming.

Esri shapefiles (.shp) and MapInfo (.grd/.tab) files

Files should be provided via Secure File Transfer (SFT) with Offeror-provided credentials or Offeror-provided portable drive

Nationwide Band 14 IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Six (6) maps of each file type with the LTE analysis layers specified above

Esri shapefiles (.shp) and MapInfo (.grd/.tab) files

Files should be provided via SFT with Offeror-provided credentials or Offeror-provided portable drive

Page F-4 Amendment 009

Table 3 Network Statistics

Coverage Type Level Phase

Non-Band 14 Area Covered ** State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Non-Band 14 Population Covered ** State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Band 14 Area Covered State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Band 14 Population Covered State/Territory IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

Band 14 Network Capacity County IOC-1, IOC-2, IOC-3, IOC-4, IOC-5, and FOC

** Note: Non-Band 14 coverage statistics should be broken down by technology: LTE, 3G, 2G, and roaming.

F.4.2.2.2 Deployment Schedule and Status

The Contractor shall provide maps noting the coverage and capacity in rural and non-rural areas and active and planned roaming agreements. The maps shall indicate the then-current coverage (with each monthly submittal) as well as the planned coverage targets for future Initial Operational Capability (IOC)/Final Operational Capability (FOC) milestones. The maps shall be provided on a monthly basis for each of the 56 states and territories as well as for the nation as a whole. The Contractor shall also provide a planned deployment schedule and note any changes to the schedule or changes in coverage expectations.

F.4.2.3 Network Technology Roadmap

The Contractor shall provide a network technology roadmap that details vendor equipment capabilities, features, and services identified for inclusion in the NPSBN. For each planned release, the Contractor shall note the targeted availability date and describe the capability, feature, or service, as well as the specific 3GPP release supported. The roadmap shall also note changes in hardware, software, and other network elements impacted by planned releases.

The roadmap shall be provided beginning six (6) months after contract award and subsequent updates shall occur every six (6) months thereafter, unless additional updates are needed and/or mutually agreed upon.

F.4.2.4 Network Operations

The Contractor shall provide the following network operations deliverables post contract award.

F.4.2.4.1 Integration of State-Deployed RANs

The Contractor shall describe the status of efforts to integrate state-deployed RANs. This report shall be provided quarterly beginning three (3) months after award.

F.4.2.4.2 NPSBN Key Performance Indicators

As noted in Section F.4.1, Proposed Deliverables, and Section L, Instructions, Conditions, and Notices to Offerors or Respondents, Section L.3.1.8, Section Eight – Deliverables Table, the Offeror shall propose deliverables that provide a formal means of communicating the metrics noted in the Quality Assurance Surveillance Plan (QASP). At a minimum, the Contractor shall provide end-to-end performance data of the NPSBN including both Band 14 and non-Band 14 operations (if applicable). The report shall include key performance indicators (KPIs) and trends for the network performance, User Equipment, and services.

This report shall be provided quarterly beginning three (3) months after award.

Solicitation No. D15PS00295 – Section J, Attachment J-19 State Plan Template

Page J-19 – i Amendment 009

Table of Contents

1 Purpose

2 FirstNet Overview and Mission

3 State Consultation

3.1 State Governing Body

3.2 [State Name] Consultation Process

3.3 Outreach and Education Support

3.4 State Plan Inputs and Outcomes

3.4.1 Minimum Criteria for a State Plan

3.4.2 Coverage Objectives

3.4.3 User Profiles/Statistics

3.4.4 Capacity Planning

3.4.5 Current Mobile Data Usage

3.5 State Decision Process

3.5.1 Summary/Timeline of Actions Required by the State

3.5.2 Changes to State Plan Following Decision to Proceed with FirstNet-Deployed

Radio Access Network

4 State Radio Access Network Plan

4.1 Radio Access Network Partner

4.2 Network Design and Key Assumptions

4.2.1 Coverage Objectives and Requirements

4.2.2 RESERVED

4.2.3 Link Budget Specifications

4.2.4 Equipment Performance Specifications

4.2.5 Early Builder Integration

4.2.6 Temporary Coverage Related to Incidents and Planned Events

4.3 State Coverage Summary

4.3.1 Persistent Coverage

4.3.2 Coverage Extension Assets for Purchase by Public Safety Entities

4.3.3 Non-Persistent Cellular Service and Devices

4.4 Deployment Phases and Timelines

4.5 Rural Milestones

4.6 Network Upgrade and Expansion

4.7 State Assets

4.7.1 Memorandum of Understanding/ Memorandum of Agreement Requirements .. 6

4.7.2 Tower Sites

4.7.3 Backhaul

4.7.4 Other State Assets

4.8 Spectrum Clearing

5 Public Safety Grade

5.1 Coverage and Hardening

5.2 Installation

Solicitation No. D15PS00295 – Section J, Attachment J-19 State Plan Template

Page J-19 – 3 Amendment 009 the techniques that will be used to enhance in-building coverage. Identify which in-building solutions will be served with or without Band 14 and include a list of locations for each in-building solution. Take into consideration the size of the in-building location to be covered, expected traffic, and types of services to be supported in the area of interest when selecting the type of in-building systems to be used.

Transportation Infrastructure – Describe the deployment strategy to serve different modes of transportation (e.g., tunnels, railways, ports and waterways, airports, roads). Provide the design, methodologies, sources, and methods used to identify transportation infrastructure coverage requirements and the methodology to determine the appropriate level of indoor, outdoor, and underground service. Provide details on the approach to integration of in-building solutions with the NPSBN.

4.2.1 Coverage Objectives and Requirements

Text for this section will be provided by FirstNet.

4.2.2 RESERVED

[This section was removed in its entirety.]

4.2.3 Link Budget Specifications

Provide the detailed link budget information utilized in the development of the provided coverage maps.

The link budget should be provided for all morphologies (dense urban, urban, suburban, and rural) and for each of the 56 states and territories. Within the link budget, include the following information:

• Assumptions, margins, and gains accounted for in downlink and uplink

• Impacts due to various device types

• Maximum allowable path loss, design thresholds, and cell radius

4.2.4 Equipment Performance Specifications

Describe the proposed Radio Access Network (RAN) vendor portfolio, scope of equipment, and feature interoperability to be included with the NPSBN. Provide specifications where applicable and, at a minimum, include the following information:

• A diagram and description of the Long Term Evolution (LTE) base station and sectors, including the antenna system and backhaul components. Identify areas of resource aggregation or redundancy. Describe redundancy mechanisms available in the event a radio fails

• A description of variants of Enhanced Node Base station (eNodeB) platforms available in the current architecture, including specifications for each platform

• Hardware or software techniques utilized to maximize coverage and capacity (e.g., MIMO, carrier aggregation)

• A dimensioning guide for all capacity-dependent hardware and software in the eNodeB. Within the guide, describe the traffic load used in the dimensioning calculation as well as any assumptions made for redundancy

• Solution details if antennae are shared with another frequency band

• The maximum number of radio bearers supported by each variant eNodeB platform

Solicitation No. D15PS00295 – Section L Instructions, Conditions, and Notices to Offerors or Respondents

Page L-9 Amendment 009

Name of the DOI/Interior Business Center (IBC) point of contact (Ms. Terrie L. Callahan in Herndon, VA) or the FirstNet points of contact (Ms. Peggy O’Connor and Mr. Mouncef Belcaid in Boulder, CO)

When submissions are hand carried or delivered by courier service or express delivery service (e.g., Federal Express, DHL), the Offeror assumes full responsibility for ensuring allocation of enough time to gain access to the IBC, Acquisition Services Directorate (AQD) staff in accordance with these instructions and to submit its capability statement by the time and date specified herein.

As stated above, please be advised that it is the Offeror’s responsibility to ensure the Government receives its submission on or before the specified due date and time.

L.2.5 Submission of Proposals

Proposals shall be received on or before 2:00 p.m. Eastern Time on Friday, May 13, 2016. Proposals shall be submitted in hard copy (one original and eighteen hard copies) and on two flash drives in Adobe PDF or Microsoft Word soft copy file format, with the exception of any Excel, map, and shape files, to be submitted with the hard copies. In the event the hard copy and soft copy content conflict, the hard copy version will take precedence over the soft copy version.

Please note it is the Offeror’s responsibility to ensure/verify that the Government receives its submission on or before the date and time specified. If the proposal is not received by the Government on or before the date and time specified, the Offeror’s submission may be considered late.

The addresses designated for receipt of proposals is:

ORIGINAL AND THIRTEEN (13) HARD COPIES AND ONE FLASH DRIVE TO:

Ms. Terrie L. Callahan U.S. Department of the Interior Office of the Secretary, Interior Business Center Acquisition Services Directorate 381 Elden Street, 4th Floor Herndon, VA 20170

Phone: 703-964-3596

FIVE (5) HARD COPIES AND ONE FLASH DRIVE TO:

Primary Points of Contact: Ms. Peggy O’Connor and Mr. Mouncef Belcaid Alternate Points of Contact: Mr. Jordan Andrews and Mr. Michael Carroll First Responder Network Authority 3122 Sterling Cir, Suite 100 Boulder, CO 80301

Phone: (303) 334-9660 Alternate Phone: (303) 334-9661

Page L-10 Amendment 009

Please note that DOI locations are secured buildings. If offers are hand delivered, instruct the courier to check in at the guard desk and ask to call the point of contact identified above. A staff member will meet the courier to receive the submittal. All packages containing proposal submissions shall be labeled and sealed as if for mailing, and the following information shall be marked on the outside:

RFP number

Date and time specified for receipt

Name and address of the Offeror

Name of the DOI/IBC point of contact (Ms. Terrie L. Callahan in Herndon, VA) or the FirstNet points of contact (Primary: Ms. Peggy O’Connor and Mr. Mouncef Belcaid or Alternate: Mr.

Jordan Andrews and Mr. Michael Carroll in Boulder, CO)

When submissions are hand carried or delivered by courier service or express delivery service (e.g., Federal Express, DHL), the Offeror assumes full responsibility for ensuring allocation of enough time to gain access to the IBC, AQD staff in accordance with these instructions and to submit its proposal by the time and date specified herein.

As stated above, please be advised that it is the Offeror’s responsibility to ensure the Government receives its submission on or before the specified due date and time.

L.2.6 Assumptions, Conditions, and/or Exceptions

The Offerors shall submit, under a separate tab, in each volume identified herein, all (if any) assumptions, conditions, or exceptions with any of the terms and conditions of this RFP. If not noted in its proposal, it will be assumed that the Offeror proposes no assumptions, conditions, or exceptions for award and agrees to comply with all of the terms and conditions as set forth herein. It is not the responsibility of the Government to seek out and identify assumptions, conditions, or exceptions buried within the Offeror’s proposal.

For proposal preparation purposes, if there are any assumptions, conditions, or exceptions made pertaining to demarcation between the Government’s responsibility and/or the Contractor, the Offeror shall describe the specific demarcation points and/or assumptions, conditions, or exceptions within the proposal submission.

L.3 Proposal Format and Submission Instructions

Proposals, signed by an official authorized to bind the Offeror, shall set forth full, accurate, and complete information as required by this RFP. The penalty for making false statements is prescribed in 18 U.S.C. § 1001. Failure to furnish full and complete information requested may cause an offer to be determined unacceptable, and it may be removed from consideration for award.

In responding to this RFP, the Offerors shall prepare and submit the indicated numbers of copies (see Section L.2.5, Submission of Proposals) and required information that constitutes the Offeror’s complete proposal submission. Additionally, the Offeror’s information and submission shall be organized by volume as indicated below. Each volume may include an Executive Summary that shall not exceed 4 pages in length (2 sheets of paper, double-sided print). Specifically, the business management volume shall be separate from the technical and pricing volumes.

Any page limitation for each proposal volume is identified within that section. However, the following information applies to each volume. The volumes shall be provided in Adobe PDF or Microsoft Word

Page L-19 Amendment 009

The technical proposal shall not exceed 300 pages in length (150 sheets of paper, double-sided print);

this excludes coverage maps and the following Section J attachments from the page limitation: Section J, Attachment J-11, Device Specifications Template; Section J, Attachment J-12, Test Strategy Template;

and Section J, Attachment J-17, Coverage and Capacity Template. The technical proposal shall contain the following information and be broken down by the following sections.

L.3.2.1 Coverage and Capacity

The Offeror shall provide a clear, concise description regarding its proposed approach in deploying a network to implement coverage and capacity. This shall include:

Coverage and Capacity Maps and Statistics

Radio Access Network (RAN) Solutions and Strategy

IOC/FOC Milestones for Coverage and Capacity

The proposed solution for coverage and capacity shall address the elements described below according to the IOC/FOC target timeline detailed in Section J, Attachment J-8. Maps submitted by the Offeror shall be based on a bin size no greater than 30 x 30 meters, include Esri shapefiles and MapInfo files (in electronic format), and reference the information contained in Section J, Attachment J-1, Coverage and Capacity Definitions. The statistics shall utilize Section J, Attachment J-17, Coverage and Capacity Template.

The Offeror must complete Section J, Attachment J-2, Nationwide and Rural Coverage Compliance Checklist, to demonstrate its ability to meet the objective to provide coverage in all states and territories and to ensure that rural coverage includes partnerships with rural telecommunications providers. The Offeror shall note whether both Band 14 and non-Band 14 coverage are included in each of the 56 states and territories (yes/no), as well as list current and planned partnerships with rural telecommunications providers by state/territory. Lastly, Section J, Attachment J-2, Nationwide and Rural Coverage Compliance Checklist, requests tabulation, by state, of the percentage of rural coverage achieved via partnerships with rural telecommunications providers. The Offeror’s solution must demonstrate intent to exercise rural telecommunications provider partnerships for at least 15 percent of the total persistent rural coverage nationwide. While Section J, Attachment J-2, Nationwide and Rural Coverage Compliance Checklist, requests these data by states, the 15 percent coverage factor will be evaluated on a nationwide basis only as stated in Section M, Evaluation Factors for Award.

L.3.2.1.1 Coverage and Capacity Maps and Statistics

The Offeror shall submit all applicable information as defined in Table 2 Coverage Maps Required for Coverage and Capacity. The Offeror shall submit all network statistics, as defined in Table 3 Network Statistics Required for Coverage and Capacity, for each of the 56 states and territories in the Coverage and Capacity Template (Section J, Attachment J-17). The Offeror shall refer to the guidelines provided in Section J, Attachment J-1, Coverage and Capacity Definitions. The Offeror shall describe the details for the network planning design as stated in Section L.3.2.1.2.2, Network Planning and Design, below and the methodologies used to create coverage maps and associated capacity information.

Page L-23 Amendment 009

Planning Tool Settings – Document settings used in the planning tool, including but not limited to Multiple Input, Multiple Output (MIMO) gains; clutter weights/losses; and environment configurations.

Geo-data description – Detailed description of the geo-data used (e.g., clutter, terrain, clutter height, buildings), including but not limited to vintage, source, and resolution.

Propagation Models Description – Detailed description of how the propagation models for planning were generated and if they are calibrated or un-calibrated. If calibrated models are utilized, describe how the models were calibrated.

Planning Project and All Supporting Folders – Copy of the project file used in the Offeror’s planning tool. All supporting files and folders needed to build a project shall be provided with the exception of the site summary data noted below. The project file shall include the analysis generated as well as traffic maps.

Site Summary – Site summary that aligns with the Section J, Attachment J-17, Coverage and Capacity Template, Site Summary tab. A site table shall be provided for the FOC, including a field to identify the site information for each IOC. Site summary data is not required as part of the proposal submittal, but will be required 30 days after award as noted in Section F, Deliverables and Performance.

As part of the evaluation process, the Government reserves the right to request detailed site information (to include all site data for up to two counties per state or territory). If requested, these data are to be supplied using the “Site Summary” tab in Section J, Attachment J-17, Coverage and Capacity Template.

Network Design Statistics L.3.2.1.2.2.1

The Offeror shall provide its proposed RAN solution for each of the 56 states and territories for each IOC and FOC milestone. The Offeror shall provide the following information in accordance with statistics required in the Coverage and Capacity Template (Section J, Attachment J-17).

Downlink SINR Distribution – Average downlink SINR and distribution by proposed coverage area and population

Uplink SINR Distribution – Average uplink SINR and distribution by proposed coverage area and population

MCS Distribution – Downlink and uplink MCS distribution by proposed coverage area and population

Average Downlink Sector Throughput – Average downlink sector throughput and throughput distribution by proposed coverage area and population

Average Uplink Sector Throughput – Average uplink sector throughput and throughput distribution by proposed coverage area and population

RAN Technology Roadmap L.3.2.1.2.2.2

The Offeror shall provide IOC/FOC milestone details of its proposed approach for the RAN technology roadmap that includes the applicable technology standards and releases, vendor equipment capabilities, features and services identified for inclusion into the NPSBN, and ways it specifically addresses the RAN public safety needs. The roadmap shall include the target availability date for the items described and shall identify the latest 3GPP release supported. The Offeror shall also provide the proposed RAN hardware, software/feature evolution roadmap, and insight into impacts to RAN nodes, antenna systems and interfaces.

Page L-23.1 Amendment 009

NPSBN Vendor Infrastructure Equipment L.3.2.1.2.2.3

The Offeror shall describe the proposed RAN vendor portfolio (outlining its proposed equipment suppliers and manufacturers), scope of equipment, and feature interoperability to be included with the NPSBN. Specifications are to be provided where applicable and shall include:

[THE REMAINDER OF THIS PAGE IS INTENTIONALLY LEFT BLANK]

Solicitation No. D15PS00295 – Section M Evaluation Factors for Award

Page M-8 Amendment 009

Coverage and Capacity Template. The Government will evaluate the maps and statistics against the coverage objectives specified in Section J, Attachment J-1, Coverage and Capacity Definitions. For the coverage maps, each individual grid block will be assessed for meeting the definition of coverage (see Section J, Attachment J-1, Coverage and Capacity Definitions). Only those grid blocks that have a reasonable amount of coverage will be considered acceptable. As noted in Section L, Instructions, Conditions, and Notices to Offerors or Respondents, Section L.3.2.1.2.2, Network Planning and Design, detailed site locations are not required; however, for evaluation purposes, the Government reserves the right to request detailed site information (to include all site data for up to two counties per state or territory.) If requested, these data are to be supplied using the “Site Summary” tab in Section J, Attachment J-17, Coverage and Capacity Template.

The Government will evaluate the Offeror’s proposed solution using a quantitative approach for each of the following coverage and capacity elements, which are of equal importance:

Non-Band 14 Area Coverage – The amount of land mass that is covered with non-Band 14 coverage solutions

Non-Band 14 Population Coverage – The amount of population that is covered with non-Band 14 coverage solutions

Band 14 Area Coverage – The amount of land mass that is covered with Band 14 coverage solutions

Band 14 Population Coverage – The amount of population that is covered with Band 14 coverage solutions

Band 14 Network Capacity – The amount of designed network capacity for first responders and secondary users

M.4.2.2 RAN Strategy and Solutions

The Offeror’s proposed solution will be evaluated qualitatively based on the proposed RAN design solution, which must include architecture, functionality, design, implementation, roadmap, and operational strategies that effectively use resources, skillsets, an organizational structure, and tools.

M.4.2.3 IOC Milestones for Coverage and Capacity

The Offeror’s proposed solution will be evaluated qualitatively based on the proposed approach to meeting and/or exceeding the deployment schedule in accordance with the coverage and capacity milestones as provided in Section J, Attachment J-8, IOC/FOC Target Timeline.

M.4.3 Volume II – Products and Architecture Factor

The Offeror’s solution will be evaluated based on its proposed approach, including innovation, creativity, and thoroughness, shown in planned execution of the overall objectives as stated in Section C, SOO, and associated Section J attachments as applicable. The products and architecture factor includes evaluation of the Offeror’s proposed solution in the following sub-factors:

Services

Applications

Device Ecosystem

Architecture and Infrastructure

Operations

Security

Test Strategy

Solicitation No. D15PS00295 – Amendment 009 Questions and Answers

Question #: 206 – Please note, the answer to this question hereby supersedes the one issued in

Amendments 004 and 008

RFP Section Reference:

Section L.3.2.3, Test Strategy

Section J, Attachment J-12, Test Strategy Template

Question:

Can the Government please confirm that proposal data provided in the Attachment J-12 format to meet the L.3.2.3 requirement is exempt from the Volume II page limitation?

Answer:

Section J, Attachment J-12, Test Strategy Template, is exempt from the Technical Volume II page limitation.

RFP Change (Yes/No):

Yes

RFP Change Description:

Section L.3.2, Volume II – Technical, is being revised in this Amendment 009 to read, “… The technical proposal shall not exceed 300 pages in length (150 sheets of paper, double-sided print); this excludes coverage maps and the following Section J attachments from the page limitation: Section J, Attachment J-

11, Device Specifications Template; Section J, Attachment J-12, Test Strategy Template; and Section J, Attachment J-17, Coverage and Capacity Template.”

Question #: 22P – Please note, the answer to this question hereby supersedes the one issued in

Amendments 007 and 008

Question:

Given the nationwide span of our wireless network, the response to Site Summary tab in Attachment J-17 will include approximately 5.7 million data points. That data, when compiled in one file, will constitute a complete and detailed report of our entire network. Carriers don’t disclose their network architecture for national security reasons. It is unadvisable for FirstNet to have your secure government network architecture in the public sphere. Given the sensitivity of this information, we respectfully request that

Offerors be permitted to provide this information in a “clean room” where Government evaluators can review the materials while not requiring the Offeror to include or distribute copies of the materials as part of their proposal submissions.

Answer:

The RFP is amended to remove the requirement to submit detailed site location data as part of the proposal. Therefore, establishment of a “clean room” is not necessary.

Section L.3.2.1.2.2, Network Planning and Design, 6th bullet, Planning Project and All Supporting

Folders, is being revised in this Amendment 009 to read, “… All supporting files and folders needed to build a project shall be provided with the exception of the site summary data noted below.” Within the same section, the 7th bullet, Site Summary, is being revised in this Amendment 009 to read, “… Site summary data is not required as part of the proposal submittal, but will be required 30 days after award as noted in Section F, Deliverables and Performance.” Additionally, the last paragraph in the section is being revised in this Amendment 009 to read, “As part of the evaluation process, the Government reserves the right to request detailed site information (to include all site data for up to two counties per state or territory). If requested, these data are to be supplied using the “Site Summary” tab in Section J, Section F.4.2.2.1, Coverage, Population, and Capacity Maps, 1st paragraph, is being revised in this

Amendment 009 to read, “… The Contractor shall also update the proposed Coverage and Capacity

Template provided in Section J, Attachment J-17, including completion of the “Site Summary Tab,” noting site locations nationwide.”

Section J, Attachment J-19, State Plan Template, Section 4.2.2, Tower Site Locations, is being revised in this Amendment 009 to remove the text entirely and replace the heading title with “RESERVED.”

Section M.4.2.1, Coverage and Capacity Maps and Statistics, 1st paragraph, is being revised in this

Amendment 009 to read, “… As noted in Section L, Instructions, Conditions, and Notices to Offerors or

Respondents, Section L.3.2.1.2.2, Network Planning and Design, detailed site locations are not required;

however, for evaluation purposes, the Government reserves the right to request detailed site information

(to include all site data for up to two counties per state or territory.) If requested, these data are to be supplied using the “Site Summary” tab in Section J, Attachment J-17, Coverage and Capacity Template.”

Question #: 26P

RFP Section Reference:

Section L.3.2.1, Coverage and Capacity, 2nd Paragraph

Section J, Attachment J-1, Coverage and Capacity Definitions

Section J, Attachment J-8, IOC/FOC Target Timeline

Section J, Attachment J-17, Coverage and Capacity Template

Section M.4.2.1, Coverage and Capacity Maps and Statistics

Section C, Statement of Objectives

Section L.3.2.1 and Section J Attachments J-1, J-8, J-17 require detailed, highly sensitive information for each site including coverage. Given the highly competitive and sensitive nature of this data, carriers are very reluctant to provide this data to anyone, including the Government and prime contractors.

This was highlighted at Industry Day on March 10th, when a Tier 1 Carrier requested special handling of their tower and coverage data including establishing a clean room environment controlled by the

Government.

Section C of the RFP emphasizes an objective based approach, valuing innovation to achieve the 16

FirstNet objectives. However, J-17 requires offerors to specify, at time of proposal submission, tower site specifics and a complete RF design for the 56 states and territories. Largely the same detailed solution coverage must be prepared, analyzed and delivered as an element of the design effort included in the Day

1 Task Order, after the contract has been awarded, so the RF design will be redone as part of the state planning process.

Will the Government consider modifying the requirements of L.3.2.1 and give bidders more latitude in demonstrating coverage, capacity, and tower information? This could include identifying more general site information that includes the number and type of sites for each State and Territory, meeting the intent of J-17. The Government could identify a specific State with a representative morphology (dense urban, urban, suburban, and rural) to enable comparative analysis of submitted bids. Such an approach would provide non-Tier 1 carriers the opportunity to submit compliant, innovative bids to meet FirstNet’s mission needs.

The RFP is amended to remove the requirement to submit detailed site location data as part of the proposal.

Section L.3.2.1.2.2, Network Planning and Design, 6th bullet, Planning Project and All Supporting

Folders, is being revised in this Amendment 009 to read, “… All supporting files and folders needed to build a project shall be provided with the exception of the site summary data noted below.” Within the same section, the 7th bullet, Site Summary, is being revised in this Amendment 009 to read, “… Site summary data is not required as part of the proposal submittal, but will be required 30 days after award as noted in Section F, Deliverables and Performance.” Additionally, the last paragraph in the section is being revised in this Amendment 009 to read, “As part of the evaluation process, the Government reserves the right to request detailed site information (to include all site data for up to two counties per state or territory). If requested, these data are to be supplied using the “Site Summary” tab in Section J, Section F.4.2.2.1, Coverage, Population, and Capacity Maps, 1st paragraph, is being revised in this

Amendment 009 to read, “… The Contractor shall also update the proposed Coverage and Capacity

Template provided in Section J, Attachment J-17, including completion of the “Site Summary Tab,” noting site locations nationwide.”

Section J, Attachment J-19, State Plan Template, Section 4.2.2, Tower Site Locations, is being revised in this Amendment 009 to remove the text entirely and replace the heading title with “RESERVED.”

Section M.4.2.1, Coverage and Capacity Maps and Statistics, 1st paragraph, is being revised in this

Amendment 009 to read, “… As noted in Section L, Instructions, Conditions, and Notices to Offerors or

Respondents, Section L.3.2.1.2.2, Network Planning and Design, detailed site locations are not required;

however, for evaluation purposes, the Government reserves the right to request detailed site information

(to include all site data for up to two counties per state or territory.) If requested, these data are to be supplied using the “Site Summary” tab in Section J, Attachment J-17, Coverage and Capacity Template.”

Question #: 27P

RFP Section Reference:

Section L.3.2.1, Coverage and Capacity

Section J, Attachment J-1, Coverage and Capacity Definitions

Section J, Attachment J-8, IOC/FOC Target Timeline

Section J, Attachment J-17, Coverage and Capacity Template

Section M.4.2.1, Coverage and Capacity Maps and Statistics

Section C, Statement of Objectives

Section L.3.2.1 and Section J Attachments J-1, J-8, J-17 require detailed, highly sensitive information for each site including coverage. Given the highly competitive and sensitive nature of this data, carriers are very reluctant to provide this data to anyone, including the Government and prime contractors.

This was highlighted at Industry Day on March 10th, when a Tier 1 Carrier requested special handling of their tower and coverage data including establishing a clean room environment controlled by the

Government.

The Government requires detailed solution information for the proposal, including proposed nation-wide coverage maps based on a bin size no greater than 30 X 30 meters. Such solution coverage maps favor carriers with an existing nation-wide coverage database at 30 meter resolution. Largely the same detailed solution coverage must be prepared, analyzed and delivered as an element of the design effort included in the Day 1 Task Order, after the contract has been awarded, so the RF design will be redone as part of the state planning process.

Will the Government consider modifying the requirements of L.3.2.1 and give bidders more latitude in demonstrating coverage, but not require detailed 30 x 30 meter final-solution coverage maps for all States and Territories in the proposal? The Government could identify a specific State with a representative morphology (dense urban, urban, suburban, and rural) and perhaps a 1 x 1 mile bin size to enable comparative analysis of submitted bids. Such an approach would provide non-Tier 1 carriers the opportunity to submit compliant, innovative bids to meet FirstNet’s mission needs.

The Government declines to modify the requirements as requested. In accordance with the instructions in

Section L.3.2.1, Coverage and Capacity, maps submitted by the Offeror shall be based on a bin size no greater than 30 x 30 meters, include Esri shapefiles and MapInfo files (in electronic format), and reference the information contained in Section J, Attachment J-1, Coverage and Capacity Definitions.

This level of detail reduces the risk of inaccurately portraying coverage that could occur with the usage of a larger bin size.

No

N/A

Question #: 28P

RFP Section Reference: Section M.4.2.1, Coverage and Capacity Maps and Statistics

Will the Government please clarify how coverage and capacity will be evaluated under this objectives based procurement?

The FirstNet coverage objectives indicate areas where persistent coverage is desired at a minimum. As stated in Section M.4.2.1, Coverage and Capacity Maps and Statistics, “The Offeror’s proposed solution will be evaluated for each of the 56 states and territories using the information provided by the Offeror through coverage maps as well as network statistics included in Section J, Attachment J-17, Coverage and

Capacity Template. The Government will evaluate the maps and statistics against the coverage objectives specified in Section J, Attachment J-1, Coverage and Capacity Definitions … The Government will evaluate the Offeror’s proposed solution using a quantitative approach for each of the following coverage and capacity elements, which are of equal importance:

Non-Band 14 Area Coverage – The amount of land mass that is covered with non-Band 14 coverage solutions

Non-Band 14 Population Coverage – The amount of population that is covered with non-Band

14 coverage solutions

Band 14 Area Coverage – The amount of land mass that is covered with Band 14 coverage solutions

Band 14 Population Coverage – The amount of population that is covered with Band 14 coverage solutions

Band 14 Network Capacity – The amount of designed network capacity for first responders and secondary users”

Question #: 29P

Given the potential diversity of offeror solutions, how will Band 14 and/or non-Band 14 coverage be considered?

Will Band 14 and non-Band 14 coverage be weighted equally or differently by the Government?

As stated in Section M.4.2.1, Coverage and Capacity Maps and Statistics, “… The Government will evaluate the Offeror’s proposed solution using a quantitative approach for each of the following coverage and capacity elements, which are of equal importance: …”

Question #: 30P

RFP Section Reference: Section B.4.4, FirstNet Operational Sustainability, 2nd Paragraph

At Industry Day on Mar 10th, Mr. Poth and others indicated that FirstNet has accurately estimated their

“fixed costs” to cover annual operating expenses over the life of the program. Payments from the prime contractor to FirstNet would cover these known fixed costs, and any funds received in excess of these fixed costs would be used for network enhancements and related task orders through this contract.

Will the Government please share their estimate of fixed costs for the first few years of the program – or the ratio of fixed costs to the minimum threshold payments? This information will be helpful to give bidders a general sense of the portion of the $5.6B that may be used by FirstNet to enhance the network over the life of the program.

The FirstNet minimum payments represent estimated base operating and general administrative costs, including personnel associated with the currently anticipated Operational Architecture as set forth in

Section J, Attachment J-7, and other authorized purposes under the Act and applicable laws. For access to financial reports detailing FirstNet’s annual finances, please visit www.firstnet.gov.

Question #: 31P

RFP Section Reference: Section B.4.4, FirstNet Operational Sustainability, 2nd Paragraph

How does FirstNet envision prioritizing network enhancements and recapitalization efforts annually through the life of the program? Will these projects add capacity, coverage, or other network enhancements in new areas that carriers deem “economically non-viable” but are important to public safety? And will they also include adding coverage, capacity, or other network enhancements in urban areas as well as rural areas?

In accordance with Section C, Statement of Objectives, among other sections of the RFP, Offerors are responsible for the building, deployment, operation, and maintenance of the NPSBN. As stated in Section

C.5, Objectives, Objective #13, Life-Cycle Innovation, one of FirstNet’s objectives is to “… evolve the

NPSBN solution—including products and services—and incorporate 3GPP LTE standards as they evolve and mature throughout the life of the contract, in accordance with the FCC TAB RMTR, the Act, including in particular Section 6206(c)(4), and the attachments in Section J.” Accordingly, the

Government may solicit, and the Contractor may propose, technology refresh and enhancements during the life of the contract (See Section H.11, Technology Refresh/Enhancement Proposals).

If the Contractor’s proposed solution included future expansions to the NPSBN, upon award, the

Contractor would be responsible for costs related to those expansions.

http://www.firstnet.gov/

With regard to Government-defined future expansions of the NPSBN, a subsequent task order would be issued and funded under this contract or through a separate RFP process. In the case of Contractor-offered expansions post-award, the Contractor would be required to follow the process identified in Section H.11, Technology Refresh/Enhancement Proposals.

Question #: 32P

RFP Section Reference: No RFP reference noted in question submitted.

SaaS – Software or mobile device management requirements within the FirstNet RFP.

Can you help to find where these requirements are?

This is an objectives-based acquisition, which affords Offerors the flexibility to propose any unique features and/or functionality within their proposed solutions that meet FirstNet’s objectives. In accordance with Section L.3.2.2.2.1.3, Hosting and Cloud Services, Offerors are to describe how they will provide different cloud services capabilities, including Software as a Service (SaaS).

Question #: 33P

RFP Section Reference: Section L.3.2, Volume II – Technical

Section L.3.2, 2nd paragraph states “The technical proposal shall not exceed 300 pages in length (150 sheets of paper, double-sided print); this excludes coverage maps, requested spreadsheets, or other

Section J attachments from the page limitation.” The Government’s answer to question 206 states that

Section J, Attachment J-12 is not exempt from the Technical Volume II page limitation.

The Section J, Attachment J-12 Test Strategy Template, with no proposal data inserted, is 29 pages. With proposal data inserted, Attachment J-12 is estimated to be 60 pages. 60 pages is 20% of the entire page count for the Technical Volume (300 pages) even though Test Strategy is only 1 of 10 sub-factors in the

Technical Volume. To prevent depleting the amount of detailed information that can be written in the other 9 sub-factors due to limited page count (if Attachment J-12 is required to be included in the page count), request the Government exclude Section J, Attachment J-12 from page count.

Yes, Section J, Attachment J-12 Test Strategy Template is exempt from Technical Volume II page limitation.

Section L.3.2, Volume II – Technical, is being revised in this Amendment 009…