Daily Rules, Proposed Rules, and Notices of the Federal Government
This is a summary of the Wireline Competition Bureau Order in WC Docket Nos. 10-90, 07-135, 05-337, 03-109; GN Docket No. 09-51; CC Docket Nos. 01-92, 96-45; WT Docket No. 10-208; DA 12-1155, released on July 18, 2012. The full text
1. In this Order, the Wireline Competition Bureau (Bureau) clarifies certain rules relating to Phase I of the Connect America Fund. Commission staff have received informal inquiries from price cap companies on certain implementation aspects of the rules governing Connect America Fund Phase I. The Bureau also makes an amendment to one of the Commission's rules to fix a clerical error relating to the support for carriers serving remote areas of Alaska.
2. In the
3. Participation in the Connect America Fund Phase I incremental support program is optional. But carriers that accept funding are required to deploy broadband to a number of locations, currently unserved by fixed broadband, equal to the amount of incremental support the carrier accepts divided by $775. Each carrier accepting funding must identify the areas, by wire center and census block, in which it intends to deploy broadband to meet its obligation, when it files its notice of acceptance. Carriers are required to complete deployment to no fewer than two-thirds of the required number of locations within two years and all required locations within three years, and they must certify that they have done so as part of their annual certifications under § 54.313 of the Commission's rules. The Commission also provided that “[c]arriers failing to meet a deployment milestone will be required to return the incremental support distributed in connection with that deployment obligation and will be potentially subject to other penalties, including additional forfeitures, as the Commission deems appropriate.” However, the Commission continued, “[i]f a carrier fails to meet the two-thirds deployment milestone within two years and returns the incremental support provided, and then meets its full deployment obligation associated with that support by the third year, it will be eligible to have support it returned restored to it.”
4. First, the Bureau clarifies how to calculate the amount of support a carrier must return for failing to meet its deployment requirements. Specifically, if a carrier fails to meet its deployment obligations, it will be required to return to the Commission an amount equal to $775 multiplied by the number of locations to which the carrier was required to deploy to but did not, but a carrier will not be required to “pay twice” for any failure to meet a requirement. For example, if a carrier accepted $6,975,000 and committed to deploying to 9,000 locations over three years, but only deployed to 5,800 by the end of two years, rather than the 6,000 required at that milestone, the carrier would be required to return $155,000 of its incremental support (200 locations times $775). Similarly, a carrier that accepted the same amount and deployed to all 6,000 locations by the second year but deployed to only 8,900 by the end of the third year would be required to return $77,500 (100 locations times $775). However, if the same carrier deployed to 5,800 of its required 6,000 locations by the second year, returned the $155,000 required, and then continued its deployment, reaching 8,900 by the end of the third year, it would have $77,500 of its returned support restored. The Bureau notes that this discussion does not address any additional penalties that the Commission may choose to impose on any carrier that fails to meet its deployment obligation, as stated in the
5. Second, the Bureau clarifies that when a carrier files its notice of acceptance of funding, identifying the wire centers and census blocks in which it intends to deploy, it is not binding itself to deploy only in those areas, nor is it committing to deploy to every unserved location in those areas. The Bureau clarifies that carriers are expected to make a good faith effort to identify where they will deploy when they file their notices of acceptance. The Bureau observes, in this regard, that there are a number of practical obstacles that may make it difficult for carriers to commit irrevocably to a particular deployment plan by July 24th. For example, carriers may not have perfect information now about the number of locations in every potential area, the number of locations in an area may change over time, and the aggressive schedule for identifying intended buildout locations may make it difficult for carriers to gain complete information about potential deployments prior to filing their notices of acceptance. Accordingly, the Bureau clarifies that carriers may, in satisfaction of their deployment requirement, deploy to eligible locations not identified in their notices of acceptance, but will be required to identify subsequently where deployment actually occurred. Similarly, if a carrier finds that deploying to an area it intended to deploy to would be impractical, it will not be subject to penalties on account of its failure to deploy broadband to that particular area.
6. Third, the Bureau clarifies that the certification associated with carriers' two- and three-year deployment milestones, which carriers must include as part of their annual filings under § 54.313(b) of the Commission's rules, must specify the number of locations in a census block-wire center combination to which they have actually built. Carriers must identify the precise number of locations so that appropriate adjustments, if any, can be made to support previously provided, if a carrier fails to meet its deployment obligation. To facilitate the ability of USAC and the Commission to validate that carriers have, in fact, met their deployment obligations, carriers must be prepared, upon request, to provide sufficient information regarding the location of actual deployment to confirm the availability of service at that location.
7. Fourth, the Bureau clarifies that the certifications each carrier makes when it accepts incremental support—that the locations to be deployed to are shown on the National Broadband Map as unserved by fixed broadband by any provider other than the certifying entity
8. Fifth, the Bureau clarifies that when a carrier certifies that the locations to which it will deploy are shown as unserved by fixed broadband on the “current” version of the National Broadband Map, the “current” version of the National Broadband Map is the version that was publicly available on the National Broadband Map Web site on the date eligible support amounts were announced. The Commission intended for carriers to have 90 days to determine how much incremental support they would accept and which wire centers and census blocks they would deploy to in order to meet their Connect America Phase I commitments. To the extent the National Broadband Map data is updated during the 90-day period in which carriers are evaluating how much incremental support they will accept, that could leave carriers with less time to evaluate the updated version of the map. Potentially altering Connect America Phase I incremental support deployment plans before the deadline for them to accept funding would be unreasonable and contrary to the Commission's framework for Connect America Phase I funding, and we clarify the requirement to ensure that carriers have a full 90 days to make their Connect America I Phase plans.
9. Sixth, the Bureau further clarifies that the term “fixed broadband” for the purposes of Connect America Phase I includes any technology identified on the then-current version of the National Broadband map that is not identified as a mobile technology or a satellite-based technology. In this regard, the Bureau observes that the technologies reported on the National Broadband Map at the time the
10. Finally, the Bureau corrects § 54.307(e)(5) of the Commission's rules. Paragraph 180 of the first erratum to the
11. This document does not contain new or modified information collection requirements subject to the Paperwork Reduction Act of 1995 (PRA), Public Law 104-13. Therefore, it does not contain any new or modified information collection burden for small business concerns with fewer than 25 employees, pursuant to the Small Business Paperwork Relief Act of 2002, Public Law 107-198, see 44 U.S.C. 3506(c)(4).
12. The Regulatory Flexibility Act of 1980, as amended (RFA), requires that a regulatory flexibility analysis be prepared for rulemaking proceedings, unless the agency certifies that “the rule will not have a significant economic impact on a substantial number of small entities.” The RFA generally defines “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.” In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act. A small business concern is one which: (1) Is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the Small Business Administration (SBA).
13. This Order clarifies, but does not otherwise modify, the
14. The Commission will send a copy of this Order to Congress and the Government Accountability Office pursuant to the Congressional Review Act.
Federal Communications Commission.
For the reasons discussed in the preamble, the Federal Communications Commission amends 47 CFR part 54 to read as follows:
47 U.S.C. 151, 154(i), 201, 205, 214, 219, 220, 254, 303(r), 403, and 1302 unless otherwise noted.
(e) * * *