Amendment_009_-_QAs.pdf

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 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, Question #: 34P

We assume that the capacity evaluation criteria in the fifth bullet of section M.4.2.1 is referencing the capacity requirements as specified in section 4.3 of attachment J-1.

If an offeror believes that the demand forecast in J-1 is unrealistic in some areas, may an offeror propose tentative sites that will only be built if the actual traffic trends indicate that the sites are required after the initial coverage sites are built and that the cost of such sites will be offset by the revenue from such traffic?

Section L.3.2.1.1.5, Band 14 Network Capacity, states, “The Offeror shall describe its proposed process used to forecast Band 14 demand at FOC. The Offeror shall detail the available capacity for public safety and secondary users based on the proposed network.” FirstNet will evaluate the proposed coverage based on the coverage maps in Section J, Attachment J-1, Coverage and Capacity Definition.

Question #: 35P

RFP Section Reference: Section J, Attachment J-1 Coverage and Capacity Definition, Tonnage User

Device by County Spreadsheet

What method was used to forecast the traffic in the tonnage workbook?

As noted in Section J, Attachment J-1, Coverage and Capacity Definition, Section 4.3, Demand Map, “FirstNet has aggregated stakeholder data to produce a nationwide view that estimates coverage demand at the county level. The demand maps include the number of devices used by those personnel, an estimate of eligible public safety users, and total monthly tonnage as of 2015.”