Comprehensive Market Data Collection for Interstate Special Access Services

On December 18, 2012, the Commission released an Order calling for the mandatory collection of data, information and documents from entities that provide and purchase special access services in price cap areas.⁰ Larger entities providing best efforts business broadband Internet access services are also required to respond to the data collection. With the data, the Commission will conduct a comprehensive analysis of special access markets to determine where relief from special access regulation is appropriate and otherwise update its rules to ensure that they reflect the state of competition today and promote competition. Italicized terms in these instructions are defined in Section I of the Mandatory Data Collection, which is available on the FCC’s website.⁰

Filing Requirements and General Instructions
1. Purpose of Data Collection

This collection will enable the Commission to obtain the data, information, and documents needed to conduct a comprehensive evaluation of competition in the special access market. In conjunction with the market analysis proposed by the Commission in the Further Notice, the data, information, and documents acquired through this collection will aid the Commission in “evaluating whether the pricing flexibility rules result in just and reasonable special access rates and what regulatory changes may be needed.”⁰

Authority for Data Collection

This collection of information stems from the Commission’s authority under sections 1, 4(i), 4(j), 5, 201-205, 211, 215, 218, 219, 303(r), 332, 403, and 503 of the Communications Act of 1934, as amended, 47 U.S.C. §§ 151, 154(i), 154(j), 155, 201, 202, 203, 204, 205, 211, 215, 218, 219, 303(r), 332, 403, 503, and section 706 of the Telecommunications Act of 1996, 47 U.S.C. § 1302.

Who Must Respond to this Data Collection?

All Providers and Purchasers of Dedicated Service in areas where the incumbent local exchange carrier (ILEC) is subject to price cap regulation (i.e., price cap areas)⁰ must respond to this data collection unless specifically excluded.⁰ By Providers, we mean any entity subject to the Commission’s jurisdiction under the Communications Act of 1934, as amended, that provides Dedicated Service in a price cap area or provides a Connection that is capable of providing a Dedicated Service in a price cap area. By Purchasers, we mean any entity subject to the Commission’s jurisdiction that purchases Dedicated Service in a price cap area. Entities that provide Best Efforts Business Broadband Internet Access Services in an area where the ILEC is subject to price cap regulation are also required to respond to this data collection unless they have fewer than 15,000 customers and fewer than 1,500 business broadband customers as of December 18, 2012.⁰

Covered Providers. Types of Providers that must respond if they provide a Dedicated Service or have Connections with the capability of providing a Dedicated Service could include, but are not limited to, incumbent local exchange carriers, competitive local exchange carriers, interexchange carriers, cable system operators, fixed wireless service providers (including wireless Internet service providers (WISPs)), terrestrial and satellite mobile wireless service providers, electric utilities, local government entities, certain providers of information services and third party network providers.

To help ensure that our analysis includes all Providers that have Connections capable of providing a Dedicated Service, any entity required to report broadband connections to end user locations on the FCC Form 477 (“Local Telephone Competition and Broadband Reporting”) for 2012 must respond to this collection, i.e., required to file the FCC Form 477 on March 1, 2013, to report connections as of December 31, 2012. If a FCC Form 477 filer does not (i) provide a Dedicated Service in a price cap area; (ii) provide a Connection capable of providing a Dedicated Service in a price cap area; or (iii) provide a Best Efforts Business Broadband Internet Access Service, then it will only need to certify as such when responding to this data collection.

For example, a carrier providing or purchasing a Dedicated Service in an interstate rate-of-return area and that reported broadband connections to end user locations in the Form 477 for Year 2012 would have to respond to this data collection only to indicate that it is not a Provider, Purchaser, or entity that provides Best Efforts Business Broadband Internet Access Services in a price cap area.

For guidance on determining whether you are a Provider with Connections “capable” of providing Dedicated Service, see the additional instructions provided for identifying reportable Locations with Connections in “Section III. Additional Instructions and Data Table Specifications,” Question II.A.3 (directed at Competitive Providers) and Question II.B.2 (directed at ILECs).

Covered Purchasers. Types of Purchasers that must respond if they buy a Dedicated Service in a price cap area include, but are not limited to, ILECs, competitive local exchange carriers, interexchange carriers (CLECs), cable system operators, wireless providers, satellite service providers, international service providers to and from points in the United States, interconnected and non-interconnected VoIP providers, and certain information service providers such as Internet access providers.

Responses are mandatory for covered Purchasers and Providers and covered entities providing Best Efforts Business Broadband Internet Access Service. Failure to respond to this collection may result in monetary penalties.⁰

Entities Specifically Excluded from the Data Collection. Entities falling into only one or more of the categories listed below are specifically excluded from the collection even if they purchase Dedicated Service in a price cap area. These exclusions do not apply, however, to entities that hold licenses, authorizations or registrations under any other Part of the Commission’s rules not listed below, or that provide a Dedicated Service or a Best Efforts Business Broadband Internet Access Service in a price cap area.⁰

End Users that provide an information service;
Equipment authorization holders regulated under Parts 2 and 15 of the Commission’s rules;
Accounting authorization holders in the maritime and maritime mobile-satellite radio services regulated under Part 3 of the Commission’s rules;
Experimental radio authorization holders regulated under Part 5 of the Commission’s rules;
Commercial radio operators regulated under Part 13 of the Commission’s rules;
Antenna structure registration holders regulated under Part 17 of the Commission’s rules;
Television and radio broadcasters regulated under Part 73 of the Commission’s rules;
Holders of authorizations issued pursuant to Part 74 of the Commission’s rules such as experimental radio, auxiliary, special broadcast and other program distribution service authorizations;
Maritime service authorization holders regulated under Part 80 of the Commission’s rules;
Aviation service authorization holders regulated under Part 87 of the Commission’s rules;
Private land mobile radio service authorization holders regulated under Part 90 of the Commission’s rules except for holders of authorizations under Part 90 for the provision of point-to-point fixed microwave services and authorizations in the Wireless Broadband Services frequency band, 3650-3700 MHz;
Personal radio service authorization holders regulated under Part 95 of the Commission’s rules; and
Amateur radio service authorization holders regulated under Part 97 of the Commission’s rules.

These exclusions only apply to the categorically excluded entity and do not extend to other entities within the same corporate structure or entities that are otherwise affiliated with the excluded entity. For example, if an entity holding a television broadcast authorization is affiliated with a cable company that provides Dedicated Service, the affiliated cable company must still respond to the data collection even though the television broadcasting entity is not required to respond. In addition, for clarity, we point out that these categorical exclusions do not include common carriers (wired or wireless), mobile wireless service providers, cable system operators even if they only provide video program services, international service providers, satellite service providers, or entities that hold FCC authorizations for the provision of fixed point-to-point microwave services.

Note that even if you fall within one of these specific exclusion categories but were required to report broadband connections to end users on the Form 477 for 2012, you are still required to respond to this data collection only to indicate that you are not a Provider, Purchaser, or entity that provides Best Efforts Business Broadband Internet Access Services in a price cap area.

Responding to the Data Collection

The Commission will create a secure Special Access Web Portal for the electronic submission of responses.⁰ Filers will login using an FCC Registration Number (FRN) and password and download a data container that will include record specifications for compiling data responses and software tools to verify that data is submitted in the appropriate format.⁰ Filers will subsequently login using its FRN and password and electronically submit responses to the data collection. The Wireline Competition Bureau (Bureau) will provide additional details on the electronic filing process in advance of the submission deadline.

Geographic Scope of Submitted Data and Information

With limited exceptions, we are requesting data on a nationwide basis for those geographic areas where the ILEC is subject to price cap regulation. However, for administrative ease, respondents can submit data that includes both price cap and non-price cap areas.

When to File

Once the collection is approved by the Office of Management and Budget (OMB) in accordance with the Paperwork Reduction Act of 1995, the Bureau will issue a public notice announcing when responses are due.

Certification of Filing Accuracy

Each submission must include a completed certification of filing accuracy. The certification must include the name and signature of a company official (e.g., corporate officer, managing partner, or sole proprietor) who certifies that he or she has examined the information contained in the data request submission and that, to the best of his/her knowledge, information, and belief, all statements of fact, data, and information contained in the submission are true and correct. Persons making false statements or misrepresentations to the Commission can be punished by fine or imprisonment under Title 18 of the U.S. Code. A sample certification is contained in the Mandatory Data Collection.⁰ Filers will electronically submit the certification when submitting the Filer Identification Information electronically filed with each submission, see “Section III: Additional Instructions and Data Table Specifications.”

Confidentiality

Respondents are required to submit data and information on revenues, prices, expenditures, subscribers, and facilities for the collection that is highly sensitive and not routinely made available to the public. In advance of the filing deadline, the Bureau will issue a Protective Order detailing the procedures for requesting confidentiality and accessing confidential and highly confidential data and information.⁰

Retention of Records

Respondents are required to retain, for a period of three years or until the Commission issues a notice relieving respondents of this requirement, any records, data, documents, documentation, or other information prepared, used, or relied upon by the respondents for their responses to this data collection.⁰

Paperwork Reduction Act Notices

This document contains information collection and recordkeeping requirements and will not become effective until approval has been given by the OMB. Covered parties are not required to respond to the information collection and recordkeeping requirements contained herein until a notice of approval has been published in the Federal Register.

The time needed to complete and file responses to the data collection will vary depending on individual circumstances. There is significant variation among Providers and Purchasers in the number of questions to be answered and the amount of responsive data and information they are required to furnish. We have estimated that each response to this collection of information will take an average of XX hours. This estimate is a national average and does not necessarily represent a “typical” case. Our estimate includes the time to read the instructions, look through existing records, gather and maintain required data, enter the data in the online interface, and submit it electronically. If you have any comments on this estimate, or on how we can improve the collection and reduce the burden it causes you, please write the Federal Communications Commission, Office of Managing Director, AMD-PERM, Washington, DC 20554, Paperwork Reduction Act Project (3060-XXXX). We will also accept your PRA comments via the Internet if you send an email to [email protected].

Please DO NOT SEND COMPLETED DATA COLLECTION RESPONSES TO THIS ADDRESS. You are not required to respond to a collection of information sponsored by the Federal government, and the government may not sponsor this collection, unless it displays a currently valid OMB control number and/or we fail to provide you with this notice. This collection has been assigned an OMB control number of 3060-XXXX.

THIS NOTICE IS REQUIRED BY THE PAPERWORK REDUCTION ACT OF 1995, PUBLIC LAW 104-13, OCTOBER 1, 1995, 44 U.S.C. SECTION 3507.

Additional Instructions and Data Table Specifications

To access the FCC website interface to submit responses to this data collection, each filer is required to provide an FRN that is unique to the filer and password, i.e., no two filers can submit responses using the same FRN.⁰ No filer can submit more than one response to the data collection questions; subsequent corrective filings are permitted however. When submitting a response, each filer must provide the information identified below and the requisite certification.⁰

Filer Identification Information
Name of Filer	[Text populated from CORES database]
Filer’s FCC Registration Number (FRN)	[Integer populated from CORES database]
Name of Contact for Filer	[Text]
Contact Phone Number	[Text]
Contact Address	[Text]
Contact Email Address	[Text]
Counsel of Record Name	[Text]
Counsel of Record Phone Number	[Text]
Counsel of Record Address	[Text]
Counsel of Record Email Address	[Text]
Holding Company FRN	[Integer]
Holding Company Name	[Text populated from CORES database]

Filer Identification Information cont.
Type of Filer (select all that apply)	□ Competitive Provider Type of Competitive Provider (select all that apply): □ Cable system operator □ CLEC □ IXC □ Wireless provider □ Other
	□ ILEC
