Format of Data
All data should be submitted in a .csv (comma-delimited) format.  The sheets in the workbook provide a template for how the tables should be designed.
The required format for the entries in each column/field is indicated in the instructions for each sheet.  
All entries in Text fields must be in quotation marks (e.g. "Verizon").
Column entries in bold red indicate that the party should enter only one of the possible entries listed for that column.  No other entries should be entered.
Data for all of the tables should be submitted for multiple quarters as of the second week of the month for the following months:
"Site Data" Table
The following data descriptions apply to the columns of the "Site Data" table.  The "Site Data" table should contain one row for every site utilized by
Verizon.  The site IDs in this table should correspond to the site IDs entered in the other requested tables.   
Column A: Date
Description: Submit annual snapshots for December 31, 2011 and December 31, 2012
Format of Field: Text - YYYY_12_31
Possible Entries: 2011_12_31
2012_12_31
Column B: Site ID
Description: A unique site ID for the site to which this data record applies.
Format of Field: Text
Example Entries: "AL0001", "VA0128", etc.
Column C: Number of Sectors
Description: This field provides an integer representing the number of sectors this site utilizes.
Format of Field: Number - Integer
Example Entries: 1, 2, 3, etc.
Column D: Latitude
Description: This field is the latitude of the site in decimal form to at least six significant digits.
Format of Field: Number - At least 6 decimal places
Example Entries: 37.705278, 34.299167, etc.
Column E: Longitude
Description: This field is the longitude of the site in decimal form to at least six significant digits.
Format of Field: Number - At least 6 decimal places
Example Entries: -77.424444, -102.860556, etc.
Column F: County FIPS
Description: This field is the five-digit FIPS code - based on 2010 designations - of the county in which the site is located.
Format of Field: Text
Example Entries: "01001", "51059", etc.
Column G: CMA
Description: This field represents the standard market number of the CMA in which the site is located.
Format of Field: Number - Integer
Possible Entries: Integers 1 - 722, excluding 91, 147, 169, 202, 204, and 306
Page 2 Site Data Instructions
"Site Data" Table
Column H: Site Type
Description: This field indicates the type of site to which the record applies using one of the possible entries listed below.
Format of Field: Text
Possible Entries: "Macro_Tower" An outdoor macrocell mounted on a monopole, guyed tower, or free standing tower
"Macro_Building" An outdoor macrocell mounted on a building
"Macro_Other" An outdoor macrocell that does not fit the previous categories (silo, water tower, etc.)
"Microcell" An outdoor cell classified by the vendor as a microcell
"Outdoor Pico" An outdoor cell classified by the vendor as a picocell
"Indoor Pico" An indoor cell classified by the vendor as a picocell
"Outdoor DAS" An outdoor Distributed Antenna System
"Indoor DAS" An indoor Distributed Antenna System
"Repeater" A cell that repeats/boosts the signal of another cell
"Other" A cell that does not meet any of the above descriptions
Column I:
Site Geographic 
Classification
Description: This field indicates the morphology of the area that the site serves using one of the possible entries listed below.
Please provide a description of the methodology used to determine these classifications in a separate attachment.
Format of Field: Text
Possible Entries: "Urban"
"Suburban"
"Rural"
Column J:
Antenna Height - 
(Feet - AGL)
Description: This field indicates the antenna height above ground level in feet.
Format of Field: Number
Possible Entries: 100
Column K:
Site Height (Feet - 
ASL)
Description: This field indicates the antenna height above sea level in feet.
Format of Field: Number
Possible Entries: 467
Column L:
Backup Power 
Capacity (Hours)
Description: This field indicates the number of hours of available site backup power.
Page 3 Site Data Instructions
"Site Data" Table
Format of Field: Number
Possible Entries: 4
Page 4 Site Data Instructions
Date Site ID
Number of 
Sectors Latitude Longitude County FIPS CMA Site Type
Site 
Geographic 
Classification
Antenna Height 
- (Feet - AGL)
Site Height 
(Feet - ASL)
Backup Power 
Capacity (Hours)
Site Data Template Page 5
"Traffic" Table
The following data descriptions apply to the columns of the "Traffic" table.  In general, this table is intended to provide data on the average busy
hour voice and data traffic at each Verizon site/sector, by technology group and by spectrum band. All busy hour data shall be the
average bouncing busy hour (BBH) over the 5-day business week period (Mon-Fri) in the second week of the month. 
The BBH is the one-hour period during the day in which the highest usage is measured,
starting on the hour or half hour, and the highest usage hour may vary from day to day.
In the column headings, "1X" indicates traffic carried by on a 1X network and "DO" indicates traffic carried on a 
EVDO network.
Column A: Date
Description: The month for which the data is being collected as of the second week of the month, except as specified for Columns 
F, I, N, and S below.  
For months subsequent to the date of this request, use projected data (except no projected data needed for Columns F, I, N, and S).
Provide two sets of projected data: (1) assuming that Verizon's discontinuance request is granted; and (2) assuming that
the request is not granted.
For columns F, I, N, and S ("Minutes = Utilization Threshold"), report cumulative minutes for the entire reporting month. 
Format of Field: Text - YYYY_MM
Possible Entries: 2011_05 2012_01 2013_01 2014_01
2011_06 2012_02 2013_02 2014_02
2011_07 2012_03 2013_03 2014_03
2011_08 2012_04 2013_04 2014_04
2011_09 2012_05 2013_05 2014_05
2011_10 2012_06 2013_06 2014_06
2011_10 2012_07 2013_07 2014_07
2011_11 2012_08 2013_08 2014_08
2011_12 2012_09 2013_09
2012_10 2013_10
2012_11 2013_11
2012_12 2013_12
Column B: Site ID
Description: A unique site ID for the site to which this data record applies.
Format of Field: Text
Example Entries: "AL0001", "VA0128", etc.
Column C: Sector ID
Description: A unique sector ID for the sector to which this data record applies, created by adding a suffix to the site ID.
Format of Field: Text
Example Entries: Suffix examples include "A","B","C" or "1","2","3"
Cellular Band - 1X
Page 6 Traffic Instructions
"Traffic" Table
Column D:
Cell_1X_Avg BBH 
Voice Traffic_Erlangs
Description: BBH voice traffic in Erlangs carried by 1X carriers in the Cellular band
Format of Field: Number
Column E: Cell_1X_Avg BBH 
Voice Traffic 
Blocking%
Description: Percent of BBH voice traffic channel blocking or congestion
Format of Field: Decimal
Column F: Cell_1X              
Minutes = Utilization 
Threshold
Description: Cumulative time in minutes that 1X carriers in the Cellular band reach 100% utilization threshold for the reporting month
Format of Field: Number
PCS Band - 1X
Column G:
PCS_1X_Avg BBH 
Voice Traffic_Erlangs
Description: BBH voice traffic in Erlangs carried by 1X carriers in the PCS band
Format of Field: Number
Column H: PCS_1X_Avg BBH 
Voice Traffic 
Blocking%
Description: Percent of BBH voice traffic channel blocking or congestion
Format of Field: Decimal
Column I: PCS_1X              
Minutes = Utilization 
Threshold
Description: Cumulative time in minutes that 1X carriers in the PCS band reach 100% utilization threshold for the reporting month
Format of Field: Number
AWS Band - LTE
Column J:
AWS_LTE_Avg BBH 
Voice Traffic_Erlangs
Description: BBH voice traffic in Erlangs carried by LTE carriers in the AWS band
Format of Field: Number
Page 7 Traffic Instructions
"Traffic" Table
Column K: AWS_LTE_Avg BBH 
Voice Traffic 
Blocking%
Description: Percent of BBH voice traffic channel blocking or congestion
Format of Field: Decimal
Column L: AWS_LTE_Avg BBH 
Data Traffic 
Downlink_MB
Description: BBH base to mobile data traffic in MB carried by LTE carriers in the AWS band
Format of Field: Number
Column M: AWS_LTE_Avg BBH 
Data Traffic 
Uplink_MB
Description: BBH mobile to base data traffic in MB carried by LTE carriers in the AWS band
Format of Field: Number
Column N: AWS_LTE              
Minutes = Utilization 
Threshold
Description: Cumulative time in minutes that LTE carriers in the AWS band reach 100% utilization threshold for the reporting month
Format of Field: Number
700MHz - LTE
Column O:
700_LTE_Avg BBH 
Voice Traffic_Erlangs
Description: BBH voice traffic in Erlangs carried by LTE carriers in the 700MHz band
Format of Field: Number
Column P: 700_LTE_Avg BBH 
Voice Traffic 
Blocking%
Description: Percent of BBH voice traffic channel blocking or congestion
Format of Field: Decimal
Column Q: 700_LTE_Avg BBH 
Data Traffic 
Downlink_MB
Description: BBH base to mobile data traffic in MB carried by LTE carriers in the 700MHz band
Format of Field: Number
Page 8 Traffic Instructions
"Traffic" Table
Column R: 700_LTE_Avg BBH 
Data Traffic 
Uplink_MB
Description: BBH mobile to base data traffic in MB carried by LTE carriers in the 700MHz band
Format of Field: Number
Column S: 700_LTE              
Minutes = Utilization 
Threshold
Description: Cumulative time in minutes that LTE carriers in the 700MHz band reach 100% utilization threshold for the reporting month
Format of Field: Number
Page 9 Traffic Instructions
Site ID
Sector 
ID
Cell_1X_Avg 
BBH Voice 
Traffic_Erlangs
Cell_1X_Avg 
BBH Voice 
Traffic 
Blocking%
Cell_1X  
Minutes = or > 
Utilization 
Threshold
PCS_1X_Avg 
BBH Voice 
Traffic_Erlangs
PCS_1X_Avg 
BBH Voice 
Traffic 
Blocking%
PCS_1X  
Minutes = 
Utilization 
Threshold
AWS_LTE_Avg 
BBH Voice 
Traffic_Erlangs
AWS_LTE_Avg 
BBH Voice 
Traffic 
Blocking%
AWS_LTE_Avg 
BBH Data 
Traffic 
Downlink_MB
AWS_LTE_Avg 
BBH Data 
Traffic 
Uplink_MB
AWS_LTE 
Minutes = 
Utilization 
Threshold
700_LTE_Avg 
BBH Voice 
Traffic_Erlangs
700_LTE_Avg 
BBH Voice 
Traffic 
Blocking%
700_LTE_Avg 
BBH Data 
Traffic 
Downlink_MB
Traffic Template