Attachment 1_FCC Drive Testing Performance Work Statement (1).pdf

For Official Use Only (FOUO)

Federal Communications Commission Broadband Data Collection

Drive Testing Support Services

Indefinite Delivery / Indefinite Delivery Quantity (IDIQ)

Performance Work Statement

June 2023

Prepared by:

Federal Communications Commission Office of Economics and Analytics 45 L Street NE Washington, DC 20554

Drive Testing Support Services

For Official Use Only (FOUO) 2

CONTENTS

1 BACKGROUND

2 OBJECTIVES

3 SCOPE

4 DETAILED REQUIREMENTS

4.1 Task 1: Program Management

4.1.1 Program / Project Management & Administration

4.2 Task 2: Drive Test Planning

4.2.1 Information Provided By the FCC

4.2.2 Contractor Drive Test Planning Requirements

4.2.3 Drive Test Plan Cost Proposal

4.2.4 Reasonable Notice, Approval and Other Factors

4.3 Task 3: Drive Test Execution and Data Collection

4.3.1 Data Requirements

4.3.2 Data Collection Process

4.3.3 Geographic Scope

4.4 Task 4: Drive Test Outputs and Reporting

4.4.1 Drive Test Outputs

4.4.2 Transfer of Data

4.5 Task 5: Special Projects (Optional Task)

5 DELIVERABLES

6 GOVERNMENT-FURNISHED PROPERTY, EQUIPMENT, OR INFORMATION

7 PLACE OF PERFORMANCE

8 PERIOD OF PERFORMANCE

9 STAFFING PLAN AND PERSONNEL REQUIREMENTS

9.1 Standardized Labor Categories

9.2 Personnel Onboarding

9.3 Staffing Plan

10 SECURITY & PRIVACY

10.1 Personnel Security

10.2 Cybersecurity Training

10.3 Access to FCC Network and Information

10.4 Usage of FCC Information

10.5 Incident Response

10.6 Breach Response

10.7 Processing of FCC Information

10.8 Software Bill of Materials (SBOM)

11 SECTION 508

11.1 Installation, Configuration & Integration Services

11.2 Maintenance Upgrades & Replacements

11.3 Service Personnel

11.4 Hosting Services

11.5 Validation for ICT Items

For Official Use Only (FOUO) 3

11.6 Documentation

12 ORGANIZATIONAL CONFLICTS OF INTEREST (OCI)

13 ADDITIONAL REFERENCES

For Official Use Only (FOUO) 4

Performance Work Statement

1 BACKGROUND

The Federal Communications Commission (FCC) requires an experienced vendor capable of performing field testing and collection of on-the-ground measurements of the coverage and service performance of mobile broadband 3G, 4G LTE, and 5G-NR networks in designated areas to support the requirements of the Broadband Deployment Accuracy and Technological Availability Act (Broadband DATA Act or BDA), Pub. L. No. 116-130, codified at 47 U.S.C. §§ 641-646.