Type of Filer cont. (select all that apply)	□ Entity that provides Best Efforts Business Broadband Internet Access Service to 15,000 or more customers or 1,500 or more business broadband customers in price cap areas
	□ Purchaser Type of Purchaser (select all that apply): □ Mobile wireless service provider □ Other
	□ None of the above (i.e., you are not a Provider, Purchaser, or an entity that provides Best Efforts Business Broadband Internet Access Service to 15,000 or more customers or 1,500 or more business broadband customers in price cap areas

Counsel of Record. If you are represented by counsel and want to designate such counsel for the service of notices and other documents, then complete the “Counsel of Record” fields in the Filer Identification Information.

Holding Company. Parties can either submit a single response reporting aggregate information at the ultimate parent/holding company level for all subsidiaries, affiliates, and intermediate holding companies or submit separate responses for individual subsidiaries, affiliates, and intermediate holding companies. In addition, list the name and FRN for all companies covered by the submission in the “Explanatory Attachment” and identify the companies whose information is being reported in response to a particular section of the data collection.⁰ For example, the responses to Section II.A include information from ABC CLEC Co. and DEF CLEC Co. and the responses to Section II.E include information from ABC Wireless Co.

If filing separate responses, identify the name and FRN of the filer’s ultimate parent/holding company or controlling entity. All reporting affiliates or commonly controlled entities must list the identical ultimate parent/holding company name or controlling entity and FRN so the FCC can internally link the responses to a single ultimate parent/holding company or controlling entity. In addition, the ultimate parent/holding company or controlling entity must separately file a letter in the Commission’s Electronic Comment Filing System (ECFS) in WC Docket No. 05-25 identifying its FRN and the FRN and name of all of its subsidiaries that are separately filing responses to this data collection; send a copy of this letter via email to [FCC contact].

Corrective Resubmissions. If you need to make a corrective resubmission, contact [FCC contact name] to make arrangements. Include with your corrective resubmission an explanation of the nature of the correction, i.e., explaining what information you are correcting and why.

Certification
I have examined the response and certify that, to the best of my knowledge, all statements of fact, data, and information contained therein are true and correct.
Signature
Name
Title
Date
Respondents are reminded that failure to comply with these data reporting requirements may subject them to monetary forfeitures of up to $160,000 for each violation or each day of a continuing violation, up to a maximum of $1,575,000 for any single act or failure to act that is a continuing violation. 47 U.S.C. § 503(b)(2); 47 C.F.R. § 1.80(b); Amendment of Section 1.80(B) of the Commission's Rules, Adjustment of Civil Monetary Penalties to Reflect Inflation, Order, DA 13-1615 (Enf. Bureau rel. Aug. 2, 2013). False statements or misrepresentations to the Commission may be punishable by fine or imprisonment under Title 18 of the U.S. Code.

The following is a chart showing the types of filers and the corresponding sections of data collection questions that must be completed by each filer type. Filers falling within multiple categories must respond to all applicable sections. For example, a Competitive Provider that purchases Dedicated Services must respond to the data collection questions directed at Competitive Providers and Purchasers.

Type of Filer	Sections of the Data Collection that Must be Completed
Competitive Provider	Sections II.A and II.D if answer to Questions II.A.2 or II.A.2.a is “yes”
ILEC	Sections II.B and II.D
Entity that provides Best Efforts Business Broadband Internet Access Service to 15,000 or more customers or 1,500 or more business broadband customers in price cap areas	Section II.C
Purchaser that is a mobile wireless service provider	Section II.E
Purchaser that is not a mobile wireless service provider	Section II.F
None of the above	Section II.G

EXPLANATORY ATTACHMENT

To the extent you need to explain certain assumptions or procedures taken in collecting and reporting the information requested in this data collection, especially for the responses to the facilities and billing information questions, include a separate document with your submission, in Word or .pdf format, containing all of your explanations.⁰ You must separately upload the Explanatory Attachment as a Word or .pdf document through the Special Access Web Portal; you will not include this document in the data container.

QUESTIONS DIRECTED AT COMPETITIVE PROVIDERS

Question II.A.1: Affiliated Company

If you are an Affiliated Company, then you must identify each entity you are affiliated with that provides and/or purchases Dedicated Service in Table II.A.1 within the data container. If you are not an Affiliated Company, then you must still type “Not Applicable” in the Affiliate_Name field and “0000000000” in the Name_FRN field. You will receive an error message upon validation of the data container if you do not put any information into Table II.A.1.

Table II.A.1 Record Format for Affiliated Company
Field Name	Description	Type	Example
Affiliate_ID	Sequential number	Integer	1
Affiliate_Name	Name of entity with which you are affiliated	Text	Local Fiber Incorporated
Name_FRN	Entity’s FCC Registration Number (with leading zeros)	Integer	0008402202

Question II.A.2: Facilities Requiring Additional Information

Table II.A.2 Record Format for Facilities Triggering Need for Additional Information
Field Name	Description	Type	Example
Connection	Do you own a Connection; lease a Connection under an IRU agreement; or obtain a Connection as a UNE to provide a Dedicated Service? (Y=Yes, N=No)	Text	Y
Price_Cap?	Are any of the Connections – that you own; lease as an IRU; or obtain as a UNE to provide a Dedicated Service – to a Location in a price cap area? (Y=Yes, N=No, NA=Not Applicable)	Text	Y

Facilities Information

Question II.A.3: Locations Data for Competitive Providers

Competitive Providers are required to report the total number of Locations to which they had a Connection during 2010 and during 2012 where the Competitive Provider either: (i) owned the Connection; (ii) leased the Connection from another entity under an IRU; or (iii) obtained the Connection as a UNE to provide a Dedicated Service. The definition of Connection is crafted to assist the Commission with sizing the broader market for Dedicated Services by including transmission facilities used to provide a Dedicated Service and facilities that are “capable” of providing a Dedicated Service.

To help Competitive Providers identify reportable Locations, we provide the following guidance:

Respondents must only report Connections to non-residential Locations. A Location is where an End User is connected, and an End User means a business, institutional, or government entity that purchases service for its own purposes, not for resale. Accordingly, residential locations connected by facilities are not reported.

Competitive Providers, except for cable system operators reporting Locations within their Franchise Areas (FAs), must report all Locations with idle and in-service Connections during the relevant reporting period regardless of the type of service provided over the Connection.

If you are a cable system operator and reporting Locations within your FA, you must report those Locations with Connections that were connected to a Node (i.e., headend) during the relevant reporting period that was upgraded or built to provide Metro Ethernet (or its equivalent) service regardless of the type of service provided over the Connection or whether the Connection is idle or in-service.⁰ In addition, for Locations with Connections that were not connected to a Node during the relevant reporting period that is capable of providing Metro Ethernet (or its equivalent), report only in-service Connections that were used to provide a Dedicated Service or a service that incorporates a Dedicated Service within the offering as part of a managed solution or bundle of services sold to the customer;⁰ do not report Connections that were used to provide a service that is substantially similar to services provided to residential customers, e.g., one or two line telephone service or best-efforts Internet access and subscription television services.⁰

For Locations with Connections obtained as a UNE to provide a Dedicated Service during 2010 and during 2012, all Competitive Providers must include those UNEs obtained to provide a service that incorporated a Dedicated Service within the offering as part of a managed solution or bundle of services sold to the customer.⁰

Table II.A.3 Record Format for Total Locations
Field Name	Description	Type	Example
Year	Indicator of the calendar year of the data	Integer	2010
Locations	Total Locations served during year	Integer	15

Instructions for Table II.A.3, Record Format for Total Locations (Competitive Providers):

Locations: The number of Locations is the count of unique Locations to which your company had a Connection in place during the year entered in Year. The number of Locations listed here must equal the number of unique Locations enumerated in Question II.A.4 for each year.

Question II.A.4: Locations Data for Competitive Providers

The purpose of this question is to obtain additional information on the individual Locations with Connections that make up the total reported in response to Question II.A.3.

Table II.A.4 Record Format for Each Location
Field Name	Description	Type	Example
Location_ID	Sequential Location number (same Location_ID will also be reported in the II.A.12 question related to billing).	Integer	1
Year	Indicator of the calendar year of the data	Integer	2010
Street_address	Actual situs for the Location (i.e., land were building or cell site is located)	Text	445 Twelfth St SW
City	City of the Location	Text	Washington
State	Two-letter state postal abbreviation of the Location	Text	DC
ZIP	5-digit ZIP code (with leading zeros) of the Location	Text	20554
ZIP4	4-digit add-on code (with leading zeros) of the Location	Text	0000
Lat	Latitude	Float	38.8835
Long	Longitude	Float	-77.0280
Loc_type	The type of Location is a 1=building; 2=other man-made structure; 3=cell site in or on a building; 4=free-standing cell site; 5=cell site on some other man-made structure, e.g., water tower; or 6=unknown.	Integer	1
IRU_Supplier	If Connections to this Location are obtained under an IRU, enter the name of the entity from which the majority of capacity is obtained.	Text	DEF Co.
UNE_Supplier	If Connections to this Location are obtained as a DS1/DS3 UNE, enter the name of the entity from which the UNE is obtained.	Text	DEF Co.
UCL_Supplier	If Connections to this Location are obtained as an Unbundled Copper Loop, enter the name of the entity from which the UCL is obtained.	Text	DEF Co.
Medium	Are any of the Connections to this Location provided over fiber? (Y/N)	Text	Y
Sold_bandwidth_total	Total bandwidth (in Mbps) of Connections provided to the Location as sold.	Float	1.544
Sold_bandwidth_enduser	Total bandwidth (in Mbps) of Connections provided to End Users at the Location as sold.	Float	1.544
Sold_bandwidth_tfw	Total bandwidth (in Mbps) of Connections provided to the Location using terrestrial fixed wireless as sold.	Float	1.544
Sold_bandwidth_Mobile	Total bandwidth (in Mbps) of Connections to cell sites at the Location as sold.	Float	1.544
Bandwidth_Internal	Total bandwidth used internally.	Float	1.544

Instructions for Table II.A.4, Record Format for Each Location (Competitive Providers):

Location_ID: This is a sequential integer ranging from 1 to the total number of unique Locations to which your company had a Connection during the year reported. This field is linked to the billing information reported in Question II.A.12 so that you must identify in Table II.A.4 every Location ID referenced in response to the billing information question.
Year: Report the year during which your company had a Connection to the Location, i.e., 2010 or 2012.
The data fields used to identify the actual situs address must be space-delimited in standardized Postal Service form. See http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.
Latitude and Longitude: You can derive the coordinate fields for the location address from a known geocoding platform like Bing maps, Google, Yahoo, batchgeo.com, Texas A&M Geoservices or other geocoding solution. Enter values in decimal degrees to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.
IRU_Supplier: Because multiple dedicated communication paths serving one or more End Users at the same Location must be counted as a single Connection (see definition of Connection), if you lease multiple IRUs to this Location from different Providers, identify the Provider that supplies the majority of the capacity you lease per an IRU. If only one Provider supplies the IRU(s), then identify that Provider as the supplier. If you do not know the name of the supplier of your Connections via IRU agreement(s), and cannot reasonably identify the supplier for each IRU, you can alternatively enter “unknown” in this field and indicate in the Explanatory Attachment the total number of Connections to Locations you obtain as an IRU and the general percentage of IRU leasing arrangements you have with particular types of suppliers, e.g., 45% of our IRUs are with ILECs, 55% with Competitive Providers or non-ILECs.
Sold_bandwidth fields: These data fields call for the reporting of total bandwidth sold. Report the downstream or upstream bandwidth of Dedicated Services sold across all sold Connections of the type requested at the Location as of December 31 of the year. Report the upstream or downstream bandwidth for symmetric services. For asymmetric services, report the average of the upstream and downstream bandwidths. For example, for a DS1 record 1.544, for three DS1s record 4.632, while for a 10 Gbit Ethernet service, 10,240, and for a fractional DS1 sold as a 384 Kbps service record 0.375. In the case where a Connection is in place but no bandwidth was provided as of December 31 of the year, enter the total bandwidth sold at the last known date during the relevant reporting period. For example, a customer or customers at the Location purchased service through October of the year but then terminated the service so that there was no service sold as of December 31; in that instance, report the total bandwidth sold in October. Exclude services other than Dedicated Service provided to the Location from your response. In the case where no Dedicated Service was sold to the Location, enter zero.
Bandwidth_Internal: If you are using bandwidth on this Connection to the Location for your own internal purposes, i.e., self-provisioning service to yourself or an Affiliated Company, then report the total bandwidth used internally as of December 31 of the year. Report the upstream or downstream bandwidth for symmetric services. For asymmetric services, report the average of the upstream and downstream bandwidths. For example, for a DS1 record 1.544, for three DS1s record 4.632, while for a 10 Gbit Ethernet service, 10,240, and for a fractional DS1 sold as a 384 Kbps service record 0.375. In the case where a Connection is in place but no bandwidth was used internally as of December 31 of the year, enter the total bandwidth used internally at the last known date during the relevant reporting period. In the case where no bandwidth was used for internal use, enter zero.

Question II.A.5: Fiber Network Map

Fiber Map. Competitive Providers must provide a map of the fiber routes that constitute their network. Include those fiber “spans” (i.e., lengths of fiber with terminating equipment on both ends) within your network that you (i) own or (ii) lease pursuant an IRU agreement. The map must show the fiber routes that constitute your network, including the “middle-mile” transport fiber network and any fiber routes to Locations.

You can file either a single map showing your network throughout your service territories in the United States or file separate maps showing the network on a regional/local basis. Filers are not required to include their long haul connections between service territories, e.g., interLATA connections between points of presence (POP) such as the connections between a POP in Los Angeles, California and POP in New York City.

Nodes. Identify all Nodes on your network that are points of interconnection with the networks of other Providers and indicate the year that the Node was first used for interconnecting with another Provider. Cable system operators must also separately indicate those Nodes that are headends that have been upgraded to provide a Metro Ethernet (or its equivalent) service. In lieu of identifying Nodes used for interconnection, you can submit to the Commission the interconnection data on file with the Central Location Online Entry System (CLONES) database for your operations.⁰ The certification submitted in connection with your submission will attest that the CLONES data are current and accurately depict your network interconnection points and the “live” dates to the best of your knowledge.

Mapping information must be provided as a separate ESRI Shapefile using a line feature class containing the data for each feature as noted below.

Shapefile Record Format for Fiber Network
Field Name	Description	Type	Example
Provider	Provider Name	Text	ABC Co.
DBA	“Doing-business-as” name	Text	Superfone, Inc.
FRN	Provider FCC Registration Number (with leading zeros)	Text	0008402202
ID	Sequential record number	Integer	1

Instructions for Shapefile Record Format for Fiber Network Map:

The shapefile must have an assigned projection w/accompanying .prj file.
The shapefile must use an unprojected (geographic) WGS84 geographic coordinate system.
The shapefile must conform to the 1:24,000 U.S. Geological Survey National Map standard.
The ID field is a sequential integer ranging from 1 to the total number of line features.
Maps must be accompanied by metadata or a plain text “readme” file that contains a comprehensive explanation of the methodology employed to generate the map layer including any necessary assumptions and an assessment of the accuracy of the finished product.
The shapefile must be submitted as a WinZip archive with a name containing the company name and FRN (e.g., CompanyName_12345678_Fiber.zip).
Cable system operators must include the FCC-assigned Physical System Identifier (PSID) associated with each system identified.

Node information must be provided as a delimited text file, e.g., .csv, that contains the following information.

Record Format for Nodes
Field Name	Description	Type	Example
Provider	Provider Name	Text	ABC Co.
DBA	“Doing-business-as” name	Text	Superfone, Inc.
FRN	Provider FCC Registration Number (with leading zeros)	Text	0008402202
ID	Sequential record number	Integer	1
Lat	Latitude	Float	38.8835
Long	Longitude	Float	-77.0280
Headend	Is this Node a headend that has been upgraded to provide a Metro Ethernet (or its equivalent) service? (Y=Yes; N=No)	Text	N
NodeYear	Date Node went “live” or when headend was upgraded to Metro Ethernet (or its equivalent) service	Integer	1996

Instructions for Record Format for Nodes:

Latitude and Longitude: Enter values in decimal degrees to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.The shapefile must be submitted as a WinZip archive with a name containing the company name and FRN (e.g., CompanyName_12345678_Fiber.zip).
NodeYear: If on or after 1995 the Node was first used for interconnecting with another Provider or in the case of cable system operators, was upgraded to provide Metro Ethernet (or its equivalent) service, then provide the year. If before 1995, then provide the year or enter 1000 if unknown. We encourage respondents to provide actual dates for as far back as they are able.

Uploading Documents. All files and documents responding to this question must be submitted to the FCC through the Special Access Web Portal (in the “Essay Questions – File Upload” section). You will not include this information in the data container.

The web portal contains two areas for uploading documents and files. One is for uploading the “Confidential” version of the document or file where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document or file noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document or file in each area or you will receive an error message during the submission process. If the document or file does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document or file in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Question II.A.6: Sampling History of Competitive Connections by Location

Based on your response to Question II.A.4, we will provide you with a list of Locations to which your company had a Connection in 2012. For each Location listed, provide the month and year – in the format set forth in Table II.A.6 – that you first served the Location with a Connection that you (i) owned; (ii) leased under an IRU; or (iii) obtained as a UNE to provide Dedicated Service.

We will derive the sample list of Locations as follows. A random sample will be drawn from the Locations entered in Table II.A.4 equal to the maximum of: (i) p percent of the Locations to which your company had a Connection in 2012 rounded up to the nearest integer or (ii) the number two.⁰ Competitive Providers with one such Location will not need to answer this question. The percentage p will be selected to ensure that about 1,600 sampling units are drawn; based on a current estimate that Competitive Providers serve on their own facilities 200,000 Locations, the value of p is expected to be on the order of 0.8 percent. This sample size is expected to provide ranges for estimates of proportions of the national population that are with 95% confidence expected to include the true value of the estimated proportion within ±2.5% of the estimate. For example, if the sample produces an estimate of 50% of the national population, the true value of the proportion would be in the range (47.5%, 52.5%) with 95% confidence. The four served Locations nearest each of the sampled served Locations will be added to the random sample of served Locations, and the resulting list, with duplicates removed, will be given to you.

To be clear, you will not include an answer to this question within the data container or otherwise with your initial submission to the data collection. The record format for when you do subsequently respond to this sampling question is provided below:

Record Format for History of Competitive Connections by Location
Field Name	Description	Type	Example
…	…The carrier’s record ID for a number of locations will be returned…	…	…
First_served	The month and year this Location was first served	Date	12/2009

Question II.A.7: Collocations by Wire Center

For each ILEC wire center where your company is collocated, provide the information listed below.

Table II.A.7 Record Format for Collocations by Wire Center
Field Name	Description	Type	Example
ID	Sequential record number	Integer	1
Street_address	Actual situs (i.e., land were building is located) address of the collocation site	Text	1025 N Irving Street
City	City of address	Text	Arlington
State	Two-letter state postal abbreviation of address	Text	VA
ZIP	5-digit ZIP code (with leading zeros) of address	Text	22201
ZIP4	4-digit add-on code (with leading zeros) of address	Text	0005
Lat	Latitude	Float	38.8840
Long	Longitude	Float	-77.0965
CLLI	Telcordia-specified eight-character CLLI	Alphanumeric	ARTNVAAR

Instructions for Table II.A.7, Record Format for Collocations by Wire Center:

Leave cells blank in the case of data that is not applicable for that record.
The ID field is a sequential integer ranging from 1 to the total number of wire centers.
Address data fields must be space-delimited in standardized Postal Service form. See http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.
Latitude and Longitude: You can derive the coordinate fields for the location address from a known geocoding platform like Bing maps, Google, Yahoo, batchgeo.com, Texas A&M Geoservices or other geocoding solution. Enter values in decimal degrees to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.
For the CLLI code, enter the first eight digits of the CLLI code of the ILEC wire center / end office in which your equipment is collocated.

Question II.A.8: Business Rules for Deployment

You must upload a .pdf text searchable (not a picture/image) document responding to this question through the Special Access Web Portal in the “Essay Questions – File Upload” section; you will not include these documents in the data container.

The web portal contains two areas for uploading documents. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Question II.A.9: Headquarters

Competitive Providers, except for cable system operators, must answer this question. Cable operators must still report “Not Applicable” as instructed below to avoid receiving an error message when validating the data container.

This question asks for the location of a Competitive Provider’s current and prior U.S. headquarters, going as far back as 1995. In addition, Competitive Providers must identify the headquarters of Affiliated Companies and entities acquired through merger that no longer exist if the affiliated or acquired entity owned (or leased under an IRU agreement) Connections to five or more Locations in a given MSA at the time of affiliation/acquisition, going as far back as 1995.

By “U.S. headquarters,” we mean the principal place where the company’s high level officers direct, control and coordinate the company’s activities.⁰ For purposes of this question, we do not consider regional field offices to be the U.S. headquarters for a company.

Table II.A.9.a-c Record Format for U.S. Headquarters
Field Name	Description	Type	Example
Street_address	Situs address of the U.S. headquarters (i.e., land were building is located)	Text	1025 N Irving Street
City	City name for U.S. headquarters	Text	Springfield
State	State name for U.S. headquarters	Text	Texas
ZIP	5 digit ZIP code for U.S. headquarters	Text	22201
ZIP4	4-digit add-on code (with leading zeros) of address	Text	0005
Year_Head	Year when U.S. headquarters established	Year	2000

Instructions for Table II.A.9.a-c, Record Format for U.S. Headquarters:

In the initial row of the table, you will identify your current U.S. headquarters and the year established in the Year_Head field. Cable system operators must type “Not Applicable” in the Street_Address field and complete the remaining fields with zeros. You will receive an error message upon validation of the data container if you do not put any information into these data fields.
In subsequent rows of the table, you will identify your prior U.S. headquarters going as far back as 1995 if different from the location of your current headquarters.

Table II.A.9.d Record Format for Headquarters of Acquired Entities
Field Name	Description	Type	Example
AcqEntity_Name	Name of acquired entity	Text	Local Fiber Incorporated
Street_address	Situs address for the U.S. headquarters of acquired entity at time of merger	Text	1025 N Irving Street
City	City name for U.S. headquarters	Text	Springfield
State	State name for U.S. headquarters	Text	Texas
ZIP	5 digit ZIP code for U.S. headquarters	Text	22201
ZIP4	4-digit add-on code (with leading zeros) of address	Text	0005
Year_Head	Year when entity merged, i.e., when transaction closed	Year	2000

Instructions for Table II.A.9.d, Record Format for Headquarters of Acquired Entities:

If you did not acquire an entity during the relevant reporting period or are a cable system operator, then you must still type “Not Applicable” in the AcqEntity_Name field and complete the remaining fields with zeros. You will receive an error message upon validation of the data container if you do not put any information into these data fields.

Table II.A.9.e-f Record Format for Headquarters for Affiliated Companies
Field Name	Description	Type	Example
AffCompany_Name	Name of Affiliated Company	Text	Local Fiber Incorporated
Year of Affiliation	Year you became affiliated with the Affiliated Company	Year	2007
Street_address	Situs address of the U.S. headquarters for Affiliated Company	Text	1025 N Irving Street
City	City name for U.S. headquarters	Text	Springfield
State	State name for U.S. headquarters	Text	Texas
ZIP	5 digit ZIP code for current U.S. headquarters	Text	22201
ZIP4	4-digit add-on code (with leading zeros) of address	Text	0005
Year_Head	Year when U.S. headquarters of Affiliated Company was established	Year	2000

Instructions for Table II.A.9.e-f, Record Format for Headquarters for Affiliated Companies:

In the initial row of the table, you will identify an Affiliated Company and the current U.S. headquarters of the Affiliated Company.
If the Affiliated Company had a prior U.S. headquarters – going back to 1995 or the year of affiliation, whichever is earlier, then on the next row identify the same company name in the AffCompany_Name field and provide information on the prior headquarters. If there is more than one prior headquarters for the Affiliated Company, going back to 1995 or the year of affiliation, whichever is earlier, then identify the prior headquarters in the subsequent rows.
Follow same reporting process for other Affiliated Companies in the subsequent rows of the table.
If you did not become affiliated with an Affiliated Company during the relevant reporting period, then you must still type “Not Applicable” in the AffCompany_Name field and complete the remaining fields with zeros. You will receive an error message upon validation of the data container if you do not put any information into these data fields.

Question II.A.10: Marketing Plans

You must upload all Word, Excel, and .pdf documents responding to this question through the Special Access Web Portal in the “Essay Questions – File Upload” section; you will not include these documents in the data container.

The web portal contains two areas for uploading documents. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Question II.A.11: Information on Requests for Proposals (RFPs)

Table II.A.11 Part 1 Record Format for RFPs
Field Name	Description	Type	Example
RFP_Type	Number 1-6 as follows: 1= Most recent RFP won for the provision of Dedicated Services 2= Most recent RFP won for the provision of Best Efforts Business Broadband Internet Access Services 3= Most recent RFP won for the provision of other high-capacity data services to business customers 4= Largest RFPs where you unsuccessfully submitted bids in the 2010-2012 timeframe for the provision of Dedicated Services 5= Largest RFPs where you unsuccessfully submitted bids in the 2010-2012 timeframe for the provision of Best Efforts Business Broadband Internet Access Services 6= Largest RFPs where you unsuccessfully submitted bids in the 2010-2012 timeframe for the provision of other high-capacity data services to business customers	Integer	1
RFP_Number	Sequential number 1-5	Integer	1
RFP_Name	Name of RFP	Text	ADA Greenfield
RFP_Description	Describe the RFP, including the date that the RFP was issued	Text	RFP requirements included . . .
RFP_Area_Covered	Identify the geographic areas covered by the RFP	Text	Network required to cover 26 counties in Michigan
RFP_Bid_Details	Details on your bid, including price offered	Text	Offered dedicated service for X amount.
Other_RFP_Details	Detail other competitively relevant information on RFP and/or bid	Text	Our bid offer included cost of leasing facilities in X areas from X where we did not own facilities.

Question II.A.11 Part 2. Question II.A.11 also asks Competitive Providers to identify the business rules relied upon to determine whether to submit a bid in response to an RFP. You must upload a .pdf text searchable (not a picture/image) document responding to this part of the question through the Special Access Web Portal in the “Essay Questions – File Upload” section; you will not include this document in the data container.

The web portal contains two areas for uploading documents. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Billing Information

Question II.A.12-14: Billing Information Overview

These questions are interrelated. Question II.A.12 requires the filer to provide billing information for each circuit element billed to its customers. To answer this question, you must reference adjustment and billing codes that are defined by responses to Questions II.A.13 and II.A.14, respectively.

Question II.A.12: Prices by Circuit Element from Competitive Provider

This question requests billing information for transmission paths that are sold for the provision of a stand-alone Dedicated Service. By using the term “transmission paths,” this question is not limited to Locations with Connections, i.e., “last-mile” facilities, reported in response to question II.A.4 but also includes dedicated interoffice transport facilities. Do not provide billing information for bundled services where the Dedicated Service component is not separately priced. Do include sales to Affiliated Companies.

Submit information for each circuit element of each circuit for each month from January 1, 2010 through December 31, 2010 and from January 1, 2012 through December 31, 2012. Include a separate entry for each separately-billed element on the circuit. In the case where circuits are billed as a single unit, the data set will contain only one entry per circuit.

Table II.A.12 Part 1 Record Format for Monthly Billing Data for Circuits by Circuit Element
Field Name	Description	Type	Example
Closing_Date	Closing date of the monthly billing cycle in mm/dd/yyyy format	Date	06/30/2012
Customer_ID	Unique customer identifier used to link all circuits purchased by a customer over all geographies and time periods. To be linked with customer names and identification numbers in Table II.A.12 Part 2.	Integer	1274
Location_ID	Sequential location number from Question II.A.4.a where applicable; required for circuit elements such as channel terminations that can be associated with a particular Location	Integer	1
Circuit_ID	Circuit identifier common to all circuit elements purchased in common for a particular circuit	Text	HHH555XYZ
Circuit_Type	Type of circuit (DS1, DS3, DS1-UNE, DS3-UNE, other CBDS (i.e., non-DSn), or PBDS.	Text	DS1
DSn_Bandwidth	If a DS1, DS3, DS1-UNE, or DS3-UNE, indicate the one-direction bandwidth of the circuit in Mbps.	Float	1.544
OtherCBDS_Bandwidth	If a CBDS circuit other than a DSn circuit, indicate the one-direction bandwidth of a symmetric circuit or the average one-direction bandwidth for non-symmetric circuits in Mbps.	Float	4.5
PBDS_Bandwidth	If a PBDS circuit, indicate the one-direction bandwidth of a symmetric circuit or the average one-direction bandwidth of non-symmetric circuits in Mbps.	Float	100
Billing_Code	Billing code (e.g., USOC) used to identify the billed circuit element. (This variable will also appear in Question II.A.14 and is used to link the billed circuit elements with their descriptions.)	Text	1YZXD
Quantity	Number of billed units for this circuit element. Do not enter the bandwidth of the circuit in this field.	Float	34
Initial_NRC	Non-recurring charge (in dollars) billed for the first unit of this circuit element	Float	0
Unit_NRC	Non-recurring charge (in dollars) billed for additional units of this circuit element	Float	0
Initial_MRC	Monthly recurring charge (in dollars) for the first unit billed	Float	17.7
Unit_MRC	Monthly recurring charge (in dollars) for additional units billed (if different from the amount billed for the initial unit)	Float	0
Billed	Per unit amount (in dollars) billed for the circuit element including all “in-cycle” discounts and penalties. For circuit elements with multiple billed units (i.e., quantity greater than one in II.A.12.g), enter the amount billed for a single unit	Float	507.3
Total_Billed	Total monthly amount (in dollars) billed for all units of the circuit element, including all “in-cycle” discounts and penalties	Float	12453.50
Term	Length of total time of the Term Commitment associated with this circuit (in months). List the total length of the current Term Commitment, not the remaining length of the Term Commitment. A circuit purchased on a month-to-month basis must be coded as 1.	Integer	36
End_Date	If this circuit has an associated Term Commitment, enter the month and year the term expires.	Date	03/2014
Term_Discount_IC	Indicator variable for whether any in-cycle term discounts have been rolled into the amount billed to the customer reported in the Billed field (0 = No in-cycle term discounts included in Billed amount; 1 = In-cycle term discounts included in Billed amount)	Integer	0
Volume_Commitment	Indicator variable showing whether this circuit contributes to a Volume Commitment (Y=Yes, N=No)	Text	N
Vol_Discount_IC	Indicator variable for whether any in-cycle volume discounts have been rolled into the amount billed to the customer reported in the Billed field (0 = No in-cycle volume discounts included in Billed amount; 1 = In-cycle volume discounts included in Billed amount)	Integer	0
Adjustment_ID_1	Unique ID number (from II.A.13) for the first billing adjustment / true-up affecting this circuit element. Leave the field blank if there are no discounts or penalties that occur during the monthly billing cycle affecting this circuit element.	Integer	1
Adjustment_ID_2	Unique ID number (from II.A.13) for the second billing adjustment / true-up affecting this circuit element, if more than one adjustment was applied to this circuit element. Leave the field blank if there are fewer than two discounts applied to this circuit element in the given billing cycle	Integer	26
…	[Continue to add columns for a total of ten (10) Adjusment_ID columns.]	…	…
Adjustment_ID_10	Unique ID number (from II.A.13) for the tenth billing adjustment/ true-up affecting this circuit element, if more than one adjustment was applied to this circuit element. Leave the field blank if there are fewer than ten discounts applied to this circuit element in the given billing cycle	Integer	15

Table II.A.12 Part 2 Record Format for Identifying Customers
Field Name	Description	Type	Example
Customer_ID	Unique customer identifier used to link all circuits purchased by a customer over all geographies and time periods. This field will be used to link the billing information in Table II.A.12 Part 1 with the customer names and identification numbers	Integer	1274
Customer_ID_499	Where applicable, include the six-digit 499A Filer ID of the customer	Integer	822116
Customer_ID_ACNA	Where applicable, include the Access Customer Name Abbreviation (ACNA) of the customer	String	ABC
Customer_ID_OCN	Where applicable, include the Operating Company Number (OCN) of the customer	Integer	1234
Customer_Name	Enter the name of the customer	Text	Verizon Wireless
Provider	Indicator variable denoting whether the circuit is purchased by a Provider (0 = non-Provider; 1 = Provider)	Integer	1

Instructions for Table II.A.12, Parts 1 and 2:⁰

Closing_Date: Enter the date on which the customer was billed. The date must appear in mm/dd/yyyy format. All dates must be in the ranges 01/01/2010 – 12/31/2010 or 01/01/2012 – 12/31/2012. Do not include data on circuits billed outside the appropriate date ranges, even if services were provided within the appropriate date ranges (e.g., service that was provided in December 2010 that was billed in January 2011). Likewise, include data on circuits billed in the appropriate date ranges, even if the service was provided outside of those ranges (e.g., service provided in December 2011 that was billed in January 2012).

The following fields in Parts 1 and 2 of Table II.A.12 are used to identify the customer of the Dedicated Service.⁰

Customer_ID: Assign a unique identifier to each customer so that all circuits purchased by the customer can be tracked over time and across locations. The identifiers must be entered in integer format. This Customer_ID will be used to link the circuit billing information (Table II.A.12, Part 1) to the customer names and identification numbers (Table II.A.12, Part 2). In Part 2, provide the customer name, an indicator for whether the customer is a Provider, and, where applicable, one of the following identification numbers: 499A filer ID, Access Customer Name Abbreviation (ACNA), or Operating Company Number (OCN). Note, the Customer_ID variable is required for all observations in both Part1 and Part 2. However, only one of the three additional identification numbers (499, ACNA, OCN) need be provided, even if multiple identification numbers are available. Each Customer_ID must appear only once in Part 2, but will likely appear multiple times in Part 1.
Customer_ID_499: Where applicable, include the 499A Filer ID of the customer in Part 2. The 499A Filer ID does not replace the Customer_ID variable. Both the Customer_ID and Customer_ID_499 fields are populated for any customer with a 499A Filer ID. If the customer does not have a 499A Filer ID, leave the field blank.
Customer_ID_ACNA: Where applicable, include the ACNA of the customer in Part 2. The ACNA does not replace the Customer_ID variable. Both the Customer_ID and Customer_ID_ACNA fields are populated for any customer with an ACNA. If the customer does not have an ACNA, leave the field blank.
Customer_ID_OCN: Where applicable, include the Operating Company Number (OCN) of the customer in Part 2. The OCN does not replace the Customer_ID variable. Both the Customer_ID and Customer_ID_OCN fields are populated for any customer with an OCN. If the customer does not have an OCN, leave the field blank.
Customer_Name: Enter the name of the customer in Part 2. The variable must be entered as a string and be no longer than 30 characters in length.
Provider: Indicate whether the customer is a Provider in Part 2, i.e., a customer that pays a pass through universal service contribution charge. Enter a 1 if the customer is a Provider and a 0 otherwise. In some instances, it may be difficult to identify if the customer is a Provider using billing information, but can often be inferred by the existence of a 499A Filer ID or by whether USF charges are passed on to the customer in their bill.

Location_ID: Include the Location ID reported in response to question II.A.4 for each circuit element on the circuit. The Location ID is used to link the billed circuit with the facilities information provided in Question II.A.4. That is, every Location ID referenced in response to Question II.A.12 must correspond to a Location ID reported in response to Question II.A.4.⁰ Also, for circuits that connect two Locations, the Location ID may not be constant within the Circuit ID. For example, the individual circuit elements for a given Circuit ID may include two channel terminations, each terminating at a different Location. The Location ID must be populated for every circuit element in the data set that can be tied to a Location. Specifically, any termination charge must be linked to a Location. If the sold Dedicated Service is not to a Location, e.g., the sale of dedicated interoffice transport, leave this field blank.

Circuit_ID: Assign a unique circuit identifier (Circuit ID) to all circuit elements purchased in common for a particular circuit. If the circuit is sold over multiple time periods, the circuit identifier must track the circuit across the multiple months and/or years it appears in the sample. We prefer that you code the Circuit IDs as sequential integers, beginning with the number “1” (similar to the Location ID). However, to the extent you have an established naming convention for your circuits, that convention may be substituted in place of sequential numbering. Code the Circuit ID as a string with a maximum of 15 characters. (Note: Because some filers may choose to use non-numeric characters in their coding, Circuit IDs must be coded as string variables, even if they have been renumbered as sequential integers.)

The following fields identify the type of circuit sold (Circuit Type), and the bandwidth of the circuit. The Circuit Type must be populated for every circuit element in the data set. Only one of the three bandwidth variables needs to be populated for each circuit element, depending on the type of circuit provided.

Circuit_Type: Indicate the type of circuit sold from the following categories: DS1, DS3, DS1-UNE, DS3-UNE, other CBDS circuit (i.e., non-DSn), or PBDS. For packages of DS1s and DS3s sold to a location, enter DS1 or DS3, respectively. Do not enter circuit types other than those listed above.
DSn_Bandwidth: If the circuit is a DS1, DS3, DS1-UNE, or DS3-UNE, enter the bandwidth of the circuit in Mbps, i.e., enter 1.544 for a DS1 and enter 44.736 for a DS3. In the case where multiple DSns are provisioned over a single circuit, enter the total bandwidth. For example, the bandwidth for a circuit with three DS1s must be entered as 4.632 (= 3 × 1.544). For non-DSn circuits, leave the field blank.
OtherCBDS_Bandwidth: If the circuit is a non-DSn CBDS circuit, enter the bandwidth of the circuit in Mbps. For symmetric services, the reported bandwidth is the one-way bandwidth of the circuit (i.e., upstream or downstream). For asymmetric services, report the average of the upstream and downstream bandwidths. Round the bandwidth of the circuit to three decimal places. For example, if the service guarantees 10 Mbps transmission speeds in one direction and 5 Mbps transmission speeds in the other direction, enter 7.500 in this field. If the circuit is a DSn or PBDS circuit, leave this field blank.
PBDS_Bandwidth: If the circuit is a PBDS circuit, enter the bandwidth of the circuit in Mbps. For symmetric services, the reported bandwidth is the one-way bandwidth of the circuit (i.e., upstream or downstream). For asymmetric services, report the average of the upstream and downstream bandwidths. For example, if the service guarantees 150 Mbps transmission speeds in one direction and 50 Mbps transmission speeds in the other direction, enter 100 in this field. Round the bandwidth of the circuit to three decimal places. For non-PBDS circuits, leave this field blank.

Billing_Code: The billing code variable (Billing Code) is used to identify the individual components of billed circuits. The Billing Code is used to link the billed circuit elements with the description of those elements in Question II.A.14. Examples of Billing Codes are Uniform Service Order Codes (USOCs). However, you are not required to use USOCs to identify the circuit elements; you can create your own Billing Codes. Similar circuit elements need to have the same Billing Code in order to track similar charges across circuits. To the extent that circuits are billed by individual circuit elements, the elements and billed amounts of the elements must be disaggregated into separate line-items in the table. If circuits are billed at the overall circuit level, only one line per circuit need be populated, and all like circuits may have the same Billing_Code and Billing Code description.

Quantity: Enter the number of billed units for this circuit element. Do not enter the bandwidth of the circuit in this field. For item codes that describe per-mile charges, the Quantity is the number of miles in the circuit that apply for that item code.

Initial_NRC: Insofar as the per unit monthly billed amount (Question II.A.12.l) can be broken into recurring and non-recurring charges, enter the non-recurring charge (in dollars) billed for the first unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Unit_NRC: Insofar as the per unit monthly billed amount (Question II.A.12.l) can be broken into recurring and non-recurring charges, enter the non-recurring charge (in dollars) billed for each additional unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Initial_MRC: Insofar as the per unit monthly billed amount (Question II.A.12.l) can be broken into recurring and non-recurring charges, enter the monthly recurring charge (in dollars) billed for the first unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Unit_MRC: Insofar as the per unit monthly billed amount (Question II.A.12.l) can be broken into recurring and non-recurring charges, enter the monthly recurring charge (in dollars) billed for each additional unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Billed: Per unit amount (in dollars) billed for the circuit element including all “in-cycle” discounts and penalties. “In-cycle” discounts and penalties are those adjustments that are rolled into the actual amount paid by the customer each month (see the instructions to Question II.A.13 for more information on “in-cycle” vs. “out-of-cycle” billing adjustments). If in-cycle adjustments show up as a separate line-item on the customer’s bill, they must be reported as separate line-items in Table II.A.12. Do not include any “out-of-cycle” adjustments as otherwise reported in response to Question II.A.12.p. For circuit elements with multiple billed units (i.e., quantity greater than one in Question II.A.12.g), enter the amount billed for a single unit, such that the product of Quantity and Billed is the total charge on the bill. For example, if the circuit includes two “channel termination” charges that are both billed at the same rate (and have the same Billing_Code (Question II.A.12.f), Location_ID, bandwidth, etc.), the quantity (Question II.A.12.g) is equal to 2, and the per unit monthly billed amount (Question II.A.12.l) is equal to the charge for a single channel termination. Alternatively, each channel termination may be recorded separately (i.e., on two separate lines with quantity equal to 1 for each line). The multiplicative product requirement also applies to charges for mileage of the circuit, if the circuit has such a charge. For example, if the circuit is 4 miles in length, the amount entered in Quantity is 4 and the amount entered in the Billed field is the charge per 1 mile. Enter the billed amount to two decimal places, and do not include other string characters (e.g., “$”). Fractional miles are permitted if the customer was billed for fractional mileage for any given circuit element. However, the amount entered in Billed must be converted to a whole-mile charge. For example, for a half mile circuit, the Quantity is reported as 0.5 on any per-mile circuit element, but the amount in Billed is the 1-mile charge such that the product of Quantity and Billed is equal to the total charge to the customer.

Total_Billed: Total monthly amount (in dollars) billed for all units of the circuit element including all “in-cycle” discounts and penalties. “In-cycle” discounts and penalties are those adjustments that are rolled into the actual amount paid by the customer each month (see the instructions to Question II.A.13 for more information on “in-cycle” vs. “out-of-cycle” billing adjustments). If in-cycle adjustments show up as a separate line-item on the customer’s bill, they must be reported as separate line-items in this table. Do not include any “out-of-cycle” adjustments as otherwise reported in Question II.A.12.p.

The following questions seek to understand the Term Commitments under which circuits are purchased.

Term: Length of total time of the Term Commitment associated with this circuit (in months). List the total length of the current Term Commitment, not the remaining length of the Term Commitment. For example, in reporting circuits for calendar month January 2010, enter 60 for a circuit that was sold in January 2007 under a 5 year commitment, even though only 24 months remain on the current term. For circuits sold on a month-to-month basis, enter 1. We anticipate that this value is identical for all circuit elements sold in common on the circuit. To the extent that the term length varies across different circuit elements, enter the appropriate Term Commitment for each individual circuit element.
End_Date: If the circuit has an associated total term longer than one month, enter the month and year the term expires. In the preceding example, the End_Date would be coded as 12/2012, sixty months after the five-year term was agreed to in January 2007. Leave the End_Date field blank for those circuits purchased on a month-to-month basis.
Term_Discount_IC: Indicate whether the per unit monthly billed amount in Question II.A.12.l includes any in-cycle discounts that have been applied due to a Term Commitment. Enter a 1 if the per unit monthly billed amount includes in-cycle term discounts; enter 0 if the per unit monthly billed amount does not include in-cycle term discounts. If the term discounts for this circuit are only given through out-of-cycle adjustments as reported in Question II.A.13, enter 0. If the circuit is not sold under a Term Commitment, leave this field blank.

Volume_Commitment: Indicate whether this circuit was sold under a Volume Commitment. Enter 0 if the circuit was not sold under a Volume Commitment, and enter 1 if the circuit was sold under a commitment by the Purchaser to purchase either a specified number of circuits or to spend a specified Revenue amount.

Vol_Discount_IC: Indicate whether the per unit monthly billed amount in Question II.A.12.l includes any in-cycle discounts that have been applied due to a Volume Commitment, either in total number of circuits or total amount of expenditures (“spend”). Enter a 1 if the per unit monthly billed amount includes in-cycle volume discounts; enter 0 if the per unit monthly billed amount does not include in-cycle volume discounts. If the volume discounts for this circuit are only given through out-of-cycle adjustments as reported in Question II.A.13, enter 0. If the circuit is not sold under a Volume Commitment, leave this field blank.

Adjustment_ID_1; Adjustment_ID_2; …Adjustment_ID_10: For each out-of-cycle billing adjustment applied to the circuit element, provide a unique adjustment ID that is used to link the circuit elements with the dollar value and descriptions of the appropriate adjustments. The table must include 10 columns for each of the ten potential Adjustment_IDs, regardless of whether all columns are used. For rate elements with fewer than ten out-of-cycle adjustments, leave the excess Adjustment_ID fields blank. If a circuit element had more than ten out-of-cycle adjustments applied to it, list the Adjustment_IDs of the ten largest adjustments. For example, if a circuit element receives five distinct adjustments, there must be five Adjustment_IDs in the first five columns. The remaining Adjustment_ID columns (i.e., columns 6 through 10) would be left blank. In addition, all adjustments must link back to the adjustment amounts and descriptions provided in response to Question II.A.13. See the instructions for Question II.A.13 for further instructions on adjustments.

Question II.A.13: Billing Adjustments

For each adjustment or true-up (including credits for meeting or penalties for not meeting contractual obligations) to billed circuit elements, provide the following information below. Provide the adjustment at the lowest level of aggregation available, and if possible, at the level of the individual circuit element. If the adjustment applies to multiple circuit elements and/or circuits, provide the total dollar amount of the billing adjustment, and include an Adjustment_ID for each circuit element reported in Question II.A.12 that can be used to link the billing adjustment (or true-up) with the appropriate circuit elements.

Note on “in-cycle” vs. “out-of-cycle” billing adjustments: Question II.A.13 is meant to capture all adjustments, penalties, and true-ups that are settled outside of the monthly billing cycle (as opposed to adjustments that are rolled into the price billed to the customer each month). Examples include lump-sum discounts for Term and Volume Commitments, early termination penalties, rebates for network outages or degraded service quality, waivers of non-recurring charges such as installation fees, etc.

For example, suppose a customer buys a single circuit with a One Month Term Only Rate of $300 per month, but receives a $100 discount on the One Month Term Only Rate each month for committing to a 5-year Term Commitment. If the Provider of the circuit rolls the discounted amount into the monthly bill, i.e., the customer is billed $200 every month, then the discount is considered an “in-cycle” adjustment, and the Provider need not report it as a separate “out-of-cycle” adjustment in Table II.A.13. The seller would only need to report the $200 charge in Question II.A.12, along with an indicator showing a Term Commitment in Question II.A.12.m. (Alternatively, depending on the billing system, the discount may show up as a separate -$100 line item in Question II.A.12 along with the $300 One Month Term Only Rate.)

However, if the Provider charges the customer the full $300 for the circuit every month, then returns a $600 payment to the purchaser every 6 months, the $600 payment must be recorded in Table II.A.13 as an out-of-cycle adjustment, and the appropriate Adjustment_ID must appear next to the affected circuit elements in Question II.A.12. Likewise, if the customer is billed at the $200 discounted rate each month but then decides to terminate the contract early and pay an early termination fee of $1000, the $1000 charge is recorded as an out-of-cycle adjustment in Question II.A.13.

Table II.A.13 Record Format for Billing Adjustment Data Circuits by Circuit
Field Name	Description	Type	Example
Adjustment_ID	Unique ID number for the billing adjustment or true-up	Integer	1
Contract_ID	Unique ID number for the Tariff or other agreement from which the adjustment originates. Leave the field blank if the adjustment cannot be linked back to a single contract	Integer	33
Date_from	Beginning date of adjustment period (or true-up) in mm/dd/yyyy format	Date	01/01/2012
Date_to	Ending date of adjustment period (or true-up) in mm/dd/yyyy format	Date	06/30/2012
Adjustment_Scope	Code indicating scope of adjustment. Enter 1 if adjustment applies to single circuit element for single circuit, enter 2 if adjustment applies to more than one circuit element on a single circuit, enter 3 if adjustment applies to more than one circuit element across multiple circuits, enter 4 if the adjustment is an overall adjustment that applies to every circuit purchased.	Integer	2
Adjustment	Total dollar amount of billing adjustment (or true-up) for all circuit elements across all circuits covered by the adjustment. Any increase in the amount owed to the vendor (e.g., penalty) is a positive number while any decrease in the amount owed to the vendor (e.g., discount or rebate) is a negative number.	Float	-100
Adj_Term	Indicator variable denoting whether the adjustment/true-up was due to a Term Commitment (Y=Yes, N=No)	Text	N
Adj_Term_Length	If Adj_Term=1, enter the term length in months. If Adj_Term=0, leave blank	Integer	60
Adj_Vol	Indicator variable denoting whether the adjustment/true-up was due to a Volume Commitment (Y=Yes, N=No)	Text	N
Adj_Vol_Circ	If Adj_Vol=1, and the Tariff or other agreement required the purchase of a certain number of circuits, enter the number of circuits specified in the Tariff or other agreement which are necessary to qualify for the adjustment. If Adj_Vol=0, or the adjustment corresponds to a commitment to a given level of expenditures/spend, leave the field blank	Integer	500
Adj_Vol_Rev	If Adj_Vol=1, and the Tariff or other agreement required the purchase of a certain dollar amount of expenditures/spend, enter the dollar value of the expenditure requirement. If Adj_Vol=0 or the adjustment corresponds to a commitment to purchase a certain number of circuits, leave the field blank	Float	20,000
Adjustment_Other	If the adjustment/true-up is for some other reason, give a brief description of the reason for the adjustment	Text	Network Outage

Instructions for Table II.A.13, Record Format for Billing Adjustment Data Circuits by Circuit:

The following questions identify each out-of-cycle billing adjustment with an adjustment ID and the Tariff or other agreement from which they originate.

Adjustment_ID: Create a unique adjustment ID for each out-of-cycle billing adjustment applied to customer purchases during the relevant timeframe. Although each Adjustment_ID may correspond to multiple circuit elements in Table II.A.12, each must appear only once in Table II.A.13. Only include adjustments which were charged/remitted to the customer during the 2010 and 2012 reporting periods. For example, do not include adjustments that were charged/remitted in January 2011, even if the adjustment applied to service provided in December 2010. Likewise, report any adjustments charged/remitted in January 2012, even if those adjustments applied to service provided in December 2011.
Contract_ID: Assign a unique ID number for the Tariff or other agreement from which the adjustment originates. This field is used to group adjustments together by Tariff or other agreement. Leave the field blank if the adjustment cannot be linked back to a single contract.

Date_From: Enter the beginning date of the adjustment period in mm/dd/yyyy format. For example, if the Tariff or other agreement specifies a rebate to the customer every three months, enter the beginning date of the three-month period for which the rebate applies, and not the beginning date of the Tariff or other agreement from which the adjustment originated. Likewise, do not enter the date on which the adjustment was charged/remitted.

Date_To: Enter the ending date of the adjustment period in mm/dd/yyyy format. For example, if a Tariff or other agreement specifies a rebate be returned to the customer every three months, enter the ending date of the 3-month period for which the rebate applies, and not the ending date of the Tariff or other agreement from which the adjustment originated. Likewise, do not enter the date on which the adjustment was charged/remitted.

Adjustment_Scope: Enter the scope of the adjustment according to the following codes: Enter 1 if the adjustment applies to a single circuit element on a single circuit. Enter 2 if the adjustment applies to more than one element on a single circuit. Enter 3 if the adjustment applies to more than one circuit elements across multiple circuits. Enter 4 if the adjustment is an overall adjustment that applies to every circuit purchased by the customer (as indicated by the Customer_ID in Question II.A.12). Apply the codes as described above, even if the adjustment applies to multiple time periods. For example, if a rebate is given for a single circuit element on a single circuit (as determined by the Circuit_ID in Question II.A.12), assign an Adjustment_Scope of 1, even if the adjustment period (as determined by Date_From and Date_To) extends over multiple months.

Adjustment: Enter the total dollar amount of the billing adjustment for all circuit elements across all circuits and across the entire adjustment period. Any increase in the amount owed to the vendor (e.g., penalty) must be a positive number, while any decrease in the amount owed to the vendor (e.g., discount or rebate) must be a negative number. For example, suppose the Provider gave the customer a $2000 rebate on 10/31/2010, and that this rebate covered 100 circuits purchased during the six-month period from 04/01/2010 to 10/01/2010. In this case, the filer must enter “-2000” in the Adjustment field with the appropriate Date_From and Date_To values. In addition, the Adjustment_Scope (see above) must be recorded as 3, and the Adjustment_ID for this specific rebate must be included next to the 100 circuits in the Adjustment_ID_# fields in Table II.A.12.

These fields describe the type of adjustment applied to the circuit elements.

Adj_Term: If the adjustment/true-up can be linked to a rebate given (or penalty charged) on a Term Commitment, enter 1. Enter 0 if the adjustment was not due to a Term Commitment.
Adj_Term_Length: If Adj_Term is equal to 1, enter the total term length (not the remaining term length) in months. If Adj_Term is equal to 0, leave the Adj_Term_Length variable blank.
Adj_Vol: Enter 1 if the adjustment/true-up can be linked to a rebate (or penalty) on a Volume Commitment. Enter 0 if the adjustment was not due to a Volume Commitment. If the Volume Commitment corresponds to a certain number of circuits, enter the number of circuits necessary to qualify for the discount in the Adj_Vol_Circ field. If the Volume Commitment corresponds to a certain level of “spend” or dollar value of services, enter the dollar amount necessary to qualify for the discount in the Adj_Vol_Rev field.
Adj_Vol_Circ: If Adj_Vol is equal to 1, and the Tariff or other agreement required the purchase of a certain number of circuits to qualify for a discount, enter the number of circuits. If Adj_Vol is equal to 0 or the Volume Commitment was a commitment to a given level of expenditures or “spend,” leave this field blank.
Adj_Vol_Rev: If Adj_Vol is equal to 1 and the Tariff or other agreement required the purchase of a certain dollar amount of expenditures (or “spend”) to qualify for a discount, enter the dollar value of the expenditure requirement. If Adj_Vol is equal to 0 or the Volume Commitment was a commitment to purchase a certain number of circuits, leave this field blank.
Adjustment_Other: If the adjustment/true-up was for some reason other than a Term or Volume Commitment, give a brief description of the reason in this field. Do not exceed 120 characters in your response. Leave blank if either Adj_Term or Adj_Vol is equal to 1. An example of such an adjustment may be a rebate remitted to the purchaser in compensation for an unanticipated network outage or degraded quality of service.

Question II.A.14: Billing Code Descriptions

Provide descriptions for each unique billing code referenced in Table II.A.12 Part 1. Enter one record for each unique billing code. Examples of common circuit elements are given in the diagram in Question II.A.14.b. If the billed element cannot be described by the elements listed in the diagram, provide a description of the billed element as indicated in Question II.A.14.c. For example, to the extent you bill circuits as a whole, rather than on an element-by-element basis, provide a description that describes the billed unit, see Question II.A.14.c, and assign a single unique billing code.

Table II.A.14 is used to link the descriptions of billing codes with the billed circuit elements reported in Table II.A.12 Part 1 using the Billing_Code variable in each table. Although each Billing_Code may appear multiple times in Table II.A.12 Part 1, you can only have one entry for each unique Billing_Code reported in Table II.A.14. Additionally, every Billing_Code that appears in Table II.A.12 Part 1 must be identified in Table II.A.14.

Table II.A.14 Record Format for Descriptions for Circuits by Circuit
Field Name	Description	Type	Example
Billing_Code	Billing code (e.g., USOC) used to identify the billed circuit element. (This variable will aslo appear in Question II.A.12 and is used to link the billed circuit elements with their descriptions)	Text	1YZXD
Billing_Code_Description	Brief description of circuit element	Text	Channel Mileage
Billing_Code_Desc_Other	The description of the circuit element as it appears on the customer’s bill.	Text

Instructions for Table II.A.14, Record Format for Descriptions for Circuits by Circuit:

Billing_Code: The billing code variable is used to identify the individual components of billed circuits. The billing code is used to link the billed circuit elements in Question II.A.12 with the description of those elements in Question II.A.14. A USOC is an example of billing code. However, USOC codes are not required to identify the circuit elements; you can create your own billing code. Enter the billing code as a string variable not to exceed 15 characters in length.

Billing_Code_Description: Choose the description from the list/diagram in Question II.A.14 that best describes the circuit element. See list of circuit elements in Question II.A.14.b. Make every effort to assign the billed element to one of the categories listed here. If the item billed to the customer does not fit any of these categories, this field may be left blank and the billed element can be described in the field Billing_Code_Desc_Other. This may occur, for example, if circuits are billed as a complete package instead of on an element-by-element basis (i.e., all the elements in the circuit are billed together under a single price). In such a case, a single billing code for the circuit elements listed in Question II.A.14.b may not apply; this field may be left blank and the appropriate description of the billed item may be filled out in Billing_Code_Desc_Other.

Billing_Code_Desc_Other: Enter a longer description of the circuit element. For circuit elements categorized under one of the descriptions in Billing_Code_Description, this field is optional. If Billing_Code_Description is left blank, this field is required. Keep descriptions under 150 characters.

Revenues, Terms and Conditions Information

Question II.A.15: Sales Revenues for CBDS

Table II.A.15 Record Format for CBDS Revenues
Field Name	Description	Type	Example
Revenue	Enter the total dollar amount of your Revenues from the sale of CBDS for the reported Year	Float	123,456
Service_Type	Indicate the service type category for which the Revenues are reported. Enter “DS1” for DS1 Revenues, enter “DS3” for DS3 Revenues, and enter “Other” for other CBDS Revenues.	Text	DS3
Customer_Type	Enter 0 if the reported Revenues are for End Users, and enter 1 if the reported Revenues are for Providers	Binary	1
Year	Enter “2010” if the reported Revenues are for the year 2010, and enter “2012” if the reported Revenues are for the year 2012	Integer	2012

Question II.A.16: Sales Revenues for PBDS

Table II.A.16 Record Format for PBDS Revenues
Field Name	Description	Type	Example
Revenue	Enter the total dollar amount of your Revenues from the sale of PBDS for the reported Year	Float	123,456
Bandwidth	Indicate the bandwidth category for which the Revenues are reported. Enter “A” for bandwidth less than or equal to 1.5 Mbps, enter “B” for bandwidth greater than 1.5 Mbps but less than or equal to 50 Mbps, enter “C” for bandwidth greater than 50 Mbps but less than or equal to 100 Mbps, enter “D” for bandwidth greater than 100 Mbps but less than or equal to 1 Gbps, and enter “E” for bandwidth greater than 1 Gbps	Text	D
Customer_Type	Enter 0 if the reported Revenues are for End Users, and enter 1 if the reported Revenues are for Providers	Binary	1
Year	Enter “2010” if the reported Revenues are for the year 2010, and enter “2012” if the reported Revenues are for the year 2012	Integer	2012

Question II.A.17: Percentage of Revenues Generated from Agreement or Tariff Containing a Prior Purchase-Based Commitment

Table II.A.17 Record Format for Revenues Generated by Prior Purchase-Based Commitments
Field Name	Description	Type	Example
Percent_Rev_2012_DS1_PPC	Percentage of Revenue from sales of DS1s in 2012 from agreements or tariffs which contain Prior Purchase-Based Commitments	Percentage	5.0
Percent_Rev_2012_DS3_PPC	Percentage of Revenue from sales of DS3s in 2012 from agreements or tariffs which contain Prior Purchase-Based Commitments	Percentage	5.0
Percent_Rev_2012_PBDS_PPC	Percentage of Revenue from sales of PBDS in 2012 from agreements or tariffs which contain Prior Purchase-Based Commitments	Percentage	5.0

Question II.A.18: How do your terms and conditions compare with ILEC offerings?

Question II.A.19: Business Justification for Term and Volume Commitments

You must upload a .pdf text searchable (not a picture/image) document responding to Questions II.A.18 and II.A.19 through the Special Access Web Portal in the “Essay Questions – File Upload” section; you will not include these documents in the data container.

The web portal contains two areas for uploading documents for each question. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

QUESTIONS DIRECTED AT ILECS

Question II.B.1: Affiliated Company

If you are an Affiliated Company, then you must identify each entity you are affiliated with that provides and/or purchases Dedicated Service in Table II.B.1 within the data container. If you are not an Affiliated Company, then you must still type “Not Applicable” in the Affiliate_Name field and “0000000000” in the Name_FRN field. You will receive an error message upon validation of the data container if you do not put any information into Table II.B.1.

Table II.B.1 Record Format for Affiliated Company
Field Name	Description	Type	Example
Affiliate_ID	Sequential number	Integer	1
Affiliate_Name	Name of entity with which you are affiliated	Text	Local Fiber Incorporated
Name_FRN	Entity’s FCC Registration Number (with leading zeros)	Integer	0008402202

Facilities Information

Question II.B.2: ILEC Locations Data for ILECs

ILECs are required to report the total number of Locations to which they provided a Connection during 2010 and during 2012 where the ILEC either: (i) owned the Connection; or (ii) leased the Connection from another entity under an IRU.⁰ The definition of Connection is crafted to assist the Commission with sizing the broader market for Dedicated Services by including transmission facilities used to provide a Dedicated Service and facilities that are “capable” of providing a Dedicated Service.

To help ILECs identify reportable Locations, we provide the following guidance:

Respondents must only report Connections to non-residential Locations. A Location is where an End User is connected, and an End User means a business, institutional, or government entity that purchases service for its own purposes, not for resell. Accordingly, residential locations connected by facilities are not reported.

Copper loops that were unable to provide a bandwidth connection of at least 1.5 Mbps in both directions (upstream/downstream) during the relevant reporting periods “as provisioned” are not considered Connections capable of providing a Dedicated Service for the purposes of this data collection and are not reported.

In addition to reporting Connections used to provide a Dedicated Service, report Connections used to provide a service that incorporates a Dedicated Service within the offering as part of a managed solution or bundle of services sold to the customer.^⁰

Do not report Connections to Locations that were used to provide services during the relevant reporting period that were substantially similar to the services provided to residential customers, e.g., one or two line telephone service or best-efforts Internet access and subscription television services like AT&T’s U-verse or Verizon’s FiOS service.⁰

Table II.B.2 Record Format for Total Locations
Field Name	Description	Type	Example
Year	Indicator of the calendar year of the data	Integer	2010
Locations	Total Locations served during year	Integer	15

Instructions for Table II.B.2, Record Format for Total Locations (ILECs):

Locations: The number of Locations is the count of unique Locations to which your company provided a Connection during the year entered in Year. The number of Locations listed here must equal the number of unique Locations enumerated in Question II.B.3 for each year.

Question II.B.3: Locations Data for ILECs

The purpose of this question is to obtain additional information on the individual Locations with Connections that make up the total reported in response to Question II.B.2.

Table II.B.3 Record Format for Each Location
Field Name	Description	Type	Example
Location_ID	Sequential Location number	Integer	1
Year	Indicator of the calendar year of the data	Integer	2010
Street_address	Actual situs for the Location (i.e., land were building or cell site is located)	Text	445 Twelfth St SW
City	City of the Location	Text	Washington
State	Two-letter state postal abbreviation of the Location	Text	DC
ZIP	5-digit ZIP code (with leading zeros) of the Location	Text	20554
ZIP4	4-digit add-on code (with leading zeros) of the Location	Text	0000
Lat	Latitude	Float	38.8835
Long	Longitude	Float	-77.0280
Loc_type	The type of Location served is a 1=building; 2=other man-made structure; 3=cell site in or on a building; 4=free-standing cell site; 5=cell site on some other man-made structure, e.g., water tower; or 6=unknown.	Integer	1
Medium	Are any of the Connections to this Location provided over fiber? (Y/N)	Text	N
Sold_bandwidth_total	Total bandwidth (in Mbps) of Connections provided to the Location as sold.	Float	1.544
Sold_bandwidth_UNE	For those Connections sold as UNE-DS1s or UNE-DS3s, total bandwidth (in Mbps) of the Connections provided to the Location as sold.	Float	1.544
Sold_bandwidth_enduser	Total bandwidth (in Mbps) of Connections provided to End Users at the Location as sold.	Float	1.544
Sold_bandwidth_tfw	Total bandwidth (in Mbps) of Connections provided to the Location using terrestrial fixed wireless as sold.	Float	1.544
Sold_bandwidth_Mobile	Total bandwidth (in Mbps) of Connections to cell sites at the Location as sold.	Float	1.544

Instructions for Table II.B.3, Record Format for Each Location (ILECs):

Location_ID: This is a sequential integer ranging from 1 to the total number of unique Locations to which your company provided a Connection during the year reported. This field is linked to the billing information reported in Question II.B.4 so that you must identify in Table II.B.3 every Location ID referenced in response to the billing information question.
Year: Report the year during which your company provided a Connection to the Location, i.e., 2010 or 2012.
The data fields used to identify the actual situs address must be space-delimited in standardized Postal Service form. See http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.
Latitude and Longitude: You can derive the coordinate fields for the location address from a known geocoding platform like Bing maps, Google, Yahoo, batchgeo.com, Texas A&M Geoservices, or other geocoding solution. Enter values in decimal degrees to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.
Sold_bandwidth fields: These data fields call for the reporting of total bandwidth sold. Report the downstream or upstream bandwidth of Dedicated Services sold across all sold Connections of the type requested at the Location as of December 31 of the year. Report the upstream or downstream bandwidth for symmetric services. For asymmetric services, report the average of the upstream and downstream bandwidths. For example, for a DS1 record 1.544, for three DS1s record 4.632, while for a 10 Gbit Ethernet service, 10,240, and for a fractional DS1 sold as a 384 Kbps service record 0.375. In the case where a Connection is in place but no bandwidth was provided as of December 31 of the year, enter the total bandwidth sold at the last known date during the relevant reporting period. For example, a customer or customers at the Location purchased service through October of the year but then terminated the service so that there was no service sold as of December 31; in that instance, report the total bandwidth sold in October. Exclude services other than Dedicated Service provided to the Location from your response. In the case where no Dedicated Service was sold to the Location, enter zero.

Billing Information

Question II.B.4-6: Billing Information Overview

These questions are interrelated. Question II.B.4 requires the filer to provide billing information for each circuit element billed to its customers. To answer this question, you must reference adjustment and billing codes that are defined by responses to Questions II.B.5 and II.B.6, respectively.

Question II.B.4: Prices by Circuit Element from ILECs

This question requests billing information for transmission paths that are sold for the provision of a stand-alone Dedicated Service. By using the term “transmission paths,” this question is not limited to Locations with Connections, i.e., “last-mile” facilities, reported in response to Question II.B.3 but also includes dedicated interoffice transport facilities. Do not, however, include the sale of interLATA POP-to-POP services or billing information for bundled services where the Dedicated Service component is not separately priced. Do include sales to Affiliated Companies.

Submit information for each circuit element of each circuit for each month from January 1, 2010 through December 31, 2010 and from January 1, 2012 through December 31, 2012. Include a separate entry for each separately-billed element on the circuit. In the case where the circuits are billed as a single unit, the data set will contain only one entry per circuit.

Table II.B.4 Part 1 Record Format for Monthly Billing Data for Circuits by Circuit and Rate Element
Field Name	Description	Type	Example
Closing_Date	Closing date of the monthly billing cycle in mm/dd/yyyy format	Date	06/30/2012
Customer_ID	Unique customer identifier used to link all circuits purchased by a customer over all geographies and time periods. To be linked with customer names and identification numbers in Table II.B.4 Part 2.	Integer	1274
Location_ID	Sequential location number from Question II.B.3.a. where applicable. Required for circuit elements such as channel terminations that can be associated with a particular Location.	Integer	1
Circuit_ID	Circuit identifier common to all circuit elements purchased in common for a particular circuit.	Text	HHH555XYZ
Circuit_Type	Type of circuit (DS1, DS3, DS1-UNE, DS3-UNE, other CBDS (i.e., non-DSn), or PBDS.	Text	DS1
DSn_Bandwidth	If a DS1, DS3, DS1-UNE, or DS3-UNE, indicate the one-direction bandwidth of the circuit in Mbps.	Float	1.544
OtherCBDS_Bandwidth	If a CBDS circuit other than a DSn circuit, indicate the one-direction bandwidth of a symmetric circuit or the average one-direction bandwidth of a non-symmetric circuit in Mbps	Float	7.5
PBDS_Bandwidth	If a PBDS circuit, indicate the one-direction bandwidth of a non-symmetric circuit or the average one-direction bandwidth of a non-symmetric circuit in Mbps.	Float	75
MRP1	Serving wire center / mileage rating point CLLI for one end of the circuit	Text	CHCGILCL
MRP2	Serving wire center / mileage rating point CLLI for the other end of the circuit	Text	JOLTILJO
MRP1_Lat	Latitude of MRP1	Float	38.8835
MRP1_Long	Longitude of MRP1	Float	-77.0280
MRP2_Lat	Latitude of MRP2	Float	38.8835
MRP2_Long	Longitude of MRP2	Float	-77.0280
MRP_Type	End of the circuit (1=MRP1 or 2=MRP2) associated with this circuit element. Enter 0 if the circuit element cannot be attributed to either MRP or the circuit element can be attributed to both ends of the MRP. All channel terminations must be attributed to one of the two MRPs	Integer	0
Billing_Code	Billing code (e.g., USOC) used to identify the billed circuit element. (This variable will also appear in Question II.B.6 and is used to link the billed circuit elements with their descriptions)	Text	1YZXD
Zone	Density pricing zone for the circuit element. See 47 C.F.R. § 69.123 (If not applicable, leave field blank)	Integer	4
Quantity	Number of billed units for this circuit element. Do not enter the bandwidth of the circuit in this field.	Float	34
Initial_NRC	Non-recurring charge (in dollars) billed for the first unit of this circuit element	Float	0
Unit_NRC	Non-recurring charge (in dollars) billed for additional units of this circuit element	Float	0
Initial_MRC	Monthly recurring charge (in dollars) for the first unit billed	Float	17.7
Unit_MRC	Monthly recurring charge (in dollars) for additional units billed (if different from the amount billed for the initial unit)	Float	0
Billed	Per unit monthly amount (in dollars) billed for the circuit element including all “in-cycle” discounts and penalties. For circuit elements with multiple billed units (i.e., quantity greater than one in II.B.4.o), enter the amount billed for a single unit	Float	507.3
Total_Billed	Total monthly amount (in dollars) billed for all units of the circuit element, including all “in-cycle” discounts and penalties	Float	12453.50
Term	Length of total time of the Term Commitment associated with this circuit (in months). List the total length of the current Term Commitment, not the remaining length of the Term Commitment. A circuit purchased on a month-to-month basis is coded as 1.	Integer	36
End_Date	If this circuit has an associated Term Commitment, enter the month and year the term expires	Date	03/2014
Term_Discount_IC	Indicator variable for whether any in-cycle term discounts have been rolled into the amount billed to the customer reported in the Billed field (0 = No in-cycle term discounts included in Billed amount; 1 = In-cycle term discounts included in Billed amount)	Integer	0
Volume_Commitment	Indicator variable showing whether this circuit contributes to a Volume Commitment (Y=Yes, N=No)	Text	N
Vol_Discount_IC	Indicator variable for whether any in-cycle volume discounts have been rolled into the amount billed to the customer reported in the Billed field (0 = No in-cycle volume discounts included in Billed amount; 1 = In-cycle volume discounts included in Billed amount)	Integer	0
Offer	Indicator variable showing whether this circuit was purchased out of a Contract-Based Tariff (Y=Yes, N=No)	Text	N
Adjustment_ID_1	Unique ID number (from II.B.5.a) of the first billing adjustment/true-up affecting this circuit element. Leave field blank if there are no discounts or penalties that occur during the monthly billing cycle affecting this circuit element	Integer	6
Adjustment_ID_2	Unique ID number (from II.B.5.a) of the second billing adjustment/true-up affecting this circuit element, if multiple adjustments were applied to this rate element. Leave the field blank if there are fewer than two discounts applied to this circuit element in the given billing cycle	Integer	14
…	[Continue to add columns for a total of ten (10) Adjustment_ID columns.]	…	…
Adjustment_ID_10	Unique ID number (from II.B.5.a) of the tenth billing adjustment/true-up affecting this circuit element, if multiple adjustments were applied to this rate element. Leave the field blank if there are fewer than ten discounts applied to this circuit element in the given billing cycle	Integer	63

Table II.B.4 Part 2 Record Format for Identifying Customers
Field Name	Description	Type	Example
Customer_ID	Unique customer identifier used to link all circuits purchased by a customer over all geographies and time periods. This field will be used to link the billing information in Table II.B.4 Part 1 with the customer names and identification numbers	Integer	1274
Customer_ID_499	Where applicable, include the six-digit 499A Filer ID of the customer	Integer	822116
Customer_ID_ACNA	Where applicable, include the Access Customer Name Abbreviation (ACNA) of the customer	Text	ABC
Customer_ID_OCN	Where applicable, include the Operating Company Number (OCN) of the customer	Integer	1234
Customer_Name	Enter the name of the customer	Text	Verizon Wireless
Provider	Indicator variable denoting whether the circuit is purchased by a Provider (0 = non-Provider; 1 = Provider)	Integer	1

Instructions for Table II.B.4, Parts 1 and 2:⁰

Closing_Date: Enter the date on which the customer was billed. The date must appear in mm/dd/yyyy format. All dates must be in the ranges 01/01/2010 – 12/31/2010 or 01/01/2012 – 12/31/2012. Do not include data on circuits billed outside the appropriate date ranges, even if services were provided within the appropriate date ranges (e.g., service that was provided in December 2010 that was billed in January 2011). Likewise, include data on circuits billed in the appropriate date ranges, even if the service was provided outside of those ranges (e.g., service provided in December 2011 that was billed in January 2012).

The following fields in Parts 1 and 2 of Table II.B.4 are used to identify the customer of the Dedicated Service.⁰

Customer_ID: Assign a unique identifier to each customer so that all circuits purchased by the customer can be tracked over time and across locations. The identifiers must be entered in integer format. This Customer_ID will be used to link the circuit billing information (Table II.B.4 Part 1) to the customer names and identification numbers (Table II.B.4 Part 2). In Part 2, provide the customer name, an indicator for whether the customer is a Provider, and, where applicable, one of the following identification numbers: 499A filer ID, Access Customer Name Abbreviation (ACNA), or Operating Company Number (OCN). Note, the Customer_ID variable is required for all observations in both Part1 and Part 2. However, only one of the three additional identification numbers (499, ACNA, OCN) need be provided, even if multiple identification numbers are available. Each Customer_ID must appear only once in Part 2, but will likely appear multiple times in Part 1.
Customer_ID_499: Where applicable, include the 499A Filer ID of the customer. The 499A Filer ID does not replace the Customer_ID variable. Both the Customer_ID and Customer_ID_499 fields are populated for any customer with a 499A Filer ID. If the customer does not have a 499A Filer ID, leave the field blank.
Customer_ID_ACNA: Where applicable, include the Access Company Name Abbreviation (ACNA) of the customer in Part 2. The ACNA does not replace the Customer_ID variable. Both the Customer_ID and Customer_ID_ACNA fields are populated for any customer with an ACNA. If the customer does not have an ACNA, leave the field blank.
Customer_ID_OCN: Where applicable, include the Operating Company Number (OCN) of the customer in Part 2. The OCN does not replace the Customer_ID variable. Both the Customer_ID and Customer_ID_OCN fields are populated for any customer with an OCN. If the customer does not have an OCN, leave the field blank.
Customer_Name: Enter the name of the customer in Part 2 of Question II.B.4. The variable must be entered as a string and be no longer than 30 characters in length.
Provider: Indicate whether the customer is a Provider in Part 2. Enter a 1 if the customer is a Provider and a 0 otherwise. In some instances, it may be difficult to identify if the customer is a Provider using billing information, but can often be inferred by the existence of a 499A Filer ID or by whether USF charges are passed on to the customer in their bill.

Location_ID: Include the Location ID for each circuit element on the circuit. The Location ID is used to link the billed circuit with the facilities information reported in Question II.B.3. That is, every unique Location ID referenced in Question II.B.4 must match to a Location ID reported in II.B.3. Also, for circuits that connect two Locations, the Location ID may not be constant within the Circuit ID. For example, the individual circuit elements for a given Circuit ID may include two channel terminations, each terminating at a different Location. The Location ID must be populated for every circuit element in the data set. Specifically, any termination charge must be linked to a Location. If the sold Dedicated Service is not to a Location, e.g., the sale of dedicated interoffice transport, leave this field blank.

Circuit_ID: Assign a unique circuit identifier (Circuit ID) to all circuit elements purchased in common for a particular circuit. If the circuit is sold over multiple time periods, the circuit identifier must track the circuit across the multiple months and/or years it appears in the sample. We prefer that you code the Circuit IDs as sequential integers, beginning with the number “1” (similar to the Location ID). However, to the extent you have an established naming convention for your circuits, that convention may be substituted in place of sequential numbering. Code the Circuit ID as a string with a maximum of 15 characters. (Note: Because some filers may choose to use non-numeric characters in their coding, Circuit IDs must be coded as string variables, even if they have been renumbered as sequential integers.)

The following fields identify the type of circuit sold (Circuit Type), and the bandwidth of the circuit. The Circuit Type must be populated for every circuit element in the data set. Only one of the three bandwidth variables needs to be populated for each circuit element, depending on the type of circuit provided.

Circuit_Type: Indicate the type of circuit sold from the following categories: DS1, DS3, DS1-UNE, DS3-UNE, other CBDS circuit (i.e., non-DSn), or PBDS. For packages of DS1s and DS3s sold to a Location, enter DS1 or DS3, respectively. Do not enter circuit types other than those listed above.
DSn_Bandwidth: If the circuit is a DS1, DS3, DS1-UNE, or DS3-UNE, enter the bandwidth of the circuit in Mbps, i.e., enter 1.544 for a DS1 and enter 44.736 for a DS3. In the case where multiple DSns are provisioned over a single circuit, enter the total bandwidth. For example, the bandwidth for a circuit with three DS1s must be entered as 4.632 (= 3 × 1.544). For non-DSn circuits, leave the field blank.
OtherCBDS_Bandwidth: If the circuit is a non-DSn CBDS circuit, enter the bandwidth of the circuit in Mbps. For symmetric services, the reported bandwidth is the one-way bandwidth of the circuit (i.e., upstream or downstream). For asymmetric services, report the average of the upstream and downstream bandwidths. Round the bandwidth of the circuit to three decimal places. For example, if the service guarantees 10 Mbps transmission speeds in one direction and 5 Mbps transmission speeds in the other direction, enter 7.500 in this field. If the circuit is a DSn or PBDS circuit, leave this field blank.
PBDS_Bandwidth: If the circuit is a PBDS circuit, enter the bandwidth of the circuit in Mbps. For symmetric services, the reported bandwidth is the one-way bandwidth of the circuit (i.e., upstream or downstream). For asymmetric services, report the average of the upstream and downstream bandwidths. For example, if the service guarantees 150 Mbps transmission speeds in one direction and 50 Mbps transmission speeds in the other direction, enter 100 in this field. Round the bandwidth of the circuit to three decimal places. For non-PBDS circuits, leave this field blank.

MRP1: Enter the 8-character CLLI for the serving wire center or mileage rating point (MRP) on one end of the circuit.

MRP2: Enter the 8-character CLLI for the serving wire center or MRP on the other end of the circuit.

MRP1_Lat: Enter the latitude coordinate of MRP1 to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.

MRP1_Long: Enter the longitude coordinate of MRP1 to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.

MRP2_Lat: Enter the latitude coordinate of MRP2 to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.

MRP2_Long: Enter the longitude coordinate of MRP2 to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.

MRP_Type: If the billed circuit element can be associated with a specific wire center/mileage rating point, indicate whether the wire center/mileage rating point is MRP1 or MRP2 above. Enter a 1 if the circuit element is associated with MRP1 and enter 2 if the circuit element is associated with MRP2. If the circuit element cannot be attributed to a single wire center, or if the circuit element can be associated with both wire centers, enter 0 in the MRP_Type field. For example, a channel termination from a customer location to MRP1 is coded as 1 in this field. An interconnection charge between your network and the network of another carrier at MRP2 is coded as 2. A transport mileage charge between MRP1 and MRP2 must be coded as a zero (unless that mileage is able to be attributed to either MRP1 or MRP2). All charges for channel terminations need to be attributed to one of the MRPs.

Billing_Code: The billing code variable (Billing Code) is used to identify the individual components of billed circuits. The Billing Code is used to link the billed circuit elements with the description of those elements in Question II.B.6. An example of a Billing Code is a USOC. However, you are not required to use a USOC to identify the circuit elements; you can create your own Billing Codes. Similar circuit elements need to have the same Billing Code in order to track similar charges across circuits. To the extent that circuits are billed to customers by individual circuit elements, the elements (along with the billed amounts for those elements) must be disaggregated into separate line-items in Table II.B.4. If circuits are billed at the overall circuit level, only one line per circuit need be populated, and all like circuits may have the same Billing_Code and Billing Code description.

Zone: Enter the density pricing zone for this circuit element. See 47 C.F.R. § 69.123 (density pricing zones for special access and switched transport). If you enter a density pricing zone, then explain the density breakpoints between each zone for your applicable study area(s) in your Explanatory Attachment,⁰ e.g., pricing zone one contains offices having at least 500 equivalent DS1 channels, pricing zone two contains offices having at least 100, but no more than 499, equivalent DS1 channels, etc. If the density pricing zone is not applicable for a particular circuit element or group of circuit elements, leave the field blank.

Quantity: Enter the number of billed units for this circuit element. Do not enter the bandwidth of the circuit in this field. For item codes that describe per-mile charges, the Quantity is the number of miles in the circuit that apply for that item code.

Initial_NRC: Insofar as the per unit monthly billed amount (Question II.B.4.t) can be broken into recurring and non-recurring charges, enter the non-recurring charge (in dollars) billed for the first unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Unit_NRC: Insofar as the per unit monthly billed amount (Question II.B.4.t) can be broken into recurring and non-recurring charges, enter the non-recurring charge (in dollars) billed for each additional unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Initial_MRC: Insofar as the per unit monthly billed amount (Question II.B.4.t) can be broken into recurring and non-recurring charges, enter the monthly recurring charge (in dollars) billed for the first unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Unit_MRC: Insofar as the per unit monthly billed amount (Question II.B.4.t) can be broken into recurring and non-recurring charges, enter the monthly recurring charge (in dollars) billed for each additional unit of this circuit element on this circuit. Enter the charge to two decimal places and do not include other string characters (e.g., “$”).

Billed: Per unit monthly amount (in dollars) billed for the circuit element including all “in-cycle” discounts and penalties. “In-cycle” discounts and penalties are those adjustments that are rolled into the actual amount paid by the customer each month (see the instructions to Question II.B.5 for more information on “in-cycle” vs. “out-of-cycle” billing adjustments). If in-cycle adjustments show up as a separate line-item on the customer’s bill, they must be reported as separate line-items in Table II.B.4. Do not include any “out-of-cycle” adjustments as otherwise reported in response to Question II.B.4.y. For circuit elements with multiple billed units (i.e., quantity greater than one in Question II.B.4.o), enter the amount billed for a single unit, such that the product of Quantity and Billed is the total charge on the bill. For example, if the circuit includes two “channel termination” charges that are both billed at the same rate (and have the same Billing_Code (Question II.B.4.m), Location_ID, bandwidth, etc.), the quantity (Question II.B.4.o) is equal to 2, and the per unit monthly billed amount (Question II.B.4.t) must equal the charge for a single channel termination. Alternatively, each channel termination may be recorded separately (i.e., on two separate lines with quantity equal to 1 for each line). The multiplicative product requirement also applies to charges for mileage of the circuit, if the circuit has such a charge. For example, if the circuit is 4 miles in length, the amount entered in Quantity is 4 and the amount entered in the Billed field is the charge per 1 mile. Enter the billed amount to two decimal places, and do not include other string characters (e.g., “$”). Fractional miles are permitted if the customer was billed for fractional mileage for any given circuit element. However, the amount entered in the Billed field must be converted to a whole-mile charge. For example, for a half mile circuit, the Quantity is reported as 0.5 on any per-mile circuit element, but the amount in Billed is the 1-mile charge such that the product of Quantity and Billed is equal to the total charge to the customer.

Total_Billed: Total monthly amount (in dollars) billed for all units of the circuit element including all “in-cycle” discounts and penalties. “In-cycle” discounts and penalties are those adjustments that are rolled into the actual amount paid by the customer each month (see the instructions to Question II.B.5 for more information on “in-cycle” vs. “out-of-cycle” billing adjustments). If in-cycle adjustments show up as a separate line-item on the customer’s bill, they must be reported as separate line-items in this table. Do not include any “out-of-cycle” adjustments as otherwise reported in Question II.B.4.y.

The following questions seek to understand the Term Commitments under which circuits are purchased.

Term: Length of total time of the Term Commitment associated with this circuit (in months). List the total length of the current Term Commitment, not the remaining length of the Term Commitment. For example, in reporting circuits for calendar month January 2010, enter 60 for a circuit that was sold in January 2007 under a 5 year commitment, even though only 24 months remain on the current term. For circuits sold on a month-to-month basis, enter 1. We anticipate that this value is identical for all circuit elements sold in common on the circuit. To the extent that the term length varies across different circuit elements, enter the appropriate term commitment for each individual circuit element.
End_Date: If the circuit has an associated total term longer than one month, enter the month and year the term expires. In the preceding example, the End_Date would be coded as 12/2012, sixty months after the five-year term was agreed to in January 2007. Leave the End_Date field blank for those circuits purchased on a month-to-month basis.
Term_Discount_IC: Indicate whether the per unit monthly billed amount in Question II.B.4.t includes any in-cycle discounts that have been applied due to a Term Commitment. Enter a 1 if the per unit monthly billed amount includes in-cycle term discounts; enter 0 if the per unit monthly billed amount does not include in-cycle term discounts. If the term discounts for this circuit are only given through out-of-cycle adjustments as reported in Question II.B.5, enter 0. If the circuit is not sold under a Term Commitment, leave this field blank.

Volume_Commitment: Indicate whether this circuit was sold under a Volume Commitment. Enter 0 if the circuit was not sold under a Volume Commitment, and enter 1 if the circuit was sold under a commitment by the customer to purchase either a specified number of circuits or to spend a specified Revenue amount.

Vol_Discount_IC: Indicate whether the per unit monthly billed amount in Question II.B.4.t includes any in-cycle discounts that have been applied due to a Volume Commitment, either in total number of circuits or total amount of expenditures (“spend”). Enter a 1 if the per unit monthly billed amount includes in-cycle volume discounts; enter 0 if the per unit monthly billed amount does not include in-cycle volume discounts. If the volume discounts for this circuit are only given through out-of-cycle adjustments as reported in Question II.B.5, enter 0. If the circuit is not sold under a Volume Commitment, leave this field blank.

Offer: Indicate whether the circuit was purchased under a Contract-Based Tariff. Enter 1 if the circuit was purchased under a Contract-Based Tariff and enter 0 if it was not.

Adjustment_ID_1; Adjustment_ID_2; …Adjustment_ID_10: For each out-of-cycle billing adjustment applied to the circuit element, provide a unique adjustment ID that is used to link the circuit elements with the dollar value and descriptions of the appropriate adjustments. The table must include 10 columns for each of the ten potential Adjustment_IDs, regardless of whether all columns are used. For rate elements with fewer than ten out-of-cycle adjustments, leave the excess Adjustment_ID fields blank. If a circuit element had more than ten out-of-cycle adjustments applied to it, list the Adjustment_IDs of the ten largest adjustments. For example, if a circuit element receives five distinct adjustments, there must be five Adjustment_IDs in the first five columns. The remaining Adjustment_ID columns (i.e., columns 6 through 10) would be left blank. In addition, all adjustments must link back to the adjustment amounts and descriptions provided in response to Question II.B.5. See the instructions for Question II.B.5 for further instructions on adjustments.

Question II.B.5: Billing Adjustments

For each adjustment or true-up (including credits for meeting or penalties for not meeting contractual obligations) to billed circuit elements, provide the following information below. Provide the adjustment at the lowest level of aggregation available, and if possible, at the level of the individual circuit element. If the adjustment applies to multiple circuit elements and/or circuits, provide the total dollar amount of the billing adjustment, and include an Adjustment_ID for each circuit element reported in Question II.B.4 that can be used to link the billing adjustment (or true-up) with the appropriate circuit elements.

Note on “in-cycle” vs. “out-of-cycle” billing adjustments: Question II.B.5 is meant to capture all adjustments, penalties, and true-ups that are settled outside of the monthly billing cycle (as opposed to adjustments that are rolled into the price billed to the customer each month). Examples include lump-sum discounts for Term and Volume Commitments, early termination penalties, rebates for network outages or degraded service quality, waivers of non-recurring charges such as installation fees, etc.

For example, suppose a customer buys a single circuit with a One Month Term Only Rate of $300 per month, but receives a $100 discount on the One Month Term Only Rate each month for committing to a 5-year Term Commitment. If the Provider of the circuit rolls the discounted amount into the monthly bill, i.e., the customer is billed $200 every month, then the discount is considered an “in-cycle” adjustment, and the Provider need not report it as a separate “out-of-cycle” adjustment in Table II.B.5. The seller would only need to report the $200 charge in Question II.B.4, along with an indicator showing a Term Commitment in Question II.B.4.u. (Alternatively, depending on the billing system, the discount may show up as a separate -$100 line item in Question II.B.4 along with the $300 One Month Term Only Rate.)

However, if the Provider charges the customer the full $300 for the circuit every month, then returns a $600 payment to the purchaser every 6 months, the $600 payment must be recorded in Table II.B.5 as an out-of-cycle adjustment, and the appropriate Adjustment_ID must appear next to the affected circuit elements in Question II.B.4. Likewise, if the customer is billed at the $200 discounted rate each month but then decides to terminate the contract early and pay an early termination fee of $1000, the $1000 charge must be recorded as an out-of-cycle adjustment in Question II.B.5.

Table II.B.5 Record Format for Billing Adjustment Data Circuits by Circuit
Field Name	Description	Type	Example
Adjustment_ID	Unique ID number for the billing adjustment or true-up	Integer	1
Contract_ID	Unique ID number for the Tariff or other agreement from which the adjustment originates. Leave the field blank if the adjustment cannot be linked back to a single contract	Integer	33
Date_from	Beginning date of adjustment period (or true-up) in mm/dd/yyyy format	Date	01/01/2012
Date_to	Ending date of adjustment period (or true-up) in mm/dd/yyyy format	Date	06/30/2012
Adjustment_Scope	Code indicating scope of adjustment. Enter 1 if adjustment applies to single circuit element for single circuit, enter 2 if adjustment applies to more than one circuit element on a single circuit, enter 3 if adjustment applies to more than one circuit element across multiple circuits, enter 4 if the adjustment is an overall adjustment that applies to every circuit purchased.	Integer	2
Adjustment	Total dollar amount of billing adjustment (or true-up) for all circuit elements across all circuits covered by the adjustment. Any increase in the amount owed to the vendor (e.g., penalty) is a positive number while any decrease in the amount owed to the vendor (e.g., discount or rebate) is a negative number.	Float	-100
Adj_Term	Indicator variable denoting whether the adjustment/true-up was due to a Term Commitment (Y=Yes, N=No)	Text	Y
Adj_Term_Length	If Adj_Term=1, enter the term length in months. If Adj_Term=0, leave blank	Integer	60
Adj_Vol	Indicator variable denoting whether the adjustment/true-up was due to a Volume Commitment (Y=Yes, N=No)	Text	Y
Adj_Vol_Circ	If Adj_Vol=1, and the Tariff or other agreement required the purchase of a certain number of circuits, enter the number of circuits specified in the Tariff or other agreement which are necessary to qualify for the adjustment. If Adj_Vol=0, or the adjustment corresponds to a commitment to a given level of expenditures/spend, leave blank	Integer	500
Adj_Vol_Rev	If Adj_Vol=1, and the Tariff or other agreement required the purchase of a certain dollar amount of expenditures/spend, enter the dollar value of the expenditure requirement. If Adj_Vol=0 or the adjustment corresponds to a commitment to purchase a certain number of circuits, leave the field blank	Float	20,000
Adjustment_Other	If the adjustment/true-up is for some other reason, give a brief description of the reason for the adjustment	Text	Network Outage

Instructions for Table II.B.5, Record Format for Billing Adjustment Data Circuits by Circuit:

The following questions identify each out-of-cycle billing adjustment with an adjustment ID and the Tariff or other agreement from which they originate.

Adjustment_ID: Create a unique adjustment ID for each out-of-cycle billing adjustment applied to customer purchases during the relevant timeframe. Although each Adjustment_ID may correspond to multiple circuit elements in Table II.B.4, each must appear only once in Table II.B.5. Only include adjustments which were charged/remitted to the customer during the 2010 and 2012 reporting periods. For example, do not include adjustments that were charged/remitted in January 2011, even if the adjustment applied to service provided in December 2010. Likewise, report any adjustments charged/remitted in January 2012, even if those adjustments applied to service provided in December 2011.
Contract_ID: Assign a unique ID number for the Tariff or other agreement from which the adjustment originates. This field is used to group adjustments together by the Tariff or other agreement. Leave the field blank if the adjustment cannot be linked back to a single Tariff or other agreement.

Date_From: Enter the beginning date of the adjustment period in mm/dd/yyyy format. For example, if a Tariff or other agreement specifies a rebate be returned to the customer every three months, enter the beginning date of the three-month period for which the rebate applies, and not the beginning date of the Tariff or other agreement from which the adjustment originated. Likewise, do not enter the date on which the adjustment was charged/remitted.

Date_To: Enter the ending date of the adjustment period in mm/dd/yyyy format. For example, if a Tariff or other agreement specifies a rebate to the customer every three months, enter the ending date of the 3-month period for which the rebate applies, and not the ending date of the Tariff or other agreement from which the adjustment originated. Likewise, do not enter the date on which the adjustment was charged/remitted.

Adjustment_Scope: Enter the scope of the adjustment according to the following codes: Enter 1 if the adjustment applies to a single circuit element on a single circuit. Enter 2 if the adjustment applies to more than one element on a single circuit. Enter 3 if the adjustment applies to one or more circuit elements across multiple circuits. Enter 4 if the adjustment is an overall adjustment that applies to every circuit purchased by the customer (as indicated by the Customer_ID in Question II.B.3). Apply the codes as described above, even if the adjustment applies to multiple time periods. For example, if a rebate is given for a single circuit element on a single circuit (as determined by the Circuit_ID in Question II.B.3), assign an Adjustment_Scope of 1, even if the adjustment period (as determined by Date_From and Date_To) extends over multiple months.

Adjustment: Enter the total dollar amount of the billing adjustment for all circuit elements across all circuits and across the entire adjustment period. Any increase in the amount owed to the vendor (e.g., penalty) is a positive number, while any decrease in the amount owed to the vendor (e.g., discount or rebate) is a negative number. For example, suppose the Provider gave a customer a $2000 rebate on 10/31/2010, and that this rebate covered 100 circuits purchased during the six-month period from 04/01/2010 to 10/01/2010. In this case, the filer must enter “-2000” in the Adjustment field with the appropriate Date_From and Date_To values. In addition, the Adjustment_Scope (see above) is recorded as 3, and the Adjustment_ID for this specific rebate is included next to the 100 circuits in the Adjustment_ID_# fields in Table II.B.4.

These fields describe the type of adjustment applied to the circuit elements.

Adj_Term: If the adjustment/true-up can be linked to a rebate given (or penalty charged) on a Term Commitment, enter 1. Enter 0 if the adjustment was not due to a Term Commitment.
Adj_Term_Length: If Adj_Term is equal to 1, enter the total term length (not the remaining term length) in months. If Adj_Term is equal to 0, leave the Adj_Term_Length variable blank.
Adj_Vol: Enter 1 if the adjustment/true-up can be linked to a rebate (or penalty) on a Volume Commitment. Enter 0 if the adjustment was not due to a Volume Commitment. If the Volume Commitment corresponds to a certain number of circuits, enter the number of circuits necessary to qualify for the discount in the Adj_Vol_Circ field. If the Volume Commitment corresponds to a certain level of “spend” or dollar value of services, enter the dollar amount necessary to qualify for the discount in the Adj_Vol_Rev field.
Adj_Vol_Circ: If Adj_Vol is equal to 1, and the Tariff or other agreement required the purchase of a certain number of circuits to qualify for a discount, enter the number of circuits. If Adj_Vol is equal to 0 or the Volume Commitment was a commitment to a given level of expenditures or “spend”, leave this field blank.
Adj_Vol_Rev: If Adj_Vol is equal to 1 and the Tariff or other agreement required the purchase of a certain dollar amount of expenditures (or “spend”) to qualify for a discount, enter the dollar value of the expenditure requirement. If Adj_Vol is equal to 0 or the Volume Commitment was a commitment to purchase a certain number of circuits, leave this field blank.
Adjustment_Other: If the adjustment/true-up was for some reason other than a Term or Volume Commitment, give a brief description of the reason in this field. Do not exceed 120 characters in your response. Leave blank if either Adj_Term or Adj_Vol is equal to 1. An example of such an adjustment may be a rebate remitted to the customer in compensation for an unanticipated network outage or degraded quality of service.

Question II.B.6: Billing Code Descriptions

Provide descriptions for each unique billing code referenced in Table II.B.4 Part 1. Enter one record for each unique billing code. Examples of common circuit elements are given in the diagram in Question II.B.6.b. If the billed element cannot be described by the elements listed in the diagram, provide a description of the billed element. To the extent you bill circuits as a whole, rather than on an element-by-element basis, describe the billed unit, see Question II.B.6.c, and assign a single unique ID.

Table II.B.6 is used to link the descriptions of billing codes with the billed circuit elements reported in Table II.B.4 Part 1 using the Billing_Code variable in each table. Although each Billing_Code may appear multiple times in Table II.B.4 Part 1, you can only have one entry for each unique Billing_Code reported in Table II.B.6. Additionally, every Billing_Code that appears in Table II.B.4 Part 1 must be identified in Table II.B.6.

Table II.B.6 Record Format for Descriptions for Circuits by Circuit
Field Name	Description	Type	Example
Billing_Code	Billing code (e.g., USOC) used to identify the billed circuit element. (This variable will aslo appear in Question II.B.4 and is used to link the billed circuit elements with their descriptions)	Text	1YZXD
Billing_Code_Description	Brief description of circuit element	Text	Channel Mileage
Billing_Code_Desc_Other	The description of the circuit element as it appears on the customer’s bill.	Text

Instructions for Table II.B.6, Record Format for Descriptions for Circuits by Circuit:

Billing_Code: The billing code variable is used to identify the individual components of billed circuits. The billing code is used to link the billed circuit elements in question II.B.4 with the description of those elements in Question II.B.6. A USOC is an example of billing code. However, USOC codes are not required to identify the circuit elements; you can create your own billing code. Enter the billing code as a string variable not to exceed 15 characters in length.

Billing_Code_Description: Choose the description from the list/diagram in Question II.B.6 that best describes the circuit element. See list of circuit elements in Question II.B.6.b. Make every effort to assign the billed element to one of the categories listed here. If the item billed to the customer does not fit any of these categories, this field may be left blank and the billed element can be described in the field Billing_Code_Desc_Other. This may occur, for example, if circuits are billed as a complete package instead of on an element-by-element basis (i.e., all the elements in the circuit are billed together under a single price). In such a case, a single billing code for the circuit elements listed in Question II.B.6.b may not apply; this field may be left blank and the appropriate description of the billed item may be filled out in Billing_Code_Desc_Other.

Billing_Code_Desc_Other: Enter a longer description of the circuit element. For circuit elements categorized under one of the descriptions in Billing_Code_Description, this field is optional. If Billing_Code_Description is left blank, this field is required. Keep descriptions under 150 characters.

Question II.B.7: Wire Centers - CLLI Codes - Regulatory Treatment

Table II.B.7 Record Format for Wire Centers
Field Name	Description	Type	Example
CLLI	Telcordia-specified eight-character CLLI of the ILEC wire center / exchange area with collocation(s)	Text	WASHDCSW
Street_address	Actual situs for the wire center (i.e., land were wire center is located)	Text	445 Twelfth St SW
City	City of the wire center	Text	Washington
State	Two-letter state postal abbreviation of the wire center	Text	DC
ZIP	5-digit ZIP code (with leading zeros) of the wire center	Text	20554
ZIP4	4-digit add-on code (with leading zeros) of the wire center	Text	0000
Lat	Latitude	Float	38.8835
Long	Longitude	Float	-77.0280

Latitude and Longitude: You can derive the coordinate fields for the location address from a known geocoding platform like Bing maps, Google, Yahoo, batchgeo.com, Texas A&M Geoservices, or other geocoding solution. Enter values in decimal degrees to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.

Revenues, Terms and Conditions Information

Question II.B.8: Sales Revenues for CBDS

Table II.B.8 Record Format for CBDS Revenues
Field Name	Description	Type	Example
Revenue	Enter the total dollar amount of your Revenues from the sale of CBDS for the reported Year	Float	123,456
Service_Type	Indicate the service type category for which the Revenues are reported. Enter “DS1” for DS1 Revenues, enter “DS3” for DS3 Revenues, and enter “Other” for other CBDS Revenues	Text	DS3
Customer_Type	Enter 0 if the reported Revenues are for End Users, and enter 1 if the reported Revenues are for Competitive Providers	Binary	1
Year	Enter “2010” if the reported Revenues are for the year 2010, and enter “2012” if the reported Revenues are for the year 2012	Integer	2012

Question II.B.9: Sales Revenues for PBDS

Table II.B.9 Record Format for PBDS Revenues
Field Name	Description	Type	Example
Revenue	Enter the total dollar amount of your Revenues from the sale of PBDS for the reported Year	Float	123,456
Bandwidth	Indicate the bandwidth category for which the Revenues are reported. Enter “A” for bandwidth less than or equal to 1.5 Mbps, enter “B” for bandwidth greater than 1.5 Mbps but less than or equal to 50 Mbps, enter “C” for bandwidth greater than 50 Mbps but less than or equal to 100 Mbps, enter “D” for bandwidth greater than 100 Mbps but less than or equal to 1 Gbps, and enter “E” for bandwidth greater than 1 Gbps	Text	D
Customer_Type	Enter 0 if the reported Revenues are for End Users, and enter 1 if the reported Revenues are for Competitive Providers	Binary	1
Year	Enter “2010” if the reported Revenues are for the year 2010, and enter “2012” if the reported Revenues are for the year 2012	Integer	2012

Question II.B.10: Revenues from One Month Term Only Rates

Table II.B.10 Record Format Revenues from One Month Term Only Rates
Field Name	Description	Type	Example
Revenues	Enter the total dollar amount of your Revenues from One Month Term Only Rates charged for the reported Year	Float	123,456
Service_Type	Indicate the service type category for which the Revenues are reported. Enter “DS1” for DS1 Revenues, enter “DS3” for DS3 Revenues, and enter “PBDS” for PBDS Revenues	Text	PBDS
Customer_Type	Enter 0 if the reported Revenues are for End Users, and enter 1 if the reported Revenues are for Competitive Providers	Binary	1
Year	Enter “2010” if the reported Revenues are for the year 2010 and enter “2012” if the reported Revenues are for the year 2012	Integer	2012

Question II.B.11: Number of Customers with One Month Term Only Rates

Table II.B.11 Record Format for Customers with One Month Term Only Rates
Field Name	Description	Type	Example
OMT_CustCount	Number of One Month Term Only Rate customers for DS1s, DS3s, and PBDS as of Dec. 31, 2012	Integer	54,321
Service_Type	Indicate the service type category for which the Revenues are reported. Enter “DS1” for DS1 Revenues, enter “DS3” for DS3 Revenues, and enter “PBDS” for PBDS Revenues	Text	DS1
Customer_Type	Enter 0 if the reported Revenues are for End Users, and enter 1 if the reported Revenues are for Competitive Providers	Binary	1

Question II.B.12: All Applicable Tariff Plans and Contract-Based Tariffs

Table II.B.12 Record Format for Applicable Tariff Plans and Contract-Based Tariffs
Field Name	Description	Type	Example
Tar_Plan	Plan is a Tariff Plan (Y=Yes, N=No)	Text	Y
CBT_Plan	Plan is a Contract-Based Tariff (Y=Yes, N=No)	Text	N
Plan_Name	Name of plan	Text	Green Tariff
Tar_Sec	Tariff Section and Number	Text	ABC Co. FCC No. 2 § 7.90
Term_Com	Does plan contain a Term Commitment? (Y=Yes, N=No)	Text	Y
Vol_Com	Does plan contain a Volume Commitment? (Y=Yes, N=No)	Text	Y
Non_Rate_Benefit	Does plan contain a Non-Rate Benefit option? (Y=Yes, N=No)	Text	Y
Non_Rate_Benefit_Exp	If plan contains a Non-Rate Benefit option, explain the Non-Rate Benefits.	Text	Plan allows for circuit portability . . .
Plan_DS1	Does plan apply to purchase of DS1s? (Y=Yes, N=No)	Text	Y
Plan_DS3	Does plan apply to purchase of DS3s? (Y=Yes, N=No)	Text	Y
Plan_PBDS	Does plan apply to purchase of PBDS? (Y=Yes, N=No)	Text	Y
Plan_Other	Does plan apply to purchase of other services? (Y=Yes, N=No)	Text	Y
Plan_Geo_Nat	Is the plan available across your entire nationwide service area? Enter “Y” if the plan is available across your entire service area, including both within and outside of MSAs, and enter “N” if it is only available in a subset of your service area.	Text	N
Plan_Geo_MSA	If the plan is not available across your entire nationwide service area (i.e., Plan_Geo_Nat = “N”), indicate whether the plan is available in at least one MSA. Enter “Y” if the plan is available in at least one MSA, and enter “N” if it is only available in non-MSA areas. If Plan_Geo_Nat = “Y”, the value for Plan_Geo_MSA must be “Y”	Text	Y
Plan_Geo_nonMSA	If the plan is not available across your entire nationwide service area (i.e., Plan_Geo_Nat = “N”), indicate whether the plan is available in at least one non-MSA area. Enter “Y” if the plan is available in at least one non-MSA, and enter “N” if it is only available in MSAs. If Plan_Geo_Nat = “Y”, the value for Plan_Geo_nonMSA must be “Y”	Text	N
PPB_Com	To receive a discount or Non-Rate Benefit under this plan, must the customer make a Prior Purchase-Based Commitment? (Y=Yes, N=No)	Text	N
OOR_Apply	Do purchases of DS1 or DS3 services in areas outside of your price cap study area(s) count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
OOR_PC_Apply	Do DS1 or DS3 purchases in areas where you are subject to price cap regulation and where pricing flexibility has not been granted count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
PH1_Apply	Do DS1 or DS3 purchases in areas where you have been granted Phase I Pricing Flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
PH2_Apply	Do DS1 or DS3 purchases in areas where you have been granted Phase II Pricing Flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
PBDS1_Apply	Do non-tariffed PBDS purchases by the customer count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
PBDS2_Apply	Do tariffed PBDS purchases by the customer count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
Other_Apply	Do purchases by the customer for services other than DS1s, DS3s, and PBDS count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	N
UNE_Cond	Is the discount or Non-Rate Benefit available under this plan conditioned on the customer limiting its purchase of UNEs, e.g., customer must keep its purchase of UNEs below a certain percentage of the customer’s total spend? (Y=Yes, N=No)	Text	N
Rev_Tot_2010	Total Revenue from the provision of Dedicated Services under this plan for 2010	Float	123,456
Rev_Tot_2012	Total Revenue from the provision of Dedicated Services under this plan for 2012	Float	123,456
Biz_Rational	What is the business justification for any Term or Volume Commitments associated with this plan?	Text	We have . . .
Tot_CustCount_2012	Total number of customers subscribed to this plan as of Dec. 31, 2012	Integer	434
DS1_CustCount_2012	Number of customers purchasing DS1s under this plan as of Dec. 31, 2012	Integer	434
DS3_CustCount_2012	Number of customers purchasing DS3s under this plan as of Dec. 31, 2012	Integer	434
PBDS_CustCount2012	Number of customers purchasing PBDS under this plan as of Dec. 31, 2012
DS1_CustCount_2012_CP	Number of customers that were Competitive Providers purchasing DS1s under this plan as of Dec. 31, 2012	Integer	434
DS3_CustCount_2012_CP	Number of customers that were Competitive Providers purchasing DS3s under this plan as of Dec. 31, 2012	Integer	434
PBDS_CustCount_2012_CP	Number of customers that were Competitive Providers purchasing PBDS under this plan as of Dec. 31, 2012	Integer	434
DS1_CustCount_2012_EUsers	Number of customers that were End Users purchasing DS1s under this plan as of Dec. 31, 2012	Integer	434
DS3_CustCount_2012_EUsers	Number of customers that were End Users purchasing DS3s under this plan as of Dec. 31, 2012	Integer	434
PBDS_CustCount_2012_EUsers	Number of customers that were End Users purchasing PBDS under this plan as of Dec. 31, 2012	Integer	434
CustCount_5orfewer	Were five or fewer customers, in total, subscribed to this plan as of Dec. 31, 2012? (Y=Yes, N=No)	Text	Y
CustCount_New	If Yes, indicate the number of subscribers to this plan that were new customers (as opposed to an existing or prior customer) at the time they to subscribed this plan.	Integer	3
CustCount_Exist	For those subscribers to this plan that were existing or prior customers at the time they committed to purchasing services under this plan, explain how the purchase commitment made under this plan compares to the customer’s previous purchase commitment. For example, indicate what percentage of the previous purchase commitment, the new purchase commitment equals.	Text	The new commitment amounts to 50% of what the customer committed to previously.
Customer_Fail	Of those customers subscribed as of December 31, 2012, how many in 2012 failed to meet any Volume Commitment or Term Commitment required to retain a discount or Non-Rate Benefit they originally agreed to when entering into this plan?	Integer	30

Question II.B.13: Non-Tariffed Agreements

If you have a non-tariffed agreement covered by Question II.B.13, then you must identify each agreement in Table II.B.13 within the data container. If you do not have an agreement covered by Question II.B.13, then type “Not Applicable” in the Agreement field. You will receive an error message upon validation of the data container if you do not put any information into Table II.B.13.

Table II.B.13 Record Format for Non-Tariffed Agreements
Field Name	Description	Type	Example
Unique_ID	Sequential number	Integer	1
Agreement	Name of non-tariffed agreement	Text	PBDS Agreement with Local Fiber Incorporated
Parties	Parties to the agreement	Text	ILEC Company and Local Fiber Inc.
Effective_Date	The beginning date of the time period covered by the agreement	Date	1/15/10
End_Date	The ending date of the time period covered by the agreement	Date	12/31/12
Summary	Summary of relevant provisions	Text	Requires the purchase of . . .

QUESTIONS DIRECTED AT ENTITIES PROVIDING BEST EFFORTS

Question II.C.1: Census Blocks and Price Lists for 2010 and 2012

You must separately upload all documents (e.g., Word, Excel, .pdf) responding to this question through the Special Access Web Portal; do not include these documents in the data container.

If the State Broadband Initiative (SBI) data previously submitted accurately and completely identifies the areas in which you offered Best Efforts Business Broadband Internet Access Services as of December 31, 2010 and as of December 31, 2012, then provide the requisite certification and identify the FRN(s) for the entities that reported the information as part of the SBI program.

If not, then identify, on a granular level (ideally, at the census block level), the geographic areas in which Best Efforts Business Broadband Internet Access Service was offered as of December 31, 2010 and as of December 31, 2012. If the data are not submitted at the census block level, identify the geography at which they are submitted, e.g., ZIP code, MSA, county, etc.

Separate from the SBI data, you must submit a price list for the Best Efforts Business Broadband Internet Access Services that you offer within your footprint as of December 31, 2010 and as of December 31, 2012. To the extent that prices vary across your service area, identify the nature of such variation, e.g., variations by region or speed tier.

The Special Access Web Portal contains two areas for uploading documents for this question. One is for uploading the “Confidential” versions of the documents where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” versions of the documents noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Below is a suggested template for formatting records in response to this question. You are not required to format your information in this manner.

Suggested Record Format Template for Responding to Question II.C.1.c-d Part 1 Best Efforts Business Broadband Internet Access Services
Field Name	Description	Type	Example
DBA Name	Name of the entity customers could contact to purchase service in this block with the characteristics below.	Text	Cable Town
Census_Block	As defined by US Census Bureau; 15 digit FIPS code	Text	060290057001136
Transtech	Category of technology for the provision of Internet access service (see Codes below)	Integer	41
Maxaddown	Maximum advertised download speed in Mbps available in the census block	Float	9
Maxaddup	Maximum advertised upload speed in Mbps offered with the above maximum advertised downstream speed	Float	0.768
Year	Year: 2010 or 2012	Date	2010

Census_Block – Each census block must be identified using the 2010 block identifier from the 2010 TIGER/Line Block State-based Shapefile or Block County-based Shapefile. The block identifier is a concatenation of Census 2010 state FIPS code, Census 2010 county FIPS code, Census 2010 census tract code and Census 2010 tabulation block number. Please see the 2010 TIGER/Line Shapefiles Technical Documentation, Chapter 5, Part 5.2 at http://www.census.gov/geo/maps-data/data/pdfs/tiger/tgrshp2010/TGRSHP10SF1CH5.pdf for more information.

Any variation in Census_Block, DBA Name, or technology of transmission (Transtech) necessitates the creation of a new record. For example, if a respondent indicates that broadband service is available in a particular census block via two technologies, then the data must contain two records for that census block. Records must be unique by Block, DBA Name, and Transtech.

Transtech – For reporting in the Transtech data field, report the technology used by the portion of the connection that would terminate at the end-user location. If different technologies could be used in the two directions of information transfer (“downstream” and “upstream”), report the connection in the technology category for the downstream direction. The Transtech field must be entered as an integer based on the following reference.

Technology of Transmission Codes
Code	Description
10	Asymmetric xDSL
20	Symmetric xDSL
30	Other Copper Wire
40	Cable Modem - DOCSIS 3.0
41	Cable Modem - Other
50	Optical Carrier/Fiber to the End User
60	Satellite
70	Terrestrial Fixed - Unlicensed
71	Terrestrial Fixed - Licensed
80	Terrestrial Mobile Wireless
90	Electric Power Line
0	Other

Suggested Record Format Template for Responding to Question II.C.1.c-d Part 2 Best Efforts Business Broadband Internet Access Services
Field Name	Description	Type	Example
County_ID	5-digit FIPS code for the state and county or equivalent entity.	Text	01121
Sum_Bandwidth	Indicate the sum bandwidth category for which you are reporting prices offered in this range. Enter “A” for sum bandwidth equal to or greater than 3 Mbps but less than or equal to 6 Mbps, enter “B” for bandwidth greater than 6 Mbps but less than or equal to 20 Mbps, enter “C” for bandwidth greater than 20 Mbps but less than or equal to 50 Mbps, enter “D” for bandwidth greater than 50 Mbps but less than or equal to 200 Mbps, and enter “E” for bandwidth greater than 200 Mbps	Text	A
Min_Price_Range	Enter the minimum price offered for the available Best Efforts Business Broadband Internet Access Services in the reported bandwidth tier	Float	9.99
Max_Price_Range	Enter the maximum price offered for the available Best Efforts Business Broadband Internet Access Services in the reported bandwidth tier	Float	29.99
Price_Territory	Indicate geographic territory where you offered the reported price range, e.g., nationwide, certain regions, certain states, etc.	Text	Nationwide
Year	Enter “2010” if the reported price range is for the year 2010 and enter “2012” if the reported price range is for the year 2012	Integer	2012

County_ID – Each county or equivalent entity must be identified using the 2010 county identifier from the 2010 TIGER/Line County and Equivalent Entity Shapefile. The county identifier is a concatenation of Census 2010 state FIPS code and the Census 2010 county FIPS code. See 2010 TIGER/Line Shapefiles Technical Documentation, Chapter 5, Part 5.7 at http://www.census.gov/geo/maps-data/data/pdfs/tiger/tgrshp2010/TGRSHP10SF1CH5.pdf for more information.
Sum_Bandwidth – To calculate the Sum_Bandwidth, add the advertised downstream and upstream bandwidth for the Best Efforts Business Broadband Internet Access Service offered. At a minimum, the Best Efforts Business Broadband Internet Access Service offered and reported must have a bandwidth connection of at least 1.5 Mbps in both directions (upstream/downstream).
Min_Price_Range – Determine the minimum price offered by looking at the prices for all available Best Efforts Business Broadband Internet Access Services you offer within the reported Sum_Bandwidth range and selecting the lowest price offered across those services.
Max_Price_Range – Determine the maximum price offered by looking at the prices for all available Best Efforts Business Broadband Internet Access Services you offer within the reported Sum_Bandwidth range and selecting the highest price offered across those services.

QUESTIONS DIRECTED AT ALL PROVIDERS

If the filer has both ILEC and Competitive Provider operations, identify the applicable operating unit when responding to these questions. For example, if discussing promotional and advertising strategies, indicate whether the strategies pertain to your ILEC or Competitive Provider operations or both.

Question II.D.1: Short Term and Long-Range Strategies

Question II.D.2: Location of Recorded Policies

You must upload a .pdf text searchable (not a picture/image) document responding to these questions through the Special Access Web Portal in the “Essay Questions – File Upload” section; you will not include these documents in the data container.

The web portal contains two areas for uploading documents for each question. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

QUESTIONS DIRECTED AT PURCHASERS THAT ARE MOBILE WIRELESS SERVICE PROVIDERS

Facilities-based mobile wireless service providers purchasing Dedicated Service in price cap areas are required to answer these questions.

Question II.E.1: Total Number of Cell Sites

Table II.E.1 Record Format for Total Cell Sites
Field Name	Description	Type	Example
Provider_Name	Name of mobile wireless service provider	Text	Local Fiber Incorporated
Total_Number	Total number of cell sites on network	Float	100

Question II.E.2: Cell Site Locations

Provide, for each cell site on your network, the following information:

Table II.E.2 Record Format for Cell Sites by Location
Field Name	Description	Type	Example
Location_ID	Sequential location number	Integer	1
Year	Indicator of the calendar year of the data	Integer	2010
Street_address	Actual situs for the cell site (i.e., land where cell site is located) if the cell site is located in or on a building	Text	445 Twelfth St SW
Other_address	If cell site does not have a street address, provide description of location	Text	500 yards N of I35 and SR270 intersection
City	City of the cell site	Text	Washington
State	Two-letter state postal abbreviation of the cell site	Text	DC
ZIP	5-digit ZIP code (with leading zeros) of the cell site	Text	20554
ZIP4	4-digit add-on code (with leading zeros) of the cell site	Text	0000
Lat	Latitude	Float	38.8835
Long	Longitude	Float	-77.0280
CLLI	Telcordia-specified eight-character CLLI of the ILEC wire center that serves the cell site	Alphanumeric	WASHDCSW
Loc_type	Indicate whether cell site is 1=in or on a building; 2=on other man-made structure, e.g., water tower; 3=a free-standing cell site	Integer	1
CBDS_Bandwidth	If a DS1, DS3, DS1-UNE, or DS3-UNE, indicate the one-direction bandwidth of the circuit in Mbps.	Float	1.544
PBDS_Bandwidth	If the cell site is served by a PBDS, indicate the bandwidth of the circuit(s) in Mbps.	Float	10.000
FW_Bandwidth	If the cell site is served by a wireless Connection, indicate the bandwidth of the circuit(s) in Mbps.	Float	0
Provider	The name of the Provider(s) that supplies your Connection to the cell site.	Text	Verizon, XO
Self_prov_bw	If you self-provide a Connection to the cell site, indicate the provisioned bandwidth of the circuit in Mbps.	Float	0

Instructions for Cell Sites Record Format:

Leave cells blank in the case of data that is not applicable for that record.
The Location_ID field is a sequential integer ranging from 1 to the total number of locations. Records containing information about Connections to the same Location must be assigned the same Location_ID.
Address data fields must be space-delimited in standardized Postal Service form. See http://pe.usps.gov/cpim/ftp/pubs/Pub28/pub28.pdf.
Latitude and Longitude: You can derive the coordinate fields for the location address from a known geocoding platform like Bing maps, Google, Yahoo, batchgeo.com, Texas A&M Geoservices or other geocoding solution. Enter values in decimal degrees to the nearest ±0.0005, i.e., each coordinate must end in #.###0 or #.###5. Coordinates must be in the WGS84 or NAD83 geographic coordinate system.
For the CLLI code, enter the first eight digits of the CLLI code of the ILEC wire center serving the location.

Expenditures Information

Question II.E.3: Total Expenditures on Dedicated Services

Table II.E.3 Record Format for Expenditures on Dedicated Service
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service	Float	4321.00
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “CBDS” for CBDS expenditures and enter “PBDS” for PBDS expenditures	Text	CBDS
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012

Note: If there were no expenditures for a particular category or year, then report 0.

Question II.E.4: Expenditures with ILECs under Tariffs

Table II.E.4 Record Format for Expenditures with ILECs Pursuant to a Tariff
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service for the corresponding categorical breakdown	Float	5364821
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “DS1” for DS1 expenditures, enter “DS3” for DS3 expenditures, and enter “PBDS” for PBDS expenditures	Text	DS3
Agreement_Type	Enter the code for the appropriate contract type indicated in the question. The codes must be a letter from “a” to “h”. See instructions below the table for more information on the codes for Agreement_Type	Text	c
Avg_Discount_PPBC	If the Agreement_Type is coded as “f” or “h”, enter the average discount (in percentage terms) off the One Month Term Only Rate incorporated in the expenditures purchased under Tariff Plans (for code “f”) or Contract-Based Tariffs (for code “h”) that contained a Prior Purchase-Based Commitment. See the example in the question on how to calculate the average discount. If Agreement_Type is not coded as “f” or “h”, leave the field blank	Float	25
5orMore	If the Year field is 2012, what percentage of your expenditures was subject to a Term Commitment of five or more years?	Integer	45

Note: If there were no expenditures for a particular category or year, then report 0.

Use the following codes for the Agreement_Type variable. Enter “a” for expenditures on ALL purchases; enter “b” for expenditures on purchases at One Month Term Only Rates; enter “c” for expenditures purchased under Tariff Plans; enter “d” for expenditures purchased under Contract-Based Tariffs; enter “e” for expenditures purchased under Tariff Plans that contained a Term Commitment but not a Volume Commitment; enter “f” for expenditures purchased under Tariff Plans that contained a Prior Purchase-Based Commitment; enter “g” for expenditures purchased under Contract-Based Tariffs that contained a Term Commitment but not a Volume Commitment; and enter “h” for expenditures purchased under Contract-Based Tariffs that contained a Prior Purchase-Based Commitment.

5orMore: Provide the percentage of your expenditures in 2012 that were subject to a Term Commitment of five or more years. If the Year field reported is 2010, then leave this field blank.

Question II.E.5: Expenditures with Competitive Providers under Tariffs

Table II.E.5 Record Format for Expenditures with Competitive Providers Pursuant to a Tariff
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service for the corresponding categorical breakdown	Float	5364821
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “DS1” for DS1 expenditures, enter “DS3” for DS3 expenditures, and enter “PBDS” for PBDS expenditures	Text	DS3
Agreement_Type	Enter the code for the appropriate contract type indicated in the question. The codes must be a letter from “a” to “d”. See instructions below the table for more information on the codes for Agreement_Type	Text	c
Avg_Discount_PPBC	If the Agreement_Type is coded as “d”, enter the average discount (in percentage terms) off the One Month Term Only Rate incorporated in the expenditures purchased under Tariffs that contained a Prior Purchase-Based Commitment. See the example in the question on how to calculate the average discount. If Agreement_Type is not coded as “d”, leave the field blank	Float	25
5orMore	If the Year field is 2012, what percentage of your expenditures was subject to a Term Commitment of five or more years?	Integer	45

Note: If there were no expenditures for a particular category or year, then report 0.

5orMore: Provide the percentage of your expenditures in 2012 that were subject to a Term Commitment of five or more years. If the Year field reported is 2010, then leave this field blank.

Question II.E.6: Expenditures with ILECs and Competitive Providers Pursuant to Non-Tariffs

Table II.E.6 Record Format for Expenditures with ILECs and Competitive Providers Pursuant to Non-Tariffed Agreement
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service for the corresponding categorical breakdown	Float	5364821
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “DS1” for DS1 expenditures, enter “DS3” for DS3 expenditures, and enter “PBDS” for PBDS expenditures	Text	DS3
Agreement_Type	Enter the code for the appropriate contract type indicated in the question. The codes must be a letter from “a” to “d”. See instructions below the table for more information on the codes for Agreement_Type	Text	c
Avg_Discount_PPBC	If the Agreement_Type is coded as “d”, enter the average discount (in percentage terms) off the non-discounted rate incorporated in the expenditures purchased under non-tariffed agreements that contained a Prior Purchase-Based Commitment. See the example in the question on how to calculate the average discount. If Agreement_Type is not coded as “d”, leave the field blank	Float	25

Note: If there were no expenditures for a particular category or year, then report 0.

Use the following codes for the Agreement_Type variable. Enter “a” for expenditures on ALL purchases; enter “b” for expenditures purchased at non-discounted rates; enter “c” for expenditures purchased under a non-tariffed agreement that contained a Term Commitment but not a Volume Commitment; enter “d” for expenditures purchased under a non-tariffed agreement that contained a Prior Purchase-Based Commitment.

Question II.E.7: Expenditures under Tariffs for PBDS

Table II.E.7 Record Format for Expenditures on PBDS Purchased Pursuant to a Tariff by Bandwidth Category
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Tariffed PBDS service	Float	4,321.00
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Bandwidth	Indicate the bandwidth category for which the expenditures are reported. Enter “A” for bandwidth less than or equal to 1.5 Mbps, enter “B” for bandwidth greater than 1.5 Mbps but less than or equal to 50 Mbps, enter “C” for bandwidth greater than 50 Mbps but less than or equal to 100 Mbps, enter “D” for bandwidth greater than 100 Mbps but less than or equal to 1 Gbps, and enter “E” for bandwidth greater than 1 Gbps	Text	B
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012

Question II.E.8: Expenditures under Non-Tariffs for PBDS

Table II.E.8 Record Format for Expenditures on PBDS Pursuant to Non-Tariff Agreement
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on non-Tariffed PBDS service	Float	4,321.00
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Bandwidth	Indicate the bandwidth category for which the expenditures are reported. Enter “A” for bandwidth less than or equal to 1.5 Mbps, enter “B” for bandwidth greater than 1.5 Mbps but less than or equal to 50 Mbps, enter “C” for bandwidth greater than 50 Mbps but less than or equal to 100 Mbps, enter “D” for bandwidth greater than 100 Mbps but less than or equal to 1 Gbps, and enter “E” for bandwidth greater than 1 Gbps	Text	B
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012

Terms and Conditions Information

Question II.E.9: Terms and Conditions Constraints

Question II.E.10: Changing Transport Providers

Question II.E.11: Purchases Solely for the Purpose of Meeting a Prior Purchase-Based Commitment

Question II.E.12: Switching Providers

Question II.E.13: Paying One Month Term Only Rates

The web portal contains two areas for uploading documents for each question. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Additional Note for Questions II.E.9-11. These questions are intended to give you an opportunity to discuss any alleged concerns that you are having with terms and conditions associated with the purchase of Dedicated Services or with changing Providers. If you do not need, or want, to provide a response, e.g., you do not have any alleged concerns with terms and conditions, then you can simply respond stating as such.

Additional Note for Question II.E.12. The purpose of this question is to assess the frequency of switching Providers for End-User Channel Terminations at as granular a geographic level as possible. Respondents may define their own geographic areas. Given the level of detail required in other parts of the data collection, respondents need only provide switching history in five geographic areas of their choice or more. Respondents may provide switching history for less than five years if they do not keep such information in the regular course of business.

Additional Note for Question II.E.13. The purpose of this question is to understand the economic impact of paying One Month Term Only Rates on your business and consumers. Given the level of detail required in other parts of the data collection, respondents may provide information over a shorter timeframe. Alternatively, respondents who do not need or want to provide a response, e.g., you do not have any alleged concerns with paying One Month Term Only Rates, then you can simply respond stating as such.

Question II.E.14: Tariffs under which you Purchase Service

Table II.E.14 Record Format for Tariffs under which you Purchase Service
Field Name	Description	Type	Example
Tar_Plan	Plan is a Tariff Plan (Y=Yes, N=No)	Text	Y
Tariff_Name	Name of Tariff Plan	Text	Regional Volume Discount Plan
TP_Provider	The Tariff Plan Provider name	Text	ABC Company
TP_Tariff_Number	The Tariff Plan Name and Section Number	Text	ABC Tariff FCC No. 2 § 7.4.15
CBT_Plan	Plan is a Contract-Based Tariff (Y=Yes, N=No)	Text	N
CBT_Name	Name of Contract-Based Tariff plan	Text	Regional Volume Discount Plan
CBT_Provider	The Contract-Based Tariff Provider name	Text	ABC Company
CBT_Tariff_Number	The Contract-Based Tariff Name and Section Number	Text	ABC Tariff FCC No. 2 § 7.4.15
Tariff_Type	Interstate (Inter) or Intrastate (Intra)	Text	Inter
Contains_Term	Contains Term Commitments (Y=Yes, N=No)	Text	Y
Contains_Vol	Contains Volume Commitments (Y=Yes, N=No)	Text	Y
Contains_NonR	Contains Non-Rate Benefits (Y=Yes, N=No)	Text	N
NonRate	If the plan contains Non-Rate Benefits, identify the Non-Rate Benefits that were relevant to your decision to purchase services under this plan.	Text	Plan allows for circuit portability . . .
Tariff_DS1	Does this plan apply to the purchase of DS1s? (Y=Yes, N=No)	Text	Y
Tariff_DS3	Does this plan apply to the purchase of DS3s? (Y=Yes, N=No)	Text	Y
Tariff_PBDS	Does this plan apply to the purchase of PBDS? (Y=Yes, N=No)	Text	N
Tariff_Other	Does this plan apply to the purchase of other services? (Y=Yes, N=No)	Text	N
Geo_DS1	In what geographic areas do you purchase DS1s under this plan?	Text	California
Geo_DS3	In what geographic areas do you purchase DS3s under this plan?	Text	Texas
Geo_PBDS	In what geographic areas do you purchase PBDS under this plan?	Text	Oklahoma
Geo_Other	In what geographic areas do you purchase other services under this plan?	Text	Kansas
Prior_P	To receive a discount or Non-Rate Benefit under this plan, does your company make a Prior Purchase-Based Commitment? (Y=Yes, N=No)	Text	Y
Outside_Area	If this is an ILEC plan, do DS1, DS3, or tariffed PBDS purchases your company makes outside the study area(s) of the ILEC count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
Outside_Area_Yes	If yes, in what geographic areas outside the study area(s) of the ILEC, do you purchase these DS1s, DS3s, and/or tariffed PBDS?	Text	Southern California
Outside_Area_Yes_Diff	Of the geographic areas identified, in which of those areas would your company have purchased from a different Provider, if at all, had it not been for the discounts or Non-Rate Benefits received under this plan?	Text	Southern California
Outside_Area_Yes_Provider	Name of Provider(s) in the geographic area identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_Price_Cap	If this is an ILEC plan, do DS1s, DS3s, and/or tariffed PBDS purchases your company makes from the ILEC in price cap areas where the Commission has not granted the ILEC pricing flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Price_Cap_Vol	If Yes, then identify the price cap areas where you purchase DS1s, DS3s, and/or tariffed PBDS that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Texas
ILEC_Price_Flex1	If this is an ILEC plan, do DS1s, DS3s, and/or tariffed PBDS purchases your company makes from the ILEC in areas where the Commission has granted the ILEC Phase I Pricing Flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Price_Flex1_Vol	If Yes, in what geographic areas subject to pricing flexibility do you purchase DS1s, DS3s, and/or tariffed PBDS that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan?	Text	Dallas MSA
ILEC_Price_Flex1_Diff	Of the geographic areas identified, in which of those areas would your company have purchased from a different Provider, if at all, had it not been for the discounts or Non-Rate Benefits received under this plan?	Text	Southern California
ILEC_Price_Flex1_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_Price_Flex2	If this is an ILEC plan, do DS1s, DS3s, and/or tariffed PBDS purchases your company makes from the ILEC in areas where the Commission has granted the ILEC Phase II Pricing Flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Price_Flex2_Vol	If Yes, in what geographic areas subject to pricing flexibility do you purchase DS1s, DS3s, and/or tariffed PBDS that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan?	Text	Dallas MSA
ILEC_Price_Flex2_Diff	Of the geographic areas identified, in which of those areas would your company have purchased from a different Provider, if at all, had it not been for the discounts or Non-Rate Benefits received under this plan?	Text	Southern California
ILEC_Price_Flex2_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_PBDS	If an ILEC plan, do non-tariffed PBDS purchases you make from this ILEC count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_PBDS_Vol	If Yes, in what geographic areas do you purchase non-tariffed PBDS that counts towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Oklahoma City, OK
ILEC_PBDS_Diff	Of the geographic areas identified, in which of those areas would your company have purchased non-tariffed PBDS from a different Provider, if at all, had it not been for the requirements of the plan?	Text	Oklahoma City, OK
ILEC_PBDS_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_Other	If this is an ILEC plan, do purchases you make for services other than DS1s, DS3s, and PBDS from this ILEC count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? ((Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Other_Service	If Yes, identify the other services purchased that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Cloud computing
ILEC_Other_Geo	If Yes, identify the geographic areas where you purchase these other services that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Little Rock, AR
ILEC_Other_Diff	Of the geographic areas identified, in which of those areas would your company have purchased those other services from a different Provider, had it not been for the requirements of the plan? In your response, indicate whether the Provider that you would have purchased from has Connections serving that geographic area.	Text	Little Rock, AR
ILEC_Other_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
Limiting_Purchase	Is the discount or Non-Rate Benefit available under this plan conditioned on the customer limiting its purchase of UNEs, e.g., the customer must keep its purchase of UNEs below a certain percentage of the customer’s total spend? If yes, then provide additional details about the condition.	Text	Yes, to obtain the discount our company must . . .

Question II.E.15: Non-Tariffed Agreements

If you have a non-tariffed agreement covered by Question II.E.15, then you must identify each agreement in Table II.E.15 within the data container. If you do not have an agreement covered by Question II.E.15, then type “Not Applicable” in the Agreement field. You will receive an error message upon validation of the data container if you do not put any information into Table II.E.15.

Table II.E.15 Record Format for Non-Tariffed Agreements
Field Name	Description	Type	Example
Unique_ID	Sequential number	Integer	1
Agreement	Name of non-tariffed agreement	Text	PBDS Agreement with Local Fiber Incorporated
Parties	Parties to the agreement	Text	ILEC Company and Local Fiber Inc.
Effective_Date	The beginning date of the time period covered by the agreement	Date	1/15/10
End_Date	The ending date of the time period covered by the agreement	Date	12/31/12
Summary	Summary of relevant provisions	Text	Requires the purchase of . . .

QUESTIONS DIRECTED AT OTHER PURCHASERS

Question II.F.1: Principal Nature of Business

Table II.F.1 Record Format for Purchaser’s Business
Field Name	Description	Type	Example
Purchaser_Name	Name of Purchaser	Text	Local Fiber Inc.
Biz_Nature	Principal nature of Purchaser’s business	Text	CLEC

Expenditures Information

Question II.F.2: Total Expenditures on Dedicated Services

Table II.F.2 Record Format for Expenditures on Dedicated Service
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service	Float	4321.00
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “CBDS” for CBDS expenditures and enter “PBDS” for PBDS expenditures	Text	CBDS
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012

Note: If there were no expenditures for a particular category or year, then report 0.

Question II.F.3: Expenditures with ILECs under Tariffs

Table II.F.3 Record Format for Expenditures with ILECs Pursuant to a Tariff
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service for the corresponding categorical breakdown	Float	5364821
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “DS1” for DS1 expenditures, enter “DS3” for DS3 expenditures, and enter “PBDS” for PBDS expenditures	Text	DS3
Agreement_Type	Enter the code for the appropriate contract type indicated in the question. The codes must be a letter from “a” to “h”. See instructions below the table for more information on the codes for Agreement_Type	Text	c
Avg_Discount_PPBC	If the Agreement_Type is coded as “f” or “h”, enter the average discount (in percentage terms) off the One Month Term Only Rate incorporated in the expenditures purchased under Tariff Plans (for code “f”) or Contract-Based Tariffs (for code “h”) that contained a Prior Purchase-Based Commitment. See the example in the question on how to calculate the average discount. If Agreement_Type is not coded as “f” or “h”, leave the field blank	Float	25
5orMore	If the Year field is 2012, what percentage of your expenditures was subject to a Term Commitment of five or more years?	Integer	45

Note: If there were no expenditures for a particular category or year, then report 0.

5orMore: Provide the percentage of your expenditures in 2012 that were subject to a Term Commitment of five or more years. If the Year field reported is 2010, then leave this field blank.

Question II.F.4: Expenditures with Competitive Providers under Tariffs

Table II.F.4 Record Format for Expenditures with Competitive Providers Pursuant to a Tariff
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service for the corresponding categorical breakdown	Float	5364821
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “DS1” for DS1 expenditures, enter “DS3” for DS3 expenditures, and enter “PBDS” for PBDS expenditures	Text	DS3
Agreement_Type	Enter the code for the appropriate contract type indicated in the question. The codes must be a letter from “a” to “d”. See instructions below the table for more information on the codes for Agreement_Type	Text	c
Avg_Discount_PPBC	If the Agreement_Type is coded as “d”, enter the average discount (in percentage terms) off the One Month Term Only Rate incorporated in the expenditures purchased under Tariffs that contained a Prior Purchase-Based Commitment. See the example in the question on how to calculate the average discount. If Agreement_Type is not coded as “d”, leave the field blank	Float	25
5orMore	If the Year field is 2012, what percentage of your expenditures was subject to a Term Commitment of five or more years?	Integer	45

Note: If there were no expenditures for a particular category or year, then report 0.

5orMore: Provide the percentage of your expenditures in 2012 that were subject to a Term Commitment of five or more years. If the Year field reported is 2010, then leave this field blank.

Question II.F.5: Expenditures with ILECs and Competitive Providers Pursuant to Non-Tariffs

Table II.F.5 Record Format for Expenditures with ILECs and Competitive Providers Pursuant to Non-Tariffed Agreement
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Dedicated Service for the corresponding categorical breakdown	Float	5364821
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Service_Type	Indicate the service type category for which the expenditures are reported. Enter “DS1” for DS1 expenditures, enter “DS3” for DS3 expenditures, and enter “PBDS” for PBDS expenditures	Text	DS3
Agreement_Type	Enter the code for the appropriate contract type indicated in the question. The codes must be a letter from “a” to “d”. See instructions below the table for more information on the codes for Agreement_Type	Text	c
Avg_Discount_PPBC	If the Agreement_Type is coded as “d”, enter the average discount (in percentage terms) off the non-discounted rate incorporated in the expenditures purchased under non-tariffed agreements that contained a Prior Purchase-Based Commitment. See the example in the question on how to calculate the average discount. If Agreement_Type is not coded as “d”, leave the field blank	Float	25

Note: If there were no expenditures for a particular category or year, then report 0.

Question II.F.6: Expenditures under Tariffs for PBDS

Table II.F.6 Record Format for Expenditures on PBDS Purchased Pursuant to a Tariff by Bandwidth Category
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on Tariffed PBDS service	Float	4,321.00
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Bandwidth	Indicate the bandwidth category for which the expenditures are reported. Enter “A” for bandwidth less than or equal to 1.5 Mbps, enter “B” for bandwidth greater than 1.5 Mbps but less than or equal to 50 Mbps, enter “C” for bandwidth greater than 50 Mbps but less than or equal to 100 Mbps, enter “D” for bandwidth greater than 100 Mbps but less than or equal to 1 Gbps, and enter “E” for bandwidth greater than 1 Gbps	Text	B
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012

Question II.F.7: Expenditures under Non-Tariffs for PBDS

Table II.F.7 Record Format for Expenditures on PBDS Pursuant to Non-Tariff Agreement
Field Name	Description	Type	Example
Expenditures	Enter the dollar value of expenditures on non-Tariffed PBDS service	Float	4,321.00
Provider_Type	Enter 0 if the reported expenditures are for purchases from ILECs and enter 1 if the reported expenditures are for purchases from Competitive Providers	Binary	0
Bandwidth	Indicate the bandwidth category for which the expenditures are reported. Enter “A” for bandwidth less than or equal to 1.5 Mbps, enter “B” for bandwidth greater than 1.5 Mbps but less than or equal to 50 Mbps, enter “C” for bandwidth greater than 50 Mbps but less than or equal to 100 Mbps, enter “D” for bandwidth greater than 100 Mbps but less than or equal to 1 Gbps, and enter “E” for bandwidth greater than 1 Gbps	Text	B
Year	Enter “2010” if the reported expenditures are for the year 2010 and enter “2012” if the reported expenditures are for the year 2012	Integer	2012

Terms and Conditions Information

Question II.F.8: Terms and Conditions Constraints

Question II.F.9: Changing Transport Providers

Question II.F.10: Purchases Solely for the Purpose of Meeting a Prior Purchase-Based Commitment

Question II.F.11: Switching Providers

Question II.F.12: Paying One Month Term Only Rates

The web portal contains two areas for uploading documents for each question. One is for uploading the “Confidential” version of the document where you will indicate information deemed Confidential and redact information that is Highly Confidential based on the Protective Order issued for the data collection. The second area is for uploading the “Highly Confidential” version of the document noting both Confidential and Highly Confidential information without any redactions. You must upload at least one document in each area or you will receive an error message during the submission process. If the document does not contain Confidential or Highly Confidential information, e.g., all information is publicly available, then upload the document in each area without the relevant Confidential/Highly Confidential notations or redactions in the case of the Confidential upload area.

Additional Note for Questions II.F.8-10. These questions are intended to give you an opportunity to discuss any alleged concerns that you are having with terms and conditions associated with the purchase of Dedicated Services or with changing Providers. If you do not need, or want, to provide a response, e.g., you do not have any alleged concerns with terms and conditions, then you can simply respond stating as such.

Additional Note for Question II.F.11. The purpose of this question is to assess the frequency of switching Providers for End-User Channel Terminations at as granular a geographic level as possible. Respondents may define their own geographic areas. Given the level of detail required in other parts of the data collection, respondents need only provide switching history in five geographic areas of their choice or more. Respondents may provide switching history for less than five years if they do not keep such information in the regular course of business.

Additional Note for Question II.F.12. The purpose of this question is to understand the economic impact of paying One Month Term Only Rates on your business and consumers. Given the level of detail required in other parts of the data collection, respondents may provide information over a shorter timeframe. Alternatively, respondents who do not need or want to provide a response, e.g., you do not have any alleged concerns with the terms and conditions, then you can simply respond stating as such.

Question II.F.13: Tariffs under which you Purchase Service

Table II.F.13 Record Format for Tariffs under which you Purchase Service
Field Name	Description	Type	Example
Tar_Plan	Plan is a Tariff Plan (Y=Yes, N=No)	Text	Y
Tariff_Name	Name of Tariff Plan	Text	Regional Volume Discount Plan
TP_Provider	The Tariff Plan Provider name	Text	ABC Company
TP_Tariff_Number	The Tariff Plan Name and Section Number	Text	ABC Tariff FCC No. 2 § 7.4.15
CBT_Plan	Plan is a Contract-Based Tariff (Y=Yes, N=No)	Text	N
CBT_Name	Name of Contract-Based Tariff plan	Text	Regional Volume Discount Plan
CBT_Provider	The Contract-Based Tariff Provider name	Text	ABC Company
CBT_Tariff_Number	The Contract-Based Tariff Name and Section Number	Text	ABC Tariff FCC No. 2 § 7.4.15
Tariff_Type	Interstate (Inter) or Intrastate (Intra)	Text	Inter
Contains_Term	Contains Term Commitments (Y=Yes, N=No)	Text	Y
Contains_Vol	Contains Volume Commitments (Y=Yes, N=No)	Text	Y
Contains_NonR	Contains Non-Rate Benefits (Y=Yes, N=No)	Text	N
NonRate	If the plan contains Non-Rate Benefits, identify the Non-Rate Benefits that were relevant to your decision to purchase services under this plan.	Text	Plan allows for circuit portability . . .
Tariff_DS1	Does this plan apply to the purchase of DS1s? (Y=Yes, N=No)	Text	Y
Tariff_DS3	Does this plan apply to the purchase of DS3s? (Y=Yes, N=No)	Text	Y
Tariff_PBDS	Does this plan apply to the purchase of PBDS? (Y=Yes, N=No)	Text	N
Tariff_Other	Does this plan apply to the purchase of other services? (Y=Yes, N=No)	Text	N
Geo_DS1	In what geographic areas do you purchase DS1s under this plan?	Text	California
Geo_DS3	In what geographic areas do you purchase DS3s under this plan?	Text	Texas
Geo_PBDS	In what geographic areas do you purchase PBDS under this plan?	Text	Oklahoma
Geo_Other	In what geographic areas do you purchase other services under this plan?	Text	Kansas
Prior_P	To receive a discount or Non-Rate Benefit under this plan, does your company make a Prior Purchase-Based Commitment? (Y=Yes, N=No)	Text	Y
Outside_Area	If this is an ILEC plan, do DS1, DS3, or tariffed PBDS purchases your company makes outside the study area(s) of the ILEC count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
Outside_Area_Yes	If yes, in what geographic areas outside the study area(s) of the ILEC, do you purchase these DS1s, DS3s, and/or tariffed PBDS?	Text	Southern California
Outside_Area_Yes_Diff	Of the geographic areas identified, in which of those areas would your company have purchased from a different Provider, if at all, had it not been for the discounts or Non-Rate Benefits received under this plan?	Text	Southern California
Outside_Area_Yes_Provider	Name of Provider(s) in the geographic area identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_Price_Cap	If this is an ILEC plan, do DS1s, DS3s, and/or tariffed PBDS purchases your company makes from the ILEC in price cap areas where the Commission has not granted the ILEC pricing flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Price_Cap_Vol	If Yes, then identify the price cap areas where you purchase DS1s, DS3s, and/or tariffed PBDS that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Texas
ILEC_Price_Flex1	If this is an ILEC plan, do DS1s, DS3s, and/or tariffed PBDS purchases your company makes from the ILEC in areas where the Commission has granted the ILEC Phase I Pricing Flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Price_Flex1_Vol	If Yes, in what geographic areas subject to pricing flexibility do you purchase DS1s, DS3s, and/or tariffed PBDS that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan?	Text	Dallas MSA
ILEC_Price_Flex1_Diff	Of the geographic areas identified, in which of those areas would your company have purchased from a different Provider, if at all, had it not been for the discounts or Non-Rate Benefits received under this plan?	Text	Southern California
ILEC_Price_Flex1_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_Price_Flex2	If this is an ILEC plan, do DS1s, DS3s, and/or tariffed PBDS purchases your company makes from the ILEC in areas where the Commission has granted the ILEC Phase II Pricing Flexibility count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Price_Flex2_Vol	If Yes, in what geographic areas subject to pricing flexibility do you purchase DS1s, DS3s, and/or tariffed PBDS that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan?	Text	Dallas MSA
ILEC_Price_Flex2_Diff	Of the geographic areas identified, in which of those areas would your company have purchased from a different Provider, if at all, had it not been for the discounts or Non-Rate Benefits received under this plan?	Text	Southern California
ILEC_Price_Flex2_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_PBDS	If an ILEC plan, do non-tariffed PBDS purchases you make from this ILEC count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? (Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_PBDS_Vol	If Yes, in what geographic areas do you purchase non-tariffed PBDS that counts towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Oklahoma City, OK
ILEC_PBDS_Diff	Of the geographic areas identified, in which of those areas would your company have purchased non-tariffed PBDS from a different Provider, if at all, had it not been for the requirements of the plan?	Text	Oklahoma City, OK
ILEC_PBDS_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
ILEC_Other	If this is an ILEC plan, do purchases you make for services other than DS1s, DS3s, and PBDS from this ILEC count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan? ((Y=Yes, N=No, NA=Not Applicable)	Text	Y
ILEC_Other_Service	If Yes, identify the other services purchased that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Cloud computing
ILEC_Other_Geo	If Yes, identify the geographic areas where you purchase these other services that count towards meeting any Volume Commitment to receive a discount or Non-Rate Benefit under this plan.	Text	Little Rock, AR
ILEC_Other_Diff	Of the geographic areas identified, in which of those areas would your company have purchased those other services from a different Provider, had it not been for the requirements of the plan? In your response, indicate whether the Provider that you would have purchased from has Connections serving that geographic area.	Text	Little Rock, AR
ILEC_Other_Provider	Name of Provider(s) in the geographic areas identified above you would have purchased from had it not been for the discounts or Non-Rate Benefits received under this plan.	Text	ABC Co.
Limiting_Purchase	Is the discount or Non-Rate Benefit available under this plan conditioned on the customer limiting its purchase of UNEs, e.g., the customer must keep its purchase of UNEs below a certain percentage of the customer’s total spend? If yes, then provide additional details about the condition.	Text	Yes, to obtain the discount our company must . . .

Question II.F.14: Non-Tariffed Agreements

If you have a non-tariffed agreement covered by Question II.F.14, then you must identify each agreement in Table II.F.14 within the data container. If you do not have an agreement covered by Question II.F.14, then type “Not Applicable” in the Agreement field. You will receive an error message upon validation of the data container if you do not put any information into Table II.F.14.

Table II.F.14 Record Format for Non-Tariffed Agreements
Field Name	Description	Type	Example
Unique_ID	Sequential number	Integer	1
Agreement	Name of non-tariffed agreement	Text	PBDS Agreement with Local Fiber Incorporated
Parties	Parties to the agreement	Text	ILEC Company and Local Fiber Inc.
Begin_Date	The beginning date of the time period covered by the agreement	Date	1/15/10
End_Date	The ending date of the time period covered by the agreement	Date	12/31/12
Summary	Summary of relevant provisions	Text	Requires the purchase of . . .

Question Directed at Non-Providers, Non-Purchasers, and Other Entities Not Covered by the Data Collection

Question II.G.1: Not Required to Submit Data

Entities that reported broadband connections to end users for 2012 in the FCC Form 477 are required to affirmatively indicate whether or not they are a Provider, a Purchaser, or an entity providing Best Efforts Business Broadband Internet Access Services to 15,000 or more customers or 1,500 or more business broadband customers in price cap areas. If you are “none of the above,” then you must electronically submit a certification, stating as such, where indicated in the Special Access Web Portal.

0 See Special Access for Price Cap Local Exchange Carriers, WC Docket No. 05-25; AT&T Corporation Petition for Rulemaking to Reform Regulation of Incumbent Local Exchange Carrier Rates for Interstate Special Access Services, WC Docket No. 05-25, RM-10593, Report and Order and Further Notice of Proposed Rulemaking, 27 FCC Rcd 16318 (2012) (Special Access Data Collection Order). For purposes of these Instructions, our use of the term “data” includes data and information.

0 See Special Access for Price Cap Local Exchange Carriers, WC Docket No. 05-25; AT&T Corporation Petition for Rulemaking to Reform Regulation of Incumbent Local Exchange Carrier Rates for Interstate Special Access Services, WC Docket No. 05-25, RM-10593, Order, DA 13-1909, App. B (WCB rel. Sept. 18, 2013) (Data Collection Implementation Order).

0 See Special Access Data Collection Order, 27 FCC Rcd at 16341, para. 56.

0 A map depicting the study areas where an incumbent local exchange carrier (ILEC) subject to price cap regulation is located is available on the FCC’s website. See Map: Regulatory Type at the Holding Company Level by Study Area, FCC, http://www.fcc.gov/maps/regulatory-type-holding-company-level-study-area (last visited Sept. 9, 2013). The Commission is currently updating this map based on a collection of study area boundaries. If the new study area boundary data are not available to respondents in time for them to take into account in formulating responses to the special access data collection, we will consider reliance on the currently available study area boundary data to be reasonable.

0 Special Access Data Collection Order, 27 FCC Rcd at 16327, para. 20; see also Instructions at 3-4 (discussing “Entities Specifically Excluded from the Data Collection”).

0 Special Access Data Collection Order, 27 FCC Rcd at 16327-28, para. 22 n.52 (“For purposes of this exemption, the number of customers and business broadband customers shall be determined as of the date of release of this Report and Order.”).

0 47 U.S.C. § 503(b)(2); 47 C.F.R. § 1.80(b);Amendment of Section 1.80(B) of the Commission's Rules, Adjustment of Civil Monetary Penalties to Reflect Inflation, Order, DA 13-1615 (Enf. Bureau rel. Aug. 2, 2013).

0 For example, an entity holding an earth station license issued under Part 25 of the Commission’s rules that also has an experimental license issued under Part 15 (a listed exclusion category), is not excluded from the collection if it purchased Dedicated Service in a price cap area during the relevant reporting periods. Likewise, an entity holding an antenna structure registration under Part 17 (a listed exclusion category) is not excluded from the collection if it provided a covered Best Efforts Business Broadband Internet Access Service in a price cap area.

0 Alternatively, for submissions containing too much data to reliably upload, respondents can make arrangements with the Bureau for the manual submission of hard drives or other data storage devices containing their responses.

0 Responses must conform to the specifications provided in the data container. We intend to submit the instructions and record format specifications to OMB as part of the application package seeking approval for the information collection.

0 See Data Collection Implementation Order, App. B.

0 See Wireline Competition Bureau Seeks Comment on Protective Order for Special Access Data Collection, WC Docket No. 05-25, RM-10593, Public Notice, DA 13-1470 (WCB rel. June 28, 2013).

0 See Special Access Data Collection Order, 27 FCC Rcd at 16340, para. 54.

0 For instructions on how to obtain an FRN, see https://fjallfoss.fcc.gov/coresWeb/publicHome.do.

0 Contact [FCC Contact] to discuss the manual submission of your database container file on hard drive(s) if it is excessively large and cannot reasonably be submitted electronically to the FCC using the SSH File Transfer Protocol, i.e., if the file is more than 11 gigabytes in size. The Filer Identification Information and Certification is required even for manual submissions.

0 See Instructions at 9.

0 See, e.g., Data Collection Implementation Order, App. B, Questions II.A.4 (asking for information on Locations) and II.A.12 (asking for billing information).

0 Metro Ethernet is an Ethernet metropolitan area network service offering that involves centrally positioning one or more gigabit Ethernet (GbE) or 10 gigabit Ethernet (10 GbE) switches in a metro area. It offers the advantage of carrying all traffic in native Ethernet format, with no requirement for introducing SDH/SONET, frame relay, ATM or other Physical Layer or Data Link Layer protocols that can increase both complexity and cost, while adding overhead. See Webster’s New World Telecom Dictionary (2010); see also Ralph Santitoro, Metro Ethernet Forum White Paper, Metro Ethernet Services – A Technical Overview (2006), available at http://metroethernetforum.org/White_Papers/metro-ethernet-services.pdf (providing a comprehensive technical overview of Ethernet services) (last visited Sept. 9, 2013).

0 Examples of services incorporating a Dedicated Service could include: the Converged Business Network solution offered by Level 3; High-Speed Dedicated Internet Access from XO or a business Ethernet solution from TW Telecom. See Converged Business Network, Level 3 Communications Inc. (Level 3), http://www.level3.com/en/products-and-services/data-and-internet/converged-business-network/ (discussing Level 3’s Converged Business Network offering that combines Internet, data and voice services over a single access circuit) (last visited Sept. 9, 2013); Dedicated Internet Access, XO Communications, LLC, http://www.xo.com/services/network/dia/Pages/overview.aspx (discussing dedicated Internet access) (last visited Sept. 9, 2013); Business Ethernet, tw telecom, Inc., http://www.twtelecom.com/telecom-solutions/voice-solutions/business-ethernet-services/ (discussing business Ethernet services) (last visited Sept. 9, 2013).

0 See, e.g., Business Internet + Voice, Comcast Corp. (Comcast), http://business.comcast.com/smb/bundle (discussing a Comcast Business Class bundled service offering that includes business voice, web hosting, email, and Internet access at monthly rates) (last visited Sept. 9, 2013); Cox Business Internet, Cox Communications, Inc., http://ww2.cox.com/business/oklahomacity/data/business-internet.cox?campcode=gntile_b_data_internet (last visited Sept. 9, 2013); Business Internet, Bright House Networks, http://business.brighthouse.com/products-and-services/data-and-internet/broadband-internet.html (last visited Sept. 9, 2013); Optimum: TV, Phone and Internet Services for your Business, Cablevision Systems Corp., http://www.optimumbusiness.com/ (last visited Sept. 9, 2013).

0 See supra note 19 (providing example of services incorporating a Dedicated Service).

0 See System and Tools, Iconectiv, https://codecenter.commonlanguage.com/systems.asp?#clones (providing information about CLONES) (last visited Sept. 9, 2013).

0 Forcing a minimum of two sampling units per Competitive Provider allows for unambiguous estimates of the stratified sample’s standard deviation.

0 High level officers could include the president, chief executive officer, chief financial officer, vice president, general counsel, etc.

0 Subparts listed herein refer to supbarts in Question II.A.12.

0 See Data Collection Implementation Order § III.C (discussing changes to Questions II.A.12-14).

0 We note that Competitive Providers may report more unique Location IDs in response to Question II.A.4 than are referenced in response to Question II.A.12 because Competitive Providers report Locations with Connections that are both idle and in-service. Competitive Providers will only report billing information for those Locations with in-service Connections.

0 ILECs are not required to separately report Locations with Connections sold as UNEs; these Connections are instead included in the Locations reported with owned Connections. See Data Collection Implementation Order § III.C.

0 Examples of services incorporating a Dedicated Service could include: AT&T’s Managed Internet Access service, Verizon’s Private IP service, and Frontier’s Ethernet Internet Access service. See http://www.business.att.com/enterprise/Service/network-services/internet-connectivity/managed-internet-service/ (discussing AT&T’s Managed Internet Access service that provides dedicated access to the Internet or a VPN) (last visited June 24, 2013); http://www.verizonenterprise.com/us/products/networking/private-ip/ (discussing Verizon’s Private IP service which provides a managed VPN / intranet) (last visited June 24, 2013); http://www.frontier.com/enterprise/internet/internet-services/ethernet (discussing Frontier’s Ethernet Internet Access service which provides dedicated access to the Internet) (last visited June 24, 2013).

0 See AT&T, http://www.att.com/u-verse/shop/index.jsp#fbid=axqyY_KT2cT (last visited Mar. 20, 2013); Verizon, http://www.verizonfios.com/ (last visited Mar. 20, 2013).

0 Subparts listed herein refer to supbarts in Question II.B.4.

0 See Data Collection Implementation Order § III.C (discussing changes to Questions II.B.4-6).

0 See Instructions at 9.

File Type	application/vnd.openxmlformats-officedocument.wordprocessingml.document
Author	William Layton
File Modified	0000-00-00
File Created	2021-01-28