Attachment 1 - PWS_BDC_Prop Modelling SW Integration.pdf

For Official Use Only (FOUO)

Federal Communications Commission

Broadband Data Collection

Wireless Propagation Modeling Software & Integration

Performance Work Statement

14 June 2022

Prepared by:

Federal Communications Commission

Office of Economics and Analytics

45 L Street NE

Washington, DC 20554

BDC Wireless Propagation Modeling Software & Integration

For Official Use Only (FOUO) 2

CONTENTS

1 BACKGROUND

2 OBJECTIVES

3 SCOPE

4 DETAILED REQUIREMENTS

4.1 Task 1: Propagation Modeling Tool Software Licenses & Maintenance Support

4.1.1 PMT Software Technical Requirements

4.1.2 Software Maintenance & Support Requirements

4.1.3 PMT Software Deployment Approach

4.1.4 PMT Software Licensing Model

4.2 Task 2: Software Integration and Automation Services

4.2.1 Integration Overview

4.2.2 Integration Timeframe

4.3 Task 3: Provision of Geographic Data Inputs for the PMT (“GeoData”)

4.3.1 Required Base GeoData Included in the Proposed PMT

4.3.2 Optional Additional GeoData

4.4 Task 4 (OPTIONAL): Special Projects

5 DELIVERABLES

6 GOVERNMENT-FURNISHED PROPERTY, MATERIAL, EQUIPMENT, OR

INFORMATION

7 PLACE OF PERFORMANCE

8 PERIOD OF PERFORMANCE

9 LABOR CATEGORIES

10 SECURITY & PRIVACY

10.1 Cybersecurity Training

10.2 Incident Response

10.3 Breach Response

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

11.6 Documentation

12 EXHIBITS

For Official Use Only (FOUO) 3

Performance Work Statement

1 BACKGROUND

The Broadband DATA Act (BDA), enacted in March 2020, requires the Federal

Communications Commission (FCC) to improve the quality of broadband availability data it collects. Among other provisions, the BDA requires the FCC to establish processes to verify coverage data collected from fixed and mobile wireless broadband service providers. Mobile broadband service providers must submit network coverage maps based on standardized propagation model parameters, as well as supplemental data about how the maps were generated to support their broadband coverage claims. Similarly, fixed wireless broadband service providers must submit broadband availability data in the form of either propagation maps and model details or a list of address or locations; if the provider submits coverage maps, it must provide additional information with its maps and model details. Moreover, mobile wireless service providers may submit on-the-ground speed test data or infrastructure data (or both), as well as potentially other data, as part of the FCC’s mobile challenge and verification processes.

See Broadband Data Collection (BDC) Mobile Technical Requirements Order, DA 22-241, Mar 9, 2022 (https://www.fcc.gov/document/fcc-releases-bdc-mobile-technical-requirements-order).

The Commission’s Broadband Data Task Force has designed and is developing 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. Service providers and governments will use these broadband maps to make decisions about where service is needed and how to fund the expansion of broadband services.

2 OBJECTIVES

To support implementation of the BDA requirements, the Commission requires an industry-leading software solution/automation platform and Propagation Modeling Tool (hereafter

“PMT”) that provides (1) capability to conduct propagation modeling for commercial wireless services, (2) access to various geographic data (GeoData) sources as inputs to the PMT, and (3) software integration support services to integrate the PMT with the BDC System. Through integration of the PMT with the BDC System, the FCC is seeking to:

• Enhance the FCC’s ability to accurately assess and verify coverage maps and related data submitted by service providers as part of the BDC challenge and verification processes;

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

For Official Use Only (FOUO) 4

• Automate the process for ingesting data from the BDC System via an Application

Programming Interface (API) and analyzing and validating that data using propagation modeling to assess fixed and mobile wireless coverage quickly and efficiently;

• Ensure access to various GeoData sources required to conduct specific analyses as they are identified (e.g., assess a specific coverage challenge in a specific region)

• Produce outputs of the analytical propagation modeling results in a format or formats specified by the FCC that can be transmitted to the FCC’s BDC System via an API; and

• Acquire maintenance and support for the propagation modeling tool and API throughout the contract period of performance.

The Commission is seeking a Contractor with the capabilities to provide a propagation modeling tool (including ongoing maintenance and support), access to required GeoData sources, and professional integration services, as a turnkey solution. Specific technical requirements are further outlined below.

3 SCOPE

As further detailed in Section 4, the government requires support in three primary task areas:

1. Propagation Modeling Tool (PMT) Software Licensing and Maintenance Support –

Includes the purchase of or access to a PMT for modeling radio frequency propagation and network planning for commercial wireless services under requirements and parameters determined by the FCC, as well as associated maintenance support including, but not limited to, patches, security enhancements, product upgrades, and help desk support. This Task area also includes the option to purchase additional licensing throughout the period of performance to support potential future system expansion.

2. Software Integration and Automation Services – Includes integration of the PMT with the FCC’s BDC System via an API that is provided, developed, and customized by the

Contractor to meet FCC requirements; full system testing (including security and end-user testing) of the API integration, including the initial provision of GeoData as required by the propagation models; and system documentation and end-user training and reference materials.

3. Provision of Geographic Data Inputs for the PMT – Includes the initial provision of

GeoData sources as required by the propagation models to support initial implementation and testing of the PMT and the integration of the PMT with the BDC System. This Task area also includes the option, at the government’s discretion, to acquire various additional

GeoData sources from the Contractor that may be required as inputs to the PMT to support future analyses as they are identified (e.g., verification analyses to support a specific coverage availability data filing from a provider or a challenge data submission).

For Official Use Only (FOUO) 5

4. Special Projects (Optional Task) – At the government’s discretion during any performance period, but only upon the Contracting Officer’s written authorization to proceed, the Contractor shall support Special Projects related to the software, integration services and/or GeoData task areas above. Refer to Section 4.4 for additional details.

4 DETAILED REQUIREMENTS

Specific requirements for each Task Area are further detailed below.

4.1 Task 1: Propagation Modeling Tool Software Licenses & Maintenance Support

The FCC requires a software solution for commercial wireless service propagation modeling and planning, and associated maintenance and support services. Specific requirements in each of these areas are outlined below.

4.1.1 PMT Software Technical Requirements

The Offeror’s proposed PMT software shall support the features and capabilities described below. The Offeror’s technical approach shall address how the proposed PMT meets or exceeds each of the requirements below. The Offeror’s response must be structured to align with the six

(6) subsections below.

4.1.1.a Wireless Infrastructure Support

• PMT shall support the ingest and/or import of data – including, but not limited to, infrastructure, propagation modeling, link budget, and terrain and clutter data – related to the deployment of multiple mobile wireless network technologies, including 5G-NR, 4G

LTE, 3G UMTS/HSPA, 3G CDMA, as well as terrestrial fixed wireless (TFW) technologies (e.g., 802.11ax).

• Offeror shall describe how the PMT supports multiple frequency plans, carrier aggregation and scalable carrier bandwidths.

• PMT shall be capable of importing 2D and 3D antenna pattern data provided in well-known file formats (e.g., MSI or NSMA). Provide a listing of the antenna pattern file formats supported by the PMT.

• PMT shall support massive MIMO and 3D/2D beamforming antennas specifications and be capable of using them in analyses.

For Official Use Only (FOUO) 6

4.1.1.b Modeling Support

• PMT shall support empirical, deterministic, and hybrid propagation models and model tuning for Sub-6 GHz and millimeter-wave spectrum (e.g., Okumura-Hata and Cost-Hata, Irregular Terrain Model-Longley Rice, Ray Tracing, ITU-R, 3GPP).

o Offeror’s response shall include a description of the propagation models supported by the PMT and specify the required input parameters for simulating each model, including geographic data (“GeoData”) such as terrain, clutter, building/street data and/or other necessary environmental factors.

• Offeror shall describe the methodology the PMT employs to support the tuning of standardized or customized propagation model types or building adaptive propagation models based on imported public and anonymized challenge and crowdsourced data elements for Sub-6 GHz and millimeter-wave spectrum. Offeror shall explain how the

PMT supports the use of crowdsourced (e.g., on-the-ground) measurement data, including imported challenge and crowdsourced data elements, for analysis, including comparison with predictions of propagation models.1

• PMT shall support the capability to convert propagation modeling results from raster to vector format (e.g., ESRI shape files).

• PMT shall support the generation of predicted coverage maps for a selected geographical area (e.g., state, county) with specified loading factor per cell(s) at a specific parameter value including signal strength, Received Signal Strength Indicator (RSSI), Reference

Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to

Interference and Noise Ratio (SINR), upload (UL) and Download (DL) speed data (i.e., throughput). The predicted coverage maps for a selected area shall be generated using input parameters passed to it from the BDC System. Input parameters could include propagation model, terrain and clutter resolution as well as other model-appropriate parameters (see related requirement for importing infrastructure data in Section 4.1.1.e).

• Offeror shall explain how the PMT supports network and public and anonymized challenge and crowdsourced speed test data comparison with selected clutter categories, including propagation model optimization, clutter loss optimization, and clutter height and dB/m loss customization for each category.

1 The FCC will provide only challenge and crowdsourced data elements that are anonymized or otherwise have been made public, the latter of which, under the BDC Third Report and Order, include the location that is the subject of a challenge. Establishing the Digital Opportunity Data Collection; Modernizing the FCC Form 477 Data Program, WC Docket Nos. 11-10 and 19-195, Third Report and Order, 36 FCC Rcd 1126, 1174, para. 125 (2021). The FCC will not provide any other challenge or crowdsource data elements that include or could reveal personally identifying information, such as contact_name, contact_email, contact_phone, server_timestamp, server_source_ip_address, server_source_port, device_imei, device_id.

For Official Use Only (FOUO) 7

• Offeror shall explain how the PMT supports the implementation of the statistical aspects of beamforming and/or MIMO antennas in service predictions for both the broadcast control channel and data channel coverage.

Additional Preferred Capabilities

• Offeror shall indicate whether the PMT has the capability to support spatial interpolation techniques, such as Kriging, to predict coverage maps using public and anonymized challenge and crowdsourced data. If so, Offeror’s response shall include a description of the simulation process to predict coverage maps.

• Offeror shall indicate whether the PMT supports the capability to divide a geographical

(i.e., targeted) area into hexagonal units based on Uber’s H3 Hexagonal Hierarchical

Spatial Index. If not, Offeror’s response shall confirm whether this capability can be added and describe the complexity and costs involved to do so.

• Offeror shall describe whether the PMT has the capability to incorporate high (1-5m) and medium (10-30m) resolution terrain data, clutter, building, street, tree, and other geographic data to produce and support propagation modeling.

4.1.1.c Data Support

Offeror shall describe how the PMT supports and uses the following datasets, and how these datasets interact with and affect the prediction models:

• Terrain elevation data. The PMT shall support the import of digitized terrain data with minimum 10m resolution for CONUS in different formats (e.g., BIL, USGS GeoTIFF

Digital Elevation Models (DEM), BMP, Erdas, ArcGIS, Binary, and others);

• Clutter class (e.g., USGS Land Use and Land Cover Data (LULC) and clutter heights data of minimum 30m resolution for CONUS;

• Infrastructure and cell loading data;

• 2D vector data, including roads, streets, etc.;

• 3D urban vector data, including building contours and heights, and trees;

• Public and anonymized challenge and crowdsourced measurements (e.g., on-the-ground) data in multiple file formats including (*.hd), multi-import files (*.ami), and CW measurement files (*.dat, *.txt, *.csv); and

• Public and anonymized challenge and crowdsourced test data elements imported from the

BDC System (fields as described in the BDC “Data Specifications for Mobile Speed Test

Data” – see https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec).

https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec

For Official Use Only (FOUO) 8

4.1.1.d Projects and Batch Processing

Offeror shall describe how the PMT supports multiple projects and batch processing.

• PMT shall have the ability to create projects and track versions of different infrastructure and model results.

• PMT shall have the ability to support batch processing.

4.1.1.e Architecture and Interfaces

• Software Solution shall be made available as a web service (e.g., Software-as-a-Service

(SaaS)) or else shall be deployable as a containerized image in the FCC’s cloud environment (e.g., Docker image, Amazon Web Services image, etc.). Offeror’s response shall document/confirm supported architectures.

• Any external cloud solution shall have at least one of the following certifications that is valid as of the date of proposal submission: FedRAMP Moderate (preferred), ISO 27001 certification, or Cloud Security Alliance STAR Level 2 certification. For the preferred

FedRAMP certification, ensuring that the software itself is FedRAMP certified (Software as a Service) is the most preferable, followed by certification of the platform (Platform as a Service) and lastly the infrastructure (Infrastructure as a Service).

o Offeror shall provide documentation, including the relevant SOC 2 report, as part of their technical response confirming that the certification(s) held are valid as of the date of proposal submission.

o Upon award, Contractor shall work with FCC IT to ensure the proposed solution complies with all FISMA requirements.

• Software shall be capable of supporting IPv6 and end-to-end encryption in transit and at rest. Software supporting IPv4 and IPv6 concurrently is acceptable, however, in this case the Offeror shall confirm that disabling IPv4 will not change the functionality or security of the software.

• Offeror shall submit as part of their technical response a complete Software Bill of

Materials (SBOM) as defined in Executive Order 14028. The SBOM shall follow the

Minimum Elements for Software Bill of Materials (SBOM) developed by the US

Department of Commerce.

• Software Solution shall be flexible and scalable to support future expansion of deployment (e.g., cloud based). Offeror’s response shall provide details regarding options to scale/expand the proposed solution in the future, if required.

• The Offeror shall specify the required architecture (e.g., CPUs) for the PMT to support the number of the users defined in Section 4.1.4 and ensure optimal performance of its intended function.

https://www.ntia.doc.gov/files/ntia/publications/sbom_minimum_elements_report.pdf

For Official Use Only (FOUO) 9

• Solution shall have a documented Software Development Kit (SDK) and/or support for industry-standard APIs (e.g., COM and/or REST) for integration with automated tools.

• PMT shall support the import of the infrastructure data elements described in BDC’s

“Data Specifications for Provider Infrastructure Data in the Mobile Challenge and

Mobile Verification Process” (see https://us-fcc.app.box.com/v/bdc-infrastructure-spec)

• PMT shall support the import of public and anonymized challenge and crowdsourced test data elements as described in the BDC “Data Specifications for Mobile Speed Test Data”

(see https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec).

4.1.1.f Analysis and Reporting

• Offeror shall describe how the PMT can be used to support the mobile provider infrastructure verification process as described in FCC DA 22-241 “Mobile Technical

Requirements Order (MTRO),” Section B.4.

• PMT shall have the ability to generate coverage maps and contours including technical details based on specified parameters such as signal level and UL/DL speed data (see

4.1.1.b).

• PMT shall have the ability to compare measured and predicted coverage and generate statistical analyses based on this comparison.

• PMT shall be capable of generating analysis (e.g., coverage) within a specified geographical area (e.g., state, county) defined by a vector that can be saved to a file with all the input and output technical details (e.g., infrastructure data and generated reports) and can be edited to add or remove technical data.

• PMT shall have the ability to export contours and coverage map/data in GIS vector, raster, or other common file formats (e.g., KML, SHP, TIF, etc.) at resolutions specified in BDC “Data Specification for Biannual Submission of Subscription, Availability, and

Supporting Data” (see https://us-fcc.app.box.com/v/bdc-availability-spec).

Additional Preferred Capabilities

• Offeror shall indicate whether the PMT has the capability to perform spatial interpolation techniques and if so, whether the PMT is able to generate and export the coverage maps, including technical details.

The Offeror’s technical approach shall address how the proposed PMT meets or exceeds each of the requirements outlined above and identify any capability gaps related to the specified requirements.

https://us-fcc.app.box.com/v/bdc-infrastructure-spec https://us-fcc.app.box.com/v/bdc-availability-spec

For Official Use Only (FOUO) 10

4.1.2 Software Maintenance & Support Requirements

The Contractor shall provide software maintenance support and end user support for the proposed PMT software. In its technical approach, the Offeror shall document the full range of support included in its proposed solution to include, but not limited to:

• Approach to providing access to updated features and functionality through regular software updates;

• Ensuring end-user customizations, if any, are preserved and fully functional following any significant software version updates;

• Approach to providing patches and other security updates required to maintain system security in accordance with FCC and broader Federal security policies and mandates;

• Approach to providing access to help desk support to respond to technical issues or end-user questions, including proposed days and hours of help desk operation; and

• Approach to providing access to self-service support through a range of technical and end-user reference documentation (e.g., technical manuals, FAQs, etc.).

See Section 4.1.3 below for additional maintenance and support requirements based on whether the PMT software is deployed as a hosted solution (i.e., SaaS model) or on FCC-owned and managed infrastructure.

4.1.3 PMT Software Deployment Approach

The Offeror’s technical approach shall specify whether the proposed PMT software is to be hosted on Contractor-owned infrastructure and delivered as a managed service (i.e., SaaS) or deployed on FCC-owned cloud-based infrastructure as a containerized image. If the Offeror’s proposed approach includes hosting of the PMT software, required datasets, custom designed modeling capability, or other FCC analysis/outputs on servers outside of the FCC environment, the Offeror shall also provide documentation of the following:

• The specific data, information, or capabilities to be hosted on infrastructure outside of the

FCC environment and the benefits of structuring the solution in this way;

• The Service Level Agreement (SLA) parameters applicable to the hosted solution, including, but not limited to, ensuring defined levels of system access/responsiveness, system availability/uptime, security standards, and other defined performance metrics according to the Offeror’s standard commercial practice;

• The Offeror’s approach to ensuring security of the PMT and associated data from unauthorized access or manipulation, including compliance with all applicable Federal and FCC cybersecurity policies;

For Official Use Only (FOUO) 11

• Evidence, such as a System Security Plan (SSP), policies or procedures, independent assessment or any equivalent documentation, that clearly demonstrates the hosted environment algins to and is compliant with NIST SP 800-171 "Protecting Controlled

Unclassified Information in Nonfederal Systems and Organizations" and NIST SP 800-

171 "Enhanced Security Requirements for Protecting Controlled Unclassified

Information: A Supplement to NIST Special Publication 800-171"; and

• The Offeror’s approach to providing data backup and disaster recovery support to ensure the software and data remain secure and accessible to FCC.

4.1.4 PMT Software Licensing Model

The Offeror shall propose a licensing approach aligned with its standard commercial practice and that the Offeror believes will provide FCC with a flexible, scalable, and cost-competitive solution throughout the period of performance. In its Technical Approach, the Offeror shall provide information regarding the following elements of the licensing structure for its proposed

PMT software.

4.1.4.a Licensing For the Initial Base Implementation

The Offeror shall propose the software product or products from its offering that are required to meet the capability requirements outlined in this PWS. As input to right-sizing the initial implementation PMT, the government provides the following estimates:

• User-Based License Metric: The government estimates an initial user-base of up to 10 concurrent users, with the potential to add additional users after the initial base implementation.

• Infrastructure-Based License Metric: The Offeror should use the technical requirements, workflow descriptions and BDC technical reference materials provided in the solicitation (including links and attachments) to assess the computing capacity (e.g., CPUs/cores) required to achieve the objectives and propose a licensing model and associated pricing that best fits those requirements.

4.1.4.b Potential Future Licensing

The government anticipates a potential need for additional licensing during the period of performance. The Optional Special Projects CLIN will be used to acquire future additional licensing requirements, if and when they are identified, to include the following:

• Expansion of the initial base licensing for the PMT to accommodate additional users or computing capacity, depending on the licensing metric proposed for the initial PMT implementation.

For Official Use Only (FOUO) 12

• Licensing for additional available tools, add-ons and/or modules, if any, that offer additional relevant capabilities that may be required in the future but are not needed to achieve the required capabilities in Section 4.1.1 for the initial implementation.

As part of its technical approach, the Offeror shall provide a list of all relevant expansion modules or add-on features that may be of future interest to the government. The list shall include a brief description of the additional capabilities offered by each optional feature and the relevance to the objectives and requirements of this PWS.

4.1.4.c Additional Licensing Details

The following additional details regarding the licensing model shall be clearly documented in the

Offeror’s technical response:

• Proposed software product(s) including product name, SKU/part number, and version number for each product proposed to achieve the required capabilities listed in Section

4.1.1

• Proposed licensing model (e.g., software subscription, perpetual license plus annual maintenance, etc.)

• Proposed licensing metric (e.g., # of cores, # of users, etc.) and quantities proposed.

o For user-based licensing approaches, a clear definition of “user” shall also be provided, including licensing requirements for “non-human” users (i.e., devices or systems accessing the software)

• Listing of all maintenance and support services included in the license costs (e.g., patches/upgrades, technical support, help desk access, etc.)

• Proposed approach and frequency of provisioning software updates

• If any third-party products are incorporated into the proposed solution, please describe the nature of the third-party products including technical specifications, capabilities provided, and reason why the capability is provided via a third-party product rather than being incorporated into the Contractor’s PMT software

The Offeror shall, in their technical response, reference and provide a response for each sub-task

(including all sub-sections and bullet points) in Task 1.

4.2 Task 2: Software Integration and Automation Services

The Offeror shall provide integration services to automate the exchange of information between the BDC System and the Offeror’s proposed PMT. Specifically, the integration shall:

For Official Use Only (FOUO) 13

• Automate the process for ingesting data from the BDC System via an Application

Programming Interface (API);

• Analyze and validate that data using propagation modeling, including incorporation of required GeoData sources, to assess specific fixed and mobile wireless broadband network coverage;

• Automate the production of propagation modeling outputs in formats specified by the

FCC; and

• Automate the transmission of model outputs back to the BDC System via an API.

Additional integration requirements are further specified below.

4.2.1 Integration Overview

The information below is provided as specific requirements regarding the required exchange of data and information between the BDC System and the Contractor’s PMT software to be automated via the integration services. The Offeror may provide any modifications of the technical approach to the integration based on industry best practices and its own knowledge, experience, and subject matter expertise in the effective execution of similar projects. The government will work with the selected Contractor post-award to collaboratively review the

Contractor’s proposed technical approach modifications, if any, and confirm the final solution design details prior to implementation.

Deployment and Configuration

1. PMT is deployed, configured, and pre-loaded with required data such as terrain, clutter and vector geodata and antenna pattern data.

2. Load default configuration parameters for technology (e.g., LTE and 5G-NR), propagation model, and coverage study parameters.

API Call from BDC to the PMT to initiate Propagation Studies

1. BDC initiates PMT service by calling REST API including the following types of data:

network data (e.g., CSV), configuration data (e.g., CSV), antenna data (e.g., CSV), public and anonymized challenge and crowdsourced data (e.g., JSON).

2. Network data: See BDC infrastructure data specification including frequencies, bandwidth, and carrier aggregation.

https://us-fcc.app.box.com/v/bdc-infrastructure-spec

3. Configuration data: See BDC availability data specification including wireless technology, antenna technology including beamforming and massive MIMO, link https://us-fcc.app.box.com/v/bdc-infrastructure-spec

For Official Use Only (FOUO) 14 budgets, propagation model (including configuration), single point study, area study

(study boundary, study resolution), study parameters.

https://us-fcc.app.box.com/v/bdc-availability-spec

- Section 9.2 Mobile Link Budget Parameters

- Section 7.6 Fixed Wireless Link Budget Parameters

4. Antenna data: Specific antenna model if available in PMT database or antenna patterns file.

5. Crowdsourced data: Public and anonymized challenge and crowdsourced data to be loaded for model verification and optimization. See BDC mobile speed test data specification for format of crowdsourced data.

https://us-fcc.app.box.com/v/bdc-mobile-speedtest-spec

6. Run audits on the network data, geodata and public and anonymized challenge and crowdsourced data to ensure data quality and integrity.

API Call from the PMT to BDC to Return Propagation Study Results

1. PMT calls BDC System REST API to return the study results at a single location (JSON) with, at a minimum, the following data: best server and specific cell DL RSSI, DL RSRP, DL RSRQ, DL SINR, DL throughput, UL PUSCH signal level, UL PUSCH SINR, UL transmission power, UL throughput.

2. PMT calls BDC System REST API to return the study results for the study area (GIS coverage study data in raster format) with, at a minimum, the following data: best server and specific cell DL RSSI, DL RSRP, DL RSRQ, DL SINR, DL throughput, UL PUSCH signal level, UL PUSCH SINR, UL transmission power, UL throughput.

3. PMT calls BDC System REST API to return the converted study results from raster data to vector polygons for the study area (GIS coverage study data in vector format) with the coverage footprint for specified minimum DL and UL throughputs.

Testing

1. Design and implement sample test cases in collaboration with FCC.

2. Verify the propagation study results including configuration parameters, study parameters, and geographic data utilization.

a. Verify infrastructure parameters are accurately passed from BDC system to PMT and back

b. Verify that model configuration data is accurately passed to PMT and implemented in the specified propagation model https://us-fcc.app.box.com/v/bdc-availability-spec

For Official Use Only (FOUO) 15

c. Verify that model results are passed back to the BDC system in the format requested

3. Execute security testing to ensure compliance with all FCC and broader Federal IT security requirements.

4.2.2 Integration Timeframe

The Contractor shall complete the integration of the proposed PMT with the BDC System within eight (8) weeks of the contract kickoff meeting. The Offeror’s technical approach to the integration shall include a project management plan, staffing approach and milestone schedule to ensure project completion within this timeframe. The Offeror’s proposed project plan shall build in time for government review and approval of the system integration design prior to implementation and government testing of the completed integration within the eight-week timeframe. Sample timeframes are offered below, however the Offeror should propose the timing and schedule that best fits the requirements of the PWS. The government will work with the selected Contractor post award to review the approach submitted by the Offeror and finalize any mutually agreed upon changes prior to initiation of Task 2.

Sample Milestones

• Week 0 (week between award and kickoff) - Contractor ramp up and finalization of project plan, staffing plan, quality plan and communications plan submitted in Offeror’s proposal

• Week 1 – Develop integration design and submit to FCC for review within 1 week of kickoff

• Week 2 - Work with FCC to finalize/approve integration approach and design by or before end of week 2

• Weeks 3-6 - Execute approved integration design/approach within 4 weeks

• Weeks 7-8 - Conduct security and user testing and modify as needed

• Final product integrated and tested within 8 weeks

The Offeror’s response to Task 2 shall include, at a minimum, the following elements:

• Technical approach to completing the integration of the Contractor’s PMT with the

Government’s BDC System using APIs such that the platform will be able to retrieve information from, and send results to, the BDC System;

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

For Official Use Only (FOUO) 16

• Staffing Plan documenting personnel to be utilized on the effort and their qualifications.

If sub-contracting some or all of this work, please provide the name and address(es) of all subcontractor(s) (if applicable) and a description of their planned subcontracting effort

• Quality Assurance Plan documenting the approach to be used to ensure high-quality and on-time delivery of the end product;

• Communications Plan including approach to engaging with FCC technical personnel and end users to understand requirements and confirm any required customization of the software, interfaces, or other design elements to meet FCC needs; and

• Approach to training and documentation development, including any technical reference documents or other end-user support resources to be developed or provided as part of the integration services.

The Offeror shall submit drafts of the Project Management Plan, Staffing Plan, Quality

Assurance Plan and Communications Plan with their proposal. The government will work with the selected Contractor in the week following award to review, update and finalize these draft plans.

4.3 Task 3: Provision of Geographic Data Inputs for the PMT (“GeoData”)

The government requires certain Base Geographic Data sources (Base Geodata) to be incorporated into the initial deployment of the PMT software to support and enable the analyses and required outputs described in Task 1. In addition, the government anticipates a potential need to acquire additional GeoData sources (Optional Additional GeoData) via the selected Contractor or other approved FCC sources to support future analytical requirements as they are identified.

The Contractor shall provide as part of its Technical Approach a “Data Plan” outlining its approach for providing the required Base GeoData and, upon government request, acquiring the relevant Optional Additional GeoData, as further defined below:

1. Base GeoData Included in the Proposed PMT – All data sets that the Offeror has included in the proposed cost for the initial Base Implementation of the PMT in order to achieve the capabilities and outputs described in Task 1 (see Section 4.3.1 for additional information).

2. Optional Additional Geodata – Additional relevant data that is not included in the proposed configuration and cost of the initial Base Implementation of the PMT, but that may be acquired separately from the Offeror in the future to support specific analyses as they are identified (e.g., to support verification analyses for specific coverage challenges or locations) (see Section 4.3.2 for additional information)

Each of these areas is further described below.

For Official Use Only (FOUO) 17

4.3.1 Required Base GeoData Included in the Proposed PMT

The Offeror shall provide, as part of its technical response, a table specifying all GeoData sets that are included in the proposed Base Implementation of the PMT to meet the requirements outlined in Task 1. Table 1 below provides a sample format for this table, as well as minimum requirements for 12 specific required data sets. However, the Offeror should propose its full list of Base GeoData customarily offered with its PMT, including any additional data sources not specified in Table 1, by adding rows to the table as needed.

The provision and integration of the data sources specified in this table shall be included in the Offeror’s proposed technical approach and pricing for the initial implementation of the

PMT.

Table 1: Requested Information for Required GeoData for Base Implementation

Data

Type Geography Year Resolution

Accuracy (Vertical

RMSE)

Source(1) Provisioning(2)

Update

Frequency(3)

Terrain

CONUS 2021 10 meters 1 meter 2 Hawaii 2021 10 meters 1 meter 3 Alaska 2021 60 meters 1 meter 4 U.S. Territories 2021 10 meters 1 meter

Clutter

CONUS 2021 30 meters NA 6 Hawaii 2021 30 meters NA 7 Alaska 2021 60 meters NA 8 U.S. Territories 2021 30 meters NA

Clutter

Height

CONUS 2021 30 meters 2 meters 10 Hawaii 2021 30 meters 2 meters 11 Alaska 2021 60 meters 2 meters 12 U.S. Territories 2021 30 meters 2 meters

Other(4)

Etc

(1) Provide the name of the company/entity providing the source data

(2) Provide your approach to provisioning the data such as term license, subscription, one-time purchase, etc.

(3) Provide the recommended frequency for updates in order to keep the data current

(4) Specify any additional datasets customarily included in the cost of your base PMT software solution (e.g., additional resolution/accuracy options for listed required data or additional data types such as building data, street data, etc.)

For Official Use Only (FOUO) 18

The Offeror shall list each included GeoData source as a separate item (row) in the table and provide the relevant information noted in Table 1 for each source. The Offeror shall also note any restrictions or limitations on the use of each data source, if applicable.

4.3.2 Optional Additional GeoData

Over the proposed five-year period of performance, the government anticipates additional data sources may be required to support specific analyses, new data sources may become available that may enhance the initial propagation modeling tool, and/or initial Base GeoData sources may require updates to remain current. In order to support such additional data needs, the

Contractor’s “Data Plan” shall document its proposed approach to gaining access to, and providing FCC with, additional data sources and data source updates as required.

The Optional Special Projects CLIN will be used to acquire future Additional GeoData needs, if and when they are identified. If exercised, the Optional Additional GeoData CLIN will allow the government to acquire these additional GeoData sources from the Contractor at an additional cost. While the government may choose, at its discretion, to acquire such additional GeoData through an alternative contract, the Offeror shall document its capability to provide additional

GeoData and its approach/process for acquiring and providing future GeoData as part of the

“Data Plan” in its technical response.

Using the general format shown in Table 2 below, the Offeror shall provide a second separate table providing a complete listing of currently available and relevant additional GeoData sources compatible with the Offeror’s PMT software that are not included in the Base Implementation of the solution.

Table 2: Requested Information for Optional Additional GeoData

Data Type Geography

Other Parameters

(Add Columns as Needed) Source Provisioning Updates

1 Examples:

Terrain, Clutter, Clutter Height, Building, Street, etc.

Examples:

CONUS,

Hawaii, Alaska, U.S.

Territories

Other relevant parameters:

• Year (e.g., 2021)

• Resolution (horizontal)

• Accuracy (vertical RMSE)

• Other relevant specifications

Company or entity providing the source data

Examples:

Term license, Subscription, One-time purchase, etc.

Recommended frequency for data updates in order to remain current

4.4 Task 4 (OPTIONAL): Special Projects

At the government’s discretion during any performance period, but only upon the Contracting

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

For Official Use Only (FOUO) 19

Special Projects to provide additional software, integration services and/or GeoData to implement future software or system design modifications. This optional work may be directed on a labor-hour basis, within the ceiling established under this order, or may be performed on a

Firm Fixed Price basis agreed upon in a bilateral modification.

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 involving modifications or other tasks relating to the software, integration services, and GeoData provided under Tasks 1-3, and other related requirements, as may be necessary.

Optional Task Exercise Procedure

Work under Optional Task 4 may be exercised by the Government, in its sole discretion, as often as it requires and as funding allows. When an optional task is exercised, 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. If, in the estimation of either party, the work plan provides the Contractor with information that is sufficient to accurately estimate the extent and duration of work and to anticipate costs with confidence, either party may propose to use Firm Fixed Price for the work.

A fixed price for the work shall require mutual agreement of the parties represented in a bilateral modification to this task order. The optional tasks do not represent a commitment by the FCC to exercise the line item, nor, when exercised, does it represent a commitment of the FCC to direct work up to the ceiling amount established under a specific work plan, nor direct labor-hour work or negotiate Firm Fixed Price amounts up to the activity ceiling amount, or up to the amount used for estimates in pricing the activity in the Contractor’s proposal, or up to the activity ceiling amount for the option period in which the work occurs, or up to the ceiling amount for the activity aggregated for all optional periods.

For Official Use Only (FOUO) 20

5 DELIVERABLES

The Contractor shall provide the deliverables outlined in the schedules below.

Deliverables Schedule

Deliverable Description Schedule

Project Planning

Documents

The Contractor shall produce a Project Plan containing:

a) Project Management Plan

b) Staffing Plan

c) Quality Assurance Plan

d) Communication Plan

Draft submitted with

Proposal Response

Updated and validated with government COR within 5 business days of award.

Incident Response

Plan & Breach

Response Plan

The Contractor shall provide an Incident Response Plan and Breach Response Plan as outlined in Section 10 of the PWS.

Within 5 business days of award

Kick-off Meeting

The Contractor shall coordinate a kick-off meeting to review the Project Plan. The meeting shall include stakeholders, subject matter experts (SMEs) and the

FCC Project Manager in order to ensure common understanding of requirements and to set expectations.

Scheduled within 5 business days of award.

Weekly Meeting &

Status Report

The Contractor shall provide a weekly status report outlining progress over the past week and planned activities for the following week. The report shall document any issues encountered or anticipated along with proposed mitigations. The Contractor shall support a weekly status meeting with the FCC Project Manager to review status, scheduled sprints, risks, recommendations/changes to project owner priorities, and review of interim and final deliverables.

Weekly During Task 2

PoP

As Requested for optional tasks

Fully Integrated &

Configured

Propagation

Modeling Tool

The Contractor shall deliver the proposed PMT, including full integration with the FCC Broadband Data

Collection (BDC) system, initial customization of the solution and interfaces to FCC requirements (if required), provision and loading of initial required

GeoData sources, full system testing (including security and end-user testing), and development or provision of system documentation and end-user reference materials.

Within eight (8) weeks of the Kickoff Meeting

Refer to Section 4.2.2 for additional schedule information

For Official Use Only (FOUO) 21

6 GOVERNMENT-FURNISHED PROPERTY, MATERIAL, EQUIPMENT, OR

INFORMATION

The Contractor will be granted access to FCC’s commercial wireless propagation modeling and planning tool software licenses (as described in Task 1 of this PWS) while conducting the integration/automation services.

As noted in Task 3, the government may, at its discretion, acquire GeoData and other data sets from third-party sources for incorporation into the Offeror’s propagation modeling tool. If applicable, such data will be provided to the Contractor as Government Furnished Information

(GFI).

7 PLACE OF PERFORMANCE

The services specified in this performance work statement shall be performed primarily at the contractor facility (or facilities). However, work may be required periodically at FCC

Headquarters, 45 L Street, NE, Washington, DC 20554 or other FCC facilities at the direction of the COR. In the event that work is required onsite at government facilities and would require the

Contractor to incur travel costs, the government will work with the Contractor regarding the process for reimbursing approved travel expenses. No travel costs shall be reimbursed without prior approval in writing by the COR.

8 PERIOD OF PERFORMANCE

The base period of performance for this contract shall be twelve (12) months starting at the date of award, with four twelve (12) month option periods, to be exercised at the discretion of the

FCC.

9 LABOR CATEGORIES

The Offeror shall use its experience performing similar integrations in conjunction with the requirements outlined in the solicitation to propose the labor categories and hours required to complete the integration of the proposed PMT with the BDC System. The Offeror shall define each labor category in its technical approach and staffing plan, in terms of the level of experience, general capabilities and roles and responsibilities on the project.

10 SECURITY & PRIVACY

The Offeror’ solution, including all products and services provided, shall comply with all FCC

Information Technology (IT) policy requirements, NIST standards, OMB guidelines, and other applicable Government-wide laws and regulations. The following requirements include, but are not limited to:

For Official Use Only (FOUO) 22

• Federal Information Security Modernization Act of 2014 (FISMA), as amended

• Privacy Act of 1974, (5 U.S.C. § 552a)

• E-Government Act of 2002, Section 208

• Title V - Confidential Information Protection and Statistical Efficiency Act of 2002 of the

E-Government Act of 2002 (CIPSEA)

• Executive Order 14028, “Improving the Nation’s Cybersecurity”

• Executive Order 13556, “Controlled Unclassified Information (CUI)”

• Clinger-Cohen Act of 1996 also known as the “Information Technology Management

Reform Act of 1996”

• Office of Management and Budget (OMB) Circular A-130, “Managing Strategic

Information as a Resource”

• OMB M-22-09, “Moving the U.S. Government Toward Zero Trust Cybersecurity

Principles”

• OMB M-21-31, “Improving the Federal Government’s Investigative and Remediation

Capabilities Related to Cybersecurity Incident”

• OMB M-21-07, “Completing the Transition to Internet Protocol Version 9 (IPv6)”

• NIST Special Publication (SP) 800-18 (as amended), “Guide for Developing Security

Plans for Federal Information Systems”

• NIST SP 800-30 (as amended), “Guide for Conducting Risk Assessments”

• NIST SP 800-34 (as amended), “Contingency Planning Guide for Federal Information

Systems”

• NIST SP 800-37 (as amended), “Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy”

• NIST SP 800-47, “Security Guide for Interconnecting Information Technology Systems”

• NIST SP 800-53 (as amended), “Security and Privacy Controls for Federal Information

Systems and Organizations”

• NIST SP 800-53A (as amended), “Assessing Security and Privacy Controls in Federal

Information Systems and Organizations: Building Effective Assessments Plans”

• NIST SP 800-60 vol 1 (as amended), “Guide for Mapping Types of Information and

Information Systems to Security Categories”

• NIST SP 800-60 vol 2 (as amended), “Guide for Mapping Types of Information and

Information Systems to Security Categories: Appendices”

• NIST SP 800-61 (as amended), “Computer Security Incident Handling Guide”

• NIST SP 800-63-3, “Digital Identity Guidelines”

For Official Use Only (FOUO) 23

• NIST SP 800-171 (as amended), “Protecting Controlled Unclassified Information in

Nonfederal Systems and Organizations”

• NIST SP 800-177 (as amended), “Trustworthy Email”

• FIPS PUB 140-3, “Security Requirements for Cryptographic Modules”

• FIPS PUB 199, “Standards for Security Categorization of Federal Information and

Information Systems”

• FIPS PUB 200, “Minimum Security Requirements for Federal Information and

Information Systems”

• FCC Cybersecurity and Privacy Policy

• Any other relevant Federal laws, regulations, policies, and guidance that FCC must adhere to

10.1 Cybersecurity Training

The selected Contractor shall provide evidence that all personnel assigned to work on this contract have completed cybersecurity training. The cybersecurity training may be company-provided or provided by FCC. FCC policy requires cybersecurity training to occur on an annual basis.

10.2 Incident2 Response

The selected…