The BDA, enacted in March 2020, requires the FCC to collect more granular and consistent data from broadband internet access service providers on the availability and quality of broadband service. Under new reporting requirements, mobile broadband service providers must submit coverage maps (voice, 3G, 4G LTE, and 5G-NR) based on standardized requirements, as well as supplemental data about how the maps were generated, to support their broadband coverage claims during biannual filing windows. Furthermore, the BDA requires the FCC to “conduct regular audits of information submitted to the Commission by providers . . . to ensure that the providers are complying with [the Act].” Audit tools could include field surveys, investigations, and annual random audits to verify data accuracy. See Broadband Data Collection (BDC) Second Report and Order and Third Further Notice of Proposed Rulemaking, FCC 20-94, 35 FCC Rcd 7460 (2020), for additional information. (https://www.fcc.gov/document/fcc-improves-broadband-data-and-maps-bridge-digital-divide-0).

The FCC’s Broadband Data Task Force (BDTF), together with other FCC Bureaus and Offices, has designed and developed an overarching Broadband Data Collection system (BDC system) to collect, validate, and publish complete, granular, and reliable data on broadband availability. See https://www.fcc.gov/BroadbandData. The key outputs of the BDC system will be public-facing broadband maps with granular information helping to pinpoint where broadband service is available and where it is not available. The FCC, other federal agencies, and other stakeholders will use these broadband maps to make decisions about where service is needed and how to fund the expansion of broadband services.

Challenge Process. The BDA requires the FCC to establish a challenge process to enable consumers, governmental entities, and other third parties to challenge, or formally dispute, the accuracy of the broadband coverage maps or other information submitted by a provider regarding the availability of its broadband internet access service.

For mobile challenges, consumers, governmental entities, and other third-party entities must submit the results of speed tests based on specific parameters and include certain metrics. The FCC will aggregate and evaluate—by the testing environment (i.e., outdoor stationary or in-vehicle mobile) and technology type—valid speed tests submitted by challengers. The FCC will apply the methodology adopted in the Mobile Technical Requirement Order to analyze the speed test data and determine whether the three thresholds for a “cognizable” challenge—geographic, https://www.fcc.gov/BroadbandData

For Official Use Only (FOUO) 5 temporal, and testing—have been met and, if so, the geographic boundary of the area subject to the cognizable challenge.1

Mobile service providers must either respond to a cognizable challenge or concede and have the challenged area identified on the mobile coverage map removed. Providers may rebut a challenge with on-the-ground test data or, in certain circumstances, infrastructure data, so that the FCC may resolve the challenge.

Verification Process. The BDA also requires the FCC to verify the accuracy and reliability of the broadband Internet access service data that service providers submit. For mobile verification inquiries, FCC staff may request and collect verification data from mobile service providers on a case-by-case basis where staff have a credible basis for requiring verification of a provider’s coverage data. Staff will rely upon all available evidence to determine whether there is a credible basis for initiating a verification inquiry.

For further information on the BDC Verification Process, please see the BDC website at https://www.fcc.gov/BroadbandData. Please also see the Mobile Technical Requirements Order, Verification Process sections, and 47 CFR § 1.7006(c).

Audit Process. The BDA requires the FCC to conduct audits of information submitted by providers. FCC staff may randomly conduct audits of a provider’s coverage area to verify coverage and request and collect data in conjunction with such audits. Audit tools will include field surveys, investigations, and annual random audits to verify data accuracy, which also includes drive-tests. In addition, audits may be initiated based on an unusual number of consumer complaints.

Crowdsource Process. The BDA requires the FCC to “develop a process through which entities or individuals . . . may submit specific information about the deployment and availability of broadband internet access service . . . on an ongoing basis . . . to verify and supplement information provided by providers.” Various entities, as well as consumers, may submit crowdsource data to the FCC. For further information on the BDC Mobile Crowdsource Process, please see the BDC website at https://www.fcc.gov/BroadbandData. Please also see the Mobile Technical Requirements Order, Crowdsource sections, and 47 CFR § 1.7006(b).

Propagation Modeling Tool. To augment the analytical capability of the BDC System and effectively evaluate and verify broadband maps, the FCC has licensed Forsk’s propagation modeling tool, Atoll/Naos, an industry-leading software solution/automation platform (hereinafter referred to as the “Propagation Modeling Tool” or “PMT”). In general, the PMT provides capability to conduct propagation modeling for commercial wireless services, including access to various geographic data (GeoData) sources as inputs to the PMT. Data collected by the

1 See Establishing the Digital Opportunity Data Collection, WC Docket No. 19-195, Order, DA 22-241, (WTB/OEA/OET Mar. 9, 2022) at https://www.fcc.gov/document/fcc-releases-bdc-mobile-technical-requirements-order (Mobile Technical Requirement Order). Five valid challenges are needed at a minimum in a hex 8 to create a cognizable challenge with the FCC speed test app (assuming all challenges fail and no other tests are done).

https://www.fcc.gov/BroadbandData https://www.fcc.gov/BroadbandData https://www.fcc.gov/document/fcc-releases-bdc-mobile-technical-requirements-order

For Official Use Only (FOUO) 6 vendor that is awarded this contract (hereinafter “Contractor”) may be used to support propagation modeling and analysis.2

2 OBJECTIVES

The FCC has established a biannual schedule for the collection of information on broadband service availability and quality of service. Mobile wireless providers are required to submit propagation maps reflecting technology-specific user download and upload speeds given prescribed minimum cell edge probabilities, cell loading factors, and modeling resolution. In addition to maps, mobile wireless providers are required to disclose to the FCC details of their propagation models and the link budgets that they use for modeling cell edge network throughput. Complete details of the data to be submitted biannually can be found in the Data

Specification for Biannual Submission of Subscription, Availability, and Supporting Data document published by the FCC at https://us-fcc.app.box.com/v/bdc-availability-spec.

On-the-ground speed tests are significant in both the BDC mobile challenge and verification processes. The FCC views actual on-the-ground test data (as opposed to infrastructure data) generally to be more reflective of user experience and of more probative value. Mobile cognizable challenges must be supported by on-the-ground test data. The National Broadband

Map shows the 3G, 4G, and 5G coverage areas reported by each mobile wireless service provider. These maps reflect where subscribers should be able to receive mobile connectivity when outdoors or in a moving vehicle. If the information on mobile coverage submitted by a provider doesn’t match a bona fide subscriber’s experience, the subscriber can dispute that information by taking outdoor stationary or in-vehicle speed tests on their mobile device using the FCC Speed Test App. Please reference the FCC Consumer Guide on Drive Tests at:

https://www.fcc.gov/consumers/guides/drive-tests-and-other-speed-tests-conducted-validate-mobile-broadband-availability.

To support implementation of the audit requirements of the BDA, the FCC requires a Contractor for drive testing services to perform on-the-ground testing and data reporting on mobile broadband network performance and coverage in designated areas. Based on specific areas identified and parameters established by the FCC, the Contractor will be expected to perform functions including, but not limited to, developing drive test plans detailing the most efficient and effective drive test routes, providing estimates for the cost of drive test projects, supporting the management and planning of all drive test projects requested by the FCC, collecting and reporting of required drive test data, furnishing all hardware and materials necessary to conduct the testing. In addition, the vendor may need to furnish software, separate from the FCC Speed Test app, to conduct testing using equipment other than a wireless handset, such as an RF scanner.

2 For purposes of this PWS, “Offeror” is a potential vendor submitting an offer or bid to fulfill the requirements of this PWS. “Contractor” refers to the Offeror that is ultimately awarded the contract and must then perform the services described in this PWS in accordance with the terms of the resulting contract.

https://us-fcc.app.box.com/v/bdc-availability-spec https://www.fcc.gov/consumers/guides/drive-tests-and-other-speed-tests-conducted-validate-mobile-broadband-availability https://www.fcc.gov/consumers/guides/drive-tests-and-other-speed-tests-conducted-validate-mobile-broadband-availability

For Official Use Only (FOUO) 7

See Broadband Data Collection (BDC) Mobile Technical Requirements Order for additional information.

3 SCOPE

One Firm Fixed Price, Indefinite Delivery/Indefinite Quantity (IDIQ) Single Award Task Order

Contract (SATOC) will be awarded for Drive Testing Support Services. As further detailed in

Section 4, the FCC will define the scope of each “Drive Test” task order, providing the

Contractor with the key parameters required to develop a specific drive test plan and cost estimate for each task order. The Contractor shall use the FCC-provided parameters to develop a comprehensive drive test plan, which shall document the Contractor’s specific approach to fulfilling the requirements outlined in each task order and specify all labor, equipment, data, tools, software, and support needed to collect drive test data. The following general activities are required for the planning and execution of each Drive Test task order:

1. Task 1: Program Management – Includes all general program management activities, including, but not limited to, staffing, project management, contract financial management, status and progress reporting, quality control, risk management, and support for a range of potential stakeholder communications and briefings.

2. Task 2: Drive Test Planning – Includes activities related to developing and approving key aspects of a drive test plan with the FCC prior to commencing drive tests.

3. Task 3: Drive Test Data and Execution – Includes activities and requirements related to the collection of speed test data and providing the equipment, tools, and software used to collect the required data.

4. Task 4: Drive Test Outputs and Reporting – Includes activities related to reporting the results of drive tests in the form of key outputs, such as reports and data files.

5. Task 5: Special Projects (Optional Task) – At the FCC’s discretion, but only upon the

Contracting Officer’s written authorization to proceed, the Contractor shall support

Special Projects related to the task areas above for any given task order. Refer to Section

4.6 for additional details.

4 DETAILED REQUIREMENTS

A PWS will be provided for each Task Order outlining the specific requirements for each Drive Test. Once a Drive Test is identified, the COR and/or Contracting Officer will reach out to the Contractor for an initial quote. The Contractor shall provide drive testing services and collect on-the-ground measurements of the coverage and service performance of mobile broadband 3G, For Official Use Only (FOUO) 8

4G LTE, and 5G-NR networks in designated areas to support the FCC’s audit process. “Drive testing” as referred to throughout this PWS is defined as on-the-ground field testing, inclusive of both stationary and in-vehicle testing, as both may be required to sufficiently address the data collection requirements as described below.

The task areas detailed in this section represent the types of drive test support anticipated to be required and the general skills and experience necessary to provide the support, but they should not be considered an exhaustive list of all required support. As various challenge, verification, audit, and other BDC processes are rolled-out for the first time, there will necessarily be a period of process review and refinement that may result in additional types of related drive test support.

Additional details of the requirements related to FCC’s audit processes are provided in the

Mobile Technical Requirements Order and the Second Order and Third Further Notice.3 Please refer to Section 13 of this PWS for links to these and other important reference materials.

Specific requirements for each of the tasks defined in Section 3 are further detailed below.

4.1 TASK 1: PROGRAM MANAGEMENT

The FCC requires a range of program management support to manage the workload allocation, staffing, quality control, reporting, and administration of all activities under this support contract.

4.1.1 Program / Project Management & Administration

The Contractor shall provide a range of Program and Project Management support activities, including, but not limited to, staffing and workload planning and management, project management, contract financial management, status and progress reporting, quality control, risk management, and support for a range of potential stakeholder communications and briefings. As further described in Section 5 Deliverables, the Contractor shall work with the FCC to develop agreed upon templates to be used in providing periodic status reports and executive briefings upon request.

The Contractor shall develop an overall Program Management Plan, as defined below, by documenting a comprehensive approach to meeting the objectives and requirements outlined in the PWS. As described in Section 5 Deliverables, the Contractor shall work with FCC post award to finalize the draft Program Management Plan and its components submitted with its proposal. The overall Project Planning Documents shall include, at a minimum, the following elements:

• Project Management Plan including key activities, milestones, and government review/approval points throughout the period of performance;

3 Establishing the Digital Opportunity Data Collection; Modernizing the FCC Form 477 Data Program, WC Docket Nos. 19-195, 11-10, Second Report and Order and Third Further Notice of Proposed Rulemaking, 35 FCC Rcd 7460 (2020) (Second Order and Third Further Notice).

For Official Use Only (FOUO) 9

• Staffing Plan documenting personnel to be utilized on the effort and their qualifications, as well as the overall approach to ensuring availability of qualified personnel on an ongoing basis o If sub-contracting any portion of the work, please provide the name(s) and address(es) of all subcontractor(s) (if applicable) and a description of their planned subcontracting effort;

o See PWS Section 10 and Clause LOCAL-1 Security Requirements Suitability and

Security Processing for additional personnel requirements;

o See PWS Section 9 for additional requirements for the Staffing Plan;

• Quality Assurance Plan documenting the approach to be used to ensure high-quality and on-time delivery of the end product, including proposed key performance indicators

(KPIs). Recommended approaches include, but are not limited to, pilot test(s), periodic data checks (every two hours is recommended) to ensure that devices are collecting the relevant data, periodic equipment checks and regular maintenance performance on equipment, and daily verification of the collected data;

• Communications Plan including approach to engaging with FCC leadership and technical personnel to support the requirements of the PWS and provide progress updates as required. Additionally, the communications plan shall document the communications channels and escalation path within the Contractor’s organization for resolution of any critical issues unable to be resolved directly with the Contractor’s drive test team; and

• Data Management and Architecture Plan outlining the approach to data collection, data management, and data acquisition architecture. It is not anticipated that the

Contractor will require access to the FCC’s network or information systems that maintain challenge, crowdsource, and other BDC data—other than via the FCC’s Speed Test App.

This PWS includes provisions that would be applicable if it is determined that the selected Contractor will require direct access to the FCC network or information systems.

Offerors should indicate in their Project Planning Documents whether they anticipate requiring such access.

The FCC will work with the selected Contractor to review, update, and finalize the draft plans submitted in the Contractor’s proposal within the first 30 days following the award.

4.2 TASK 2: DRIVE TEST PLANNING

On a task order basis, the Contractor shall develop and submit a drive test plan and associated cost estimate to the FCC for approval prior to initiation of each Drive Test. The following sections elaborate on the drive test planning requirements. While the process of developing inputs for the drive tests will be collaborative, the Contractor is ultimately responsible for developing each element of the drive test plan and ensuring the plan meets the FCC’s requirements.

For Official Use Only (FOUO) 10

4.2.1 Information Provided By the FCC

To support the Contractor’s drive test planning process, the FCC will work with the Contractor to provide certain information necessary to design an effective drive test plan and collect the data specified in this PWS. The information the FCC will provide includes, but is not limited to, the following:

1. Geographic area in which drive testing is to be conducted. Area may be based on different underlying boundaries depending on the needs of the FCC (e.g., census blocks, cities, towns, rural areas, H3 geospatial indexing system) and will be determined at the time of the planning process.4

2. List of public locations (e.g., latitude, longitude) within the geographic area where stationary and/or in-vehicle tests must be taken. The FCC will specify a list of locations of interest for auditing needs where drive test data must be collected. While the Contractor will be required to collect data at these specific locations, the Contractor must also gather data throughout the agreed-upon test route per the approved drive test plan.

Additionally, FCC will consider any recommendations the Contractor makes on the geographic locations or routes within the geographic area where tests may be taken.

3. The minimum number of tests required at each location. This may include specific time windows to test or specific time differences/intervals between tests. For example, FCC may require two sets of four tests taken at least four hours apart within a three-block radius of a location.

4. Technologies, environment (stationary/in-vehicle), and frequency bands to be tested.

5. The operators/providers to be tested. The FCC will specify a list of mobile providers whose network services and coverage need to be tested.

6. Data on where provider network infrastructure is located (under limited circumstances).

Under certain circumstances, the FCC may provide the Contractor with data that the Contractor would be unable to parse from the measurement (e.g., cell loading), assuming such data is needed for analysis and report generation. The FCC will work to provide all information with reasonable lead time before the Contractor conducts the drive tests to ensure testing is conducted in the most effective and cost-efficient manner.

7. Data to be collected. The type of data to be collected and the formats in which it must be submitted are defined in Section (4.3). However, the FCC may make future modifications or additions to the data specified depending on the needs of specific drive test projects.

8. In the event FCC requires an audit to be completed in an expedited timeframe, FCC will notify the Contractor as to whether more than one drive test team is needed to complete the testing within the required timeframe.

4 See Mobile Technical Requirements Order, para. 41, for a discussion of the H3 geospatial indexing system.

For Official Use Only (FOUO) 11

9. Any other information per the agreed-upon drive test plan. The list provided above is not intended to be exhaustive. The FCC will work with the Contractor to determine any new inputs required to improve the efficiency and effectiveness of the planning process.

All data is subject to applicable limitations. If the drive test plan requires the provision of any data that is confidential, proprietary, non-public, or is otherwise deemed by FCC staff to require protection to ensure the security, confidentiality, or privacy of data, the Contractor must maintain the confidentiality of such information.

4.2.2 Contractor Drive Test Planning Requirements

Based on the information provided by the FCC in 4.2.1, the Contractor shall propose a drive test plan for each Task Order documenting the detailed methodology and approach for conducting the requested testing and a proposed cost for executing the plan. The Contractor shall make all necessary arrangements to successfully execute the project. FCC shall review data collection processes, methodologies, and tools proposed in the plan by the Contractor. FCC review and acceptance of each drive test plan shall be required before any testing is conducted.

While the planning process will include input from the FCC, the Contractor is ultimately responsible for developing a drive test plan that most efficiently and effectively meets the objectives of each drive test effort based on the parameters defined by the FCC. The Contractor’s drive test plan shall, at a minimum, address the following elements:

1. Confirm the data to be collected under the plan, as well as any other inputs and parameters defined during discussions with the FCC. (Reference section 4.2.1)

2. Describe the data collection methodologies to ensure the data collected are robust, accurately characterize network performance/coverage, and meet the specifications described by the FCC. In particular, the Contractor shall include any actions necessary to account for data caps associated with a specific provider’s plans and limits, such as using multiple devices with sufficient data plan capacity to prevent being de-prioritized during testing. Please see the Mobile Technical Requirements Order, Technical Appendix § 3, available at https://www.fcc.gov/document/fcc-releases-bdc-mobile-technical-requirements-order.

3. Design the approach for conducting drive testing in the specified geographic area. The plan shall include a proposal for the routes to be driven, number of days of testing, times of day for testing, approach to monitoring data usage to prevent de-prioritization, and other key parameters required to ensure accurate and valid results. In addition, the plan should clearly lay out the different stages of testing (where applicable) and the time periods within which testing is estimated to be completed.

4. Approach for sourcing and providing all hardware (e.g., vehicles, equipment, tools) required to execute the drive test plan. If the Contractor procures certain equipment and tools to meet the needs of this contract specifically, the Contractor shall also develop and

For Official Use Only (FOUO) 12 provide a plan for storing and securing such procured equipment and tools for use in conducting any future tests for the FCC.

5. Approach for sourcing and providing all software (e.g., speed test app, post-processing software, mapping software) required to execute the drive test plan. The Contractor shall indicate where any of these tools are specialized or proprietary, and if so, ensure that these tools are fully compatible with BDC System requirements. Please see BDC Bulk Mobile Speed Test Submissions Process Public Notice available at https://www.fcc.gov/document/broadband-data-collection-bulk-mobile-speed-test-submissions-process. The Contractor must also indicate whether the use of such tools imposes any additional cost or limitations on the FCC’s transferring, use, or analysis of collected data.

6. Approach to staffing the Drive Test, including the number and type of personnel utilized across the planning, execution, and back-end reporting for each Drive Test. In addition, the plan should describe the working arrangements of the staff, for example, whether they are full-time staff or contractors and whether they are personnel previously utilized under this contract.

7. Provide a cost estimate for the drive test project detailing all cost components and the total cost required to complete the drive test plan (see additional details in 4.2.3).

8. Approach to providing drive test results to the FCC in a timely manner, including the formats within which data will be submitted (e.g., drive test log files in a raw data file).

Refer to Sections 4.3 and 4.4 for additional data and reporting requirements.

The FCC will review and either approve or request modifications to the plan based on an assessment of the efficiency, thoroughness, and cost-effectiveness of the proposed approach.

4.2.3 Drive Test Plan Cost Proposal

As part of each Drive Test Plan, the Contractor shall propose a Firm Fixed-Price total cost estimate for conducting each Drive Test. The Drive Test cost estimate shall document all required labor, materials, and travel costs required to execute the plan.

Labor

Proposed labor cost shall specify the labor categories to be used in executing the Drive Test Plan and the proposed number of hours required to execute the plan. The required hours should include documentation substantiating the labor requirements based on the proposed number of days of testing and other parameters in the Drive Test Plan. Labor costs should be inclusive of time required to complete any final reporting requirements after the field testing is completed per PWS Task 4 below.

Material

The Contractor is expected to provide all materials required to conduct their core business such as computers, software, office supplies and other general materials required to conduct business for any customer. The FCC will not reimburse such costs under the materials CLIN.

https://www.fcc.gov/document/broadband-data-collection-bulk-mobile-speed-test-submissions-process https://www.fcc.gov/document/broadband-data-collection-bulk-mobile-speed-test-submissions-process

For Official Use Only (FOUO) 13

The FCC will reimburse the Contractor for reasonable costs for equipment and provider service plans required in order to execute an approved Drive Test Plan. Such costs shall be clearly enumerated in the Drive Test Plan cost proposal along with explanation and documentation for how the costs were derived.

Allowable reimbursable materials costs include the items listed below.

• Android Devices & RF Scanner Equipment – Reasonable lease/rental costs for approved mobile handsets and RF scanner equipment required to conduct the drive test.

Documentation/explanation for how the daily rental costs were derived is required in order to assess price reasonableness.

• Provider Service Plans – FCC will reimburse the Contractor for the approved number and type of provider services plans specified in the approved Drive Test plan. The Contractor shall provide documentation substantiating the costs and will be reimbursed for the actual costs incurred – no markup shall be added to these costs.

Other materials outside of the equipment and service plans noted above are not reimbursable and shall be the responsibility of the Contractor.

Travel Costs

As part of its staffing plan, the Offeror shall describe its approach to ensuring qualified personnel are able to be deployed across the 50 States and all U.S. Territories for potential drive tests.

The contractor shall ensure that the requested travel costs shall not exceed what has been authorized in each task order. Contractor-incurred actual expenses resulting from Government-directed travel are cost reimbursable but are limited by the Federal Travel Regulation (FTR).

Travel Requests must be submitted at least 5 business days prior to any travel start dates and pre-approved in writing by the Contracting Officer or COR prior to travel. Failure to comply with this requirement may result in rejection of invoices and/or non-payment. Specific travel locations and the duration of travel cannot be established at this time. Travel will be negotiated and awarded firm fixed-price at the task order level.

A Contractor-generated travel authorization request shall be submitted to the COR or Contracting Officer and approved prior to beginning any travel. The form must identify the traveler’s name, travel dates, location(s), per diem rates, purpose of trip, all estimated expenses (i.e., lodging, lodging tax, M&IE, transportation air fare, train, bus, rental car, fuel for rental car, private car mileage, registration, tolls, parking, other related expenses), and a funding validation reflecting an estimate of the trip total and the remaining travel funds available after the travel being authorized is completed. A summary report shall be included with each invoice requesting travel reimbursement identifying each trip, and traveler, location, dates of travel, approved amount estimated, amount invoiced and delta, along with an electronic copy of the travel expense summary and receipts submitted with the monthly invoice.

For Official Use Only (FOUO) 14

The FCC will reimburse the Contractor for approved travel costs in alignment with the Federal Travel Regulation (FTR). The FTR summarizes the travel policy for all federal civilian employees and others authorized to travel at the government’s expense (refer to eCFR for full details https://www.ecfr.gov/current/title-41/subtitle-F).

The General Services Administration (GSA) publishes per diem rates governing allowable expenses for common travel expenses including hotels, meals and incidentals, and mileage reimbursement rates for use of privately owned vehicles. The Contractor shall operate within the published limits for the region or location to which they are traveling to conduct FCC business.

(See https://www.gsa.gov/travel/plan-book/per-diem-rates).

Local travel is defined as travel of fewer than 50 miles between the traveler’s primary residence and the work location. Such general commuting expenses for Contractor employees are not reimbursable under this contract and shall be the responsibility of the Contractor. Approved travel greater than 50 miles from the traveler’s primary residence is reimbursable in accordance with the FTR and COR approval as described above.

In addition, the Contractor must adhere to the following requirements while renting cars.

1. Reimbursement for car rental will normally be limited to an economy through full size car at the time of travel. Reimbursement for luxury car will be determined on a case-by-case basis, generally if the luxury car is cost comparable to a lesser class car.

2. A one-way drop charge should not be incurred unless it is the least expensive alternative.

3. Contractor should fill up the gas tank before returning the car to avoid a costly gasoline surcharge. Extenuating circumstances must be documented for a surcharge to be reimbursed.

4. Any unneeded car rental reservation must be cancelled in a timely manner. Unused reservation charges are not reimbursable without appropriate business justification.

4.2.4 Reasonable Notice, Approval and Other Factors

The Contractor will have 60 calendar days’ notice to begin collecting drive test data from the date the FCC has formally submitted a Task Order request for a drive test to be conducted for a specific area. This period will be divided into three phases – planning, preparation, and execution.

Drive Test Planning (Up to 30 Days)

The objective is to develop an FCC-approved Drive Test plan within 30 days of request. Each drive test task order request will specify the required timeframes, which may vary based on the scope and complexity of the specific drive test or other factors (e.g., expediated requirement).

However, general target timeframes are:

• Contractor develops and submits draft Drive Test plan and cost proposal (7-10 days)

• FCC reviews proposal and provides suggested revisions to Contractor (7-10 days) https://www.ecfr.gov/current/title-41/subtitle-F https://www.gsa.gov/travel/plan-book/per-diem-rates

For Official Use Only (FOUO) 15

• Contractor and FCC negotiate final cost and Drive Test plan technical approach, FCC approves plan for execution (7-10 days)

These timeframes are the standard targets for the planning phase, however, if circumstances warrant, FCC may approve modifications to these timeframes for specific Drive Test planning efforts.

Drive Test Preparation (Up to 30 Days)

The preparation phase provides additional lead time for the Contractor to ensure availability of required personnel and equipment as well as arrange travel (if required) following approval of the Drive Test Plan. After the plan has been approved by the FCC, the Contractor shall have 30 days to begin executing drive tests. During this time, the Contractor shall make all necessary arrangements to execute the drive test plan. As with the planning phase, these timeframes are the standard targets for the preparation phase, however, if circumstances warrant, FCC may approve modifications to these timeframes for specific Drive Test efforts.

Drive Test Execution

Because individual Drive Tests may vary in complexity and duration, the timeframe for execution of each Drive Test will be specified in the approved Drive Test plan. The Contractor shall meet all agreed-upon timeframes specified in the approved plan unless otherwise explicitly approved by the FCC.

Drive Test Reporting

The FCC expects aggregation of all data collected and delivery of all data and deliverables specified in Task 4 within 7 calendar days after each Drive Test plan is fully executed. At FCC discretion, this timeframe may be adjusted based on specific circumstances of each Drive Test.

For more details on deliverables and their respective timelines refer to Section 5.

Summary

The table below summarizes the target timeframes across all phases of the Drive Test planning and execution process. While under certain circumstances the FCC may request expedited timeframes or agree to extended timeframes, the objective is to execute each Drive Test within the timeframes below.

Phase Timeframe Details

Planning Up to 30 calendar days Drive Test plan and cost proposal drafted by Contractor and approved by FCC

Preparation Up to 30 calendar days Contractor secures personnel, equipment, and travel arrangements to execute test

Execution Based upon approved Drive Test plan

Contractor executes Drive Test Plan

For Official Use Only (FOUO) 16

Reporting Up to one week from last day of testing

Contractor compiles all test results and provides required outputs/deliverables to FCC

4.3 TASK 3: DRIVE TEST EXECUTION AND DATA COLLECTION

4.3.1 Data Requirements

The objective of performing drive tests is to gather on-the-ground speed tests and RF measurement data to independently audit whether mobile providers are meeting their claimed standards for network performance and coverage. Assessing network performance includes conducting on-the-ground speed tests to confirm providers are meeting technology-specific downlink and uplink speeds and associated signal strengths. Network coverage assessments focus on analyzing whether the coverage maps reported by mobile providers are accurate.

See paras. 38-51, Broadband Data Collection (BDC) Second Report and Order and Third

Further Notice of Proposed Rulemaking, FCC 20-94, July 17, 2020, for additional information. (https://www.fcc.gov/document/fcc-improves-broadband-data-and-maps-bridge-digital-divide-0).

All data collected by the Contractor as part of the drive testing effort are the exclusive property of the FCC and may not be shared with third parties (other than the FCC Speed Test application, which shall be utilized to conduct drive testing).

Speed Test Data

Data and measurements to be collected by the Contractor are incorporated by reference and outlined in the Data Specifications for Mobile Speed Test Data available at: https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec. These data are material components to each Task Order.

RF Scanner & Other Data

The Contractor is required to collect RF Scanner data during each drive test in addition to the data collected by the FCC app. RF Scanner results shall be grouped by:

• Radio Access Technology: 3G, 4G LTE, 5G NR

• Mobile Network Operator

• Downlink Radio Frequency and Bandwidth

• Uplink Radio Frequency and Bandwidth

• Cell Identity

RF Coverage statistics to be collected are, at a minimum:

• Received Signal Power (RSCP, RSSI, RSRP, SS-RSRP),

• Received Signal Quality (EcNo, RSRQ, SS-RSRQ),

• Signal to Interference and Noise Ratio (SNR, SINR. SS-SINR).

https://www.fcc.gov/document/fcc-improves-broadband-data-and-maps-bridge-digital-divide-0 https://www.fcc.gov/document/fcc-improves-broadband-data-and-maps-bridge-digital-divide-0 https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec

For Official Use Only (FOUO) 17

Note that the FCC does not expect, require, or want personally identifiable information (PII) about the individuals conducting the drive tests, except and only insofar as that information is collected automatically (e.g., via the FCC Speed Test Application).

See section III.A.1. and Appendix A, sections 2-3, Broadband Data Collection (BDC) Mobile

Technical Requirements Order, for additional information.

4.3.2 Data Collection Process

As a part of its drive test solution, the Contractor shall provide all software (except for the FCC Speed Test App) and hardware required to collect the data described in this PWS and specified in the drive test plan. During the planning phase, the Contractor shall describe its approach to providing all required equipment and software. While the specific hardware and software needs may change based on the requirements of each individual drive test, the following section describes the Contractor’s responsibilities regarding hardware and software. Please note that this list is not exhaustive and may be amended per the specifics of each drive test plan.

Hardware Requirements

The Contractor shall provide at least one dedicated device for each operator and technology combination being tested (e.g., separate device for 4G vs 5G for a given carrier if both technologies are to be tested). All devices shall be Android devices to ensure capture of all required data and information. Devices shall only be used for purposes set forth in this PWS and other related supporting activities.

The Offeror must describe in its proposal how it plans to physically keep track of the devices in the vehicle while driving. The Offeror must describe the processes used during active testing for:

(i) keeping the devices properly positioned and free of obstacles; (ii) keeping the test devices’ batteries charged; and (iii) keeping the batteries’ temperature within the ideal operating range as device performance degrades if batteries are exposed to extreme temperatures.

The Contractor shall also provide and operate an RF scanner system during each Drive Test. RF channel quality testing in specific frequency bands must be tested via an autonomous RF scanner with the following features:

• Autonomous RF scanner should be capable of 3G, 4G-LTE and 5G-NR, self-contained, and automated such that minimal user interaction and technical skills are required to operate the system.

• The data that the autonomous RF scanner must be able to collect include, but are not limited to, RF carrier frequency, RSRP, RSRQ, SINR and PCI parameters for LTE and 5G-NR. The system shall be a turn-key solution inclusive of integrated software to facilitate post processing and automatic upload of the scanner data to a central server hosted by the Contractor and made accessible to FCC personnel for retrieving the data.

For Official Use Only (FOUO) 18

• The system must be inclusive of all antenna devices and supporting equipment required to perform readings of infrastructure and related data.

Exhibit 2 to the PWS provides additional details regarding RF Scanner technical requirements, as well as a sample approved scanner offered by Ranlytics that demonstrates the features and functionality required by the FCC for the RF scanner. As part of its technical response, the Offeror shall complete the Technical Compliance Matrix in Exhibit 2 and either certify that they intend to use the brand name scanner specified or provide the details of an alternative scanner that is equal to the brand-name product specified. Refer to Exhibit 2 for additional details.

Service Plan Requirements

The Contractor is responsible for acquiring all provider data plans required to ensure proper testing per the parameters agreed upon in each Drive Test Plan. Key considerations include, but are not limited to:

• Understanding the differences between available provider plans and ensuring use of “Premium level” plans that align with each provider’s optimal performance capabilities

• Understanding the data usage thresholds at which a given provider will begin restricting/throttling data speeds

• Ensure that plans can measure unrestricted/unthrottled speed throughout the Drive Test.

This may require direct negotiations with the provider if an unrestricted/unthrottled plan does not exist for the provider or may require a Drive Test Plan that incorporates use of multiple devices to ensure maximum data thresholds are not exceeded during the Drive Test.

Software Requirements

The FCC requires that the Contractor use the FCC Speed Test App to ensure the collection of all required data in a format compatible with the FCC’s BDC System. The FCC app may also require use of a macro to automate the frequency of collecting speed test data (e.g., running a speed test once per minute). The FCC will work with the selected Contractor to provide the most current version of the FCC Speed Test App for use in each drive test conducted.

The Contractor shall provide all other required software necessary to execute the agreed-upon drive test plan including, but not limited to, the following:

• Any required RF scanner software compatible with the selected hardware

• Any additional software required for post processing and analysis of data collected

4.3.3 Geographic Scope

For Official Use Only (FOUO) 19

The FCC may require drive test support services in all 50 states, the District of Columbia, and all U.S. territories (e.g., U.S. Virgin Islands, Puerto Rico, Guam, etc.). The Contractor shall ensure that their approach to drive test planning incorporates capability to provide services across this entire geographic scope. If partnering/subcontracting is required, the Contractor shall provide appropriate oversight and management of the Contractor team to ensure a seamless customer experience to the FCC across all partners/subcontractors.

4.4 TASK 4: DRIVE TEST OUTPUTS AND REPORTING

4.4.1 Drive Test Outputs

While additional specifics may be provided at the task order level, for each drive test plan executed, the Contractor shall provide the following deliverables/outputs:

• Summary Report – The FCC will work with the Contractor post award to finalize the specific format and content of the summary report. The report shall contain, at a minimum, a narrative of the drive test scope, timeline, drive test route, test methodology used, test devices used, test plans used, radio access technologies tested, mobile network operators tested, geographical areas tested, list of stationary locations tested, and testing notes citing any issues encountered or deviations from the drive test plan. Note that the FCC does not expect, require, or want PII about the individuals conducting the drive tests, except and only insofar as that information is collected automatically (e.g., via the FCC Speed Test Application).

• Active Performance Tests Data Files collected from the test devices, including details about the on-the-ground speed tests conducted, fully conforming with the BDC Mobile Speed Test Data Specifications (https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec).

• Passive Coverage Tests Data Files containing the RF scanner logs collected and CSV data (e.g., provider, timestamp, latitude, longitude, altitude, technology, pci1, freq1, bandwidth1, rsrp1, rsrq1, rssi1, sinr1, pci2, freq2, bandwidth2, rsrp2, rsrq2, rssi2, sinr2, etc...).

• Radio frequency coverage measurements obtained from the RF scanner, including, at a minimum, Received Signal Power (RSCP, RSSI, RSRP, SS-RSRP), Received Signal Quality (EcNo, RSRQ), and Signal to Interference and Noise Ratio (SNR, SINR, SS- SINR), grouped by:

− Radio Access Technology: 3G, 4G LTE, 5G NR

− Mobile Network Operator

− Downlink Radio Frequency and Bandwidth

− Uplink Radio Frequency and Bandwidth

− Cell Identity

4.4.2 Transfer of Data

For Official Use Only (FOUO) 20

At the conclusion of a drive test, both speed test and RF scanner data specified above must be exported from test devices and uploaded to a central server hosted by the Contractor and made accessible to FCC personnel for retrieval.

While the FCC is requesting manual exports of data, the Contractor should be aware that data collected from the FCC Speed Test App is automatically uploaded to the BDC system. The Contractor will work with the FCC to provide identifying information related to devices and plans used to run the FCC Speed Test App such that speed test data collected during such drive tests can be easily identified within the BDC system.

4.5 TASK 5: SPECIAL PROJECTS (OPTIONAL TASK)

At the FCC’s discretion but only upon the Contracting Officer’s written authorization to proceed, the Contractor shall provide services to support Special Projects to provide additional analytical, consulting, and advisory support related to the task areas above. This optional work may be issued under any Task Order as a time and material or labor-hour basis within the ceiling established under the task order, or may be performed on a Firm Fixed Price basis.

As technology and FCC needs change, or when special situations arise, this optional task provides the flexibility for the FCC to obtain from the Contractor additional support for other requirements relating to Tasks 1-4, and other related requirements, as may be necessary.

Optional Task Exercise Procedure

Work under Optional Task 5 may be included under a Task Order, by the Government. When an optional task is considered, the FCC shall send the Contractor a work plan, which shall detail requirements, deliverables, and timelines and provide a labor-hour estimate or firm fixed price and proposed ceiling amount to accomplish the work in the plan. The Contractor may be asked to provide feedback on the work plan, and a final work plan will be determined by the Contracting Officer, setting forth final requirements and a ceiling amount for the work.