How to Format Bulk Fixed Challenge and Crowdsource Data

Updated April 26, 2023 13:18

Choose a Methodology

To submit bulk fixed availability challenge or crowdsourced data, all entities must first complete a web form indicating the methodology used to collect the data. The format of the data file to upload varies slightly depending on the methodology. The three methodology options are:

Knowledge of Infrastructure
Information Collected from Individual Consumers
Other

For more information about these methodologies, please see the "Overview of Bulk Fixed Availability Challenges” and “Overview of Bulk Fixed Availability Crowdsource Data” articles.

Format the Data File for Upload

You must create a separate file for each provider that is the subject of the challenge or crowdsource data.

The table below lists the data you must include when submitting Bulk Fixed Availability Challenge or Crowdsource data. Note that the first three fields should only be included if using Methodologies 2 (Information Collected from Individual Consumers) or 3 (Other).

A few additional things to note about the data file:

It must be submitted in Comma Separated Value (CSV) format.
It must include the header row.
It must contain records for each location about which challenge/crowdsource information is being submitted, and the location must be identified using the Location ID shown on the National Broadband Map and used in the Broadband Service Location Fabric.
Use the vintage of the Fabric associated with the fixed availability data about which challenge/crowdsource information is being submitted (i.e., if submitting challenge/crowdsource information about the fixed availability data as of June 30, 2022, filers must use the location_ids associated with that version of the Fabric used and availability data as of that date).
To submit challenge/crowdsource data about a particular location for more than one reason, enter an additional record for that location_id and enter the additional category_code associated with that location.

Field	Data Type	Example	Description/Notes
contact_name	String	Jane Broadband	Full name of the individual contact associated with the challenge at the location *- Omit field if using Methodology 1*
contact_email	String	Jane.broadband@fcc.gov	Email address of the individual contact associated with the challenge at the location. - Value must match valid email address format, e.g.: atom@domain.tld. *- Omit field if using Methodology 1*
contact_phone	String	888-225-5322	Phone number of the individual contact associated with the challenge at the location. - Value is optional and may be null. - Value must match valid US phone number format: 000-000-0000, if not null. *- Omit field if using Methodology 1*
provider_id	Integer	900104	Unique identifier for the fixed service provider about which challenge or crowdsource data is being submitted.
brand_name	String	Acme Broadband	Brand name of the service, as shown on the Broadband Map, about which challenge or crowdsource data is being submitted.
technology	Integer	50	Code for the technology of the fixed broadband service, as shown on the Broadband Map, about which challenge or crowdsource data is being submitted. - Value must be one of the following codes: 10 – Copper Wire 40 – Coaxial Cable / HFC 50 – Optical Carrier / Fiber to the Premises 60 – Geostationary Satellite 61 – Non-geostationary Satellite 70 – Unlicensed Terrestrial Fixed Wireless 71 – Licensed Terrestrial Fixed Wireless 72 - Licensed-by-Rule Terrestrial Fixed Wireless 0 – Other
location_id	String	1357135307	Unique identifier for the location, from the Broadband Serviceable Location Fabric, subject to the fixed broadband availability challenge or crowdsource data.
data_vintage	Date	2022-06-30	Vintage date of fixed broadband availability data about which challenge or crowdsource data is being submitted. - Value must match valid ISO-8601 date format, e.g.: YYYY-MM-DD - Value must correspond to the as-of date of published fixed broadband availability data.
category_code	Enumerated	5	Code identifying the category or reason for the fixed availability challenge or crowdsource data being submitted for that location. - Value must be one of the following codes: 1 – Provider failed to schedule a service installation within 10 business days of a request. 2 –Provider did not install the service at the agreed-upon time. 3 – Provider requested more than the standard installation fee to connect this location. 4 – Provider denied the request for service. 5 – Provider does not offer the technology entered above at this location. 6 – Provider does not offer the speed(s) shown on the Broadband Map for purchase at this location. 7 – The actual speed of the service does not match its advertised speed (Bulk Crowdsource only). 8 – No wireless or satellite signal is available at this location. 9 – New, non-standard equipment is required to connect this location. - Value may not be 8 or 9 unless technology value is 60, 61, 70, or 71. *- Value 7 may only be entered for bulk fixed availability crowdsource data and cannot be used in a challenge.*
request_date	Date	2022-09-01	As relevant, enter the most recent date associated with the category_code above, such as the date a service request was denied or the date the filer became aware of the circumstances. - Value is required if category_code value is 1, 2, 3, 4, 8, or 9. - Value must be null if category_code value is 5 or 6.
request_method_code	Enumerated	1	As relevant, enter the communication method associated with the category_code and request_date above, such as how a service request was denied or how the filer became aware of the circumstances. - Value must be one of the following codes: 1 – Email 2 – Phone 3 – Website 0 – Other - Value is required if category_code value is 1, 2, 3, 4, 8, or 9. - Value must be null if category_code value is 5 or 6.
evidence_description	String		Narrative description of the evidence in support of the challenge. *- Value may be null if using Methodology 1 for a challenge.* *- Value may be null if submitting bulk fixed crowdsource data.*

For more information about formatting the data file for upload, see the Specifications for Bulk Fixed Availability Challenge and Crowdsource Data.

Include an Evidence File if Necessary

In addition to the required CSV file, filers submitting bulk fixed challenge data based on Methodology 1 (Knowledge of Infrastructure) must also upload a separate file that provides evidence to support the fixed availability challenge. At least one evidence file must be submitted for each bulk fixed challenge file. The accepted file formats for the evidence file are: DOC, DOCX, PDF, JPEG, PNG, JSON.

This evidence file is optional for fixed challenge submissions based on Methodologies 2 and 3, but challengers are encouraged to include evidence (such as emails and other correspondence, screenshots, or photos if relevant) that may help to support or corroborate the factual basis of their challenges.

The evidence file is optional for filers of bulk fixed availability crowdsource data, regardless of the methodology used to collect the data.

File Templates:

Methodology 1

Methodologies 2 and 3

Re-Filing a Bulk Challenge

If a bulk fixed availability challenger wishes to re-file a rejected submission with additional evidence, they will need to delete the rejected challenge in the system, read the disclaimer, accept the deletion, and then re-file the challenge with the additional evidence. Please note that deleting the submission means the information is permanently deleted and non-retrievable, so any information from the filing that is needed should be captured before deleting it.

Articles in this section