FCC Web Documents citing 69.118

as compiled by hallikainen.com/FccRules on 2012 06 01

• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-104945A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-104945A1.txt
  • a matter of regulation. For example, the record outlines a variety of difficulties that incumbent LECs will confront in determining peak and off-peak hours with any degree of certainty, based on geographic, user-type, service, and other variations. Moreover, peak usage periods may shift over time as usage patterns change, and as competitors enter the market. Based on 193 47 C.F.R. §69.118. 194 47 C.F.R. § 69.129. 195 Order, 11 FCC Red 3839 (Com. Car. Bur. 1996) Section III.E. 196 Ameritech Comments at 16. Ameritech states that, "SS7 technology is currently used for more than 95% of customers in the Ameritech network. This figure is probably comparable for other large [incumbent LECs.]" 16046 Federal Communications Commission____ FCC 97-158 these difficulties, some incumbent
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-304A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-304A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-304A1.txt
  • may be assessed on originating calls handed off to the interexchange carrier's point of presence and on terminating calls received from an interexchange carrier's point of presence, whether or not that call is completed at the called location. Local exchange carriers may not recover through this charge any costs recovered through other rate elements. (h) Except as provided in § 69.118, non-price cap local exchange carriers may establish rate elements for local switching as follows: (1) Non-price cap local exchange carriers may separate from the projected annual revenue requirement for the Local Switching element those costs projected to be incurred for ports (including cards and DS1/voice-grade multiplexers required to access end offices equipped with analog switches) on the trunk side of
• http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.doc http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.pdf http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.txt
  • price cap tariff becomes effective, which tariff results in an API value (calculated pursuant to § 61.46) that exceeds the currently applicable PCI value, the PCI value shall be adjusted upward to equal the API value. (h) [Reserved] (i)(1)(i) Price cap local exchange carriers that are recovering revenues through rates pursuant to §§ 69.106, 69.108, 69.109, 69.110, 69.111, 69.112, 69.113, 69.118, 69.123, 69.124, 69.125, 69.129, or § 69.155 of this chapter shall target, to the extent necessary to reduce the ATS Charge to the Target Rate as set forth in § 61.3(qq) for the first time, any PCI reductions associated with the dollar impact of application of the (GDPPI-X) portion of the formula in § 61.45(b)(1)(i) to the traffic sensitive and
• http://www.fcc.gov/Bureaus/Common_Carrier/Notices/1995/fcc95419.html
  • 17-19 for a discussion of proposals to reduce lag time. Footnote 97 Although the IXC tariffs contain many references to 800 service, the IXCs are either non-dominant carriers that file tariffs on one day's notice or, in the case of AT&T, offer 800 service as a streamlined service and file most tariff changes on 14 days' notice. Footnote 98 Section 69.118 of the Commission's Rules, [187]47 C.F.R. 69.118, requires many LECs to establish an 800 database sub-element. Footnote 99 For example, Ameritech will not initially be able to deliver 888 traffic through end office switches. It will have to route all 888 traffic through access tandems for several months until 888 routing capability is installed in its end offices. Consequently, Ameritech
• http://www.fcc.gov/Bureaus/Common_Carrier/Notices/1999/fcc99235.doc
  • becomes effective, which tariff results in an API value (calculated pursuant to § 61.46) that exceeds the currently applicable PCI value, the PCI value shall be adjusted upward to equal the API value. (h) [Removed and reserved.] (i) (1) Price cap local exchange carriers that are recovering revenues through rates pursuant to §§ 69.106, 69.108, 69.109, 69.110, 69.111, 69.112, 69.113, 69.118, 69.123, 69.124, 69.125, 69.129 or § 69.155 of this chapter shall target, to the extent necessary to reduce the Average Traffic Sensitive Charge to the Target Rate for the first time, any PCI reductions associated with the dollar impact of the Common Line, Traffic Sensitive, Trunking and Marketing baskets' GDP-PI and productivity factor, as those items are described in paragraph
• http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.doc http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.pdf http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.txt
  • price cap tariff becomes effective, which tariff results in an API value (calculated pursuant to § 61.46) that exceeds the currently applicable PCI value, the PCI value shall be adjusted upward to equal the API value. (h) [Reserved] (i)(1)(i) Price cap local exchange carriers that are recovering revenues through rates pursuant to §§ 69.106, 69.108, 69.109, 69.110, 69.111, 69.112, 69.113, 69.118, 69.123, 69.124, 69.125, 69.129, or § 69.155 of this chapter shall target, to the extent necessary to reduce the ATS Charge to the Target Rate as set forth in § 61.3(qq) for the first time, any PCI reductions associated with the dollar impact of application of the (GDPPI-X) portion of the formula in § 61.45(b)(1)(i) to the traffic sensitive and
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-104945A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-104945A1.txt
  • a matter of regulation. For example, the record outlines a variety of difficulties that incumbent LECs will confront in determining peak and off-peak hours with any degree of certainty, based on geographic, user-type, service, and other variations. Moreover, peak usage periods may shift over time as usage patterns change, and as competitors enter the market. Based on 193 47 C.F.R. §69.118. 194 47 C.F.R. § 69.129. 195 Order, 11 FCC Red 3839 (Com. Car. Bur. 1996) Section III.E. 196 Ameritech Comments at 16. Ameritech states that, "SS7 technology is currently used for more than 95% of customers in the Ameritech network. This figure is probably comparable for other large [incumbent LECs.]" 16046 Federal Communications Commission____ FCC 97-158 these difficulties, some incumbent
• http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-304A1.doc http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-304A1.pdf http://hraunfoss.fcc.gov/edocs_public/attachmatch/FCC-01-304A1.txt
  • may be assessed on originating calls handed off to the interexchange carrier's point of presence and on terminating calls received from an interexchange carrier's point of presence, whether or not that call is completed at the called location. Local exchange carriers may not recover through this charge any costs recovered through other rate elements. (h) Except as provided in § 69.118, non-price cap local exchange carriers may establish rate elements for local switching as follows: (1) Non-price cap local exchange carriers may separate from the projected annual revenue requirement for the Local Switching element those costs projected to be incurred for ports (including cards and DS1/voice-grade multiplexers required to access end offices equipped with analog switches) on the trunk side of
• http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.doc http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.pdf http://transition.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.txt
  • price cap tariff becomes effective, which tariff results in an API value (calculated pursuant to § 61.46) that exceeds the currently applicable PCI value, the PCI value shall be adjusted upward to equal the API value. (h) [Reserved] (i)(1)(i) Price cap local exchange carriers that are recovering revenues through rates pursuant to §§ 69.106, 69.108, 69.109, 69.110, 69.111, 69.112, 69.113, 69.118, 69.123, 69.124, 69.125, 69.129, or § 69.155 of this chapter shall target, to the extent necessary to reduce the ATS Charge to the Target Rate as set forth in § 61.3(qq) for the first time, any PCI reductions associated with the dollar impact of application of the (GDPPI-X) portion of the formula in § 61.45(b)(1)(i) to the traffic sensitive and
• http://www.fcc.gov/Bureaus/Common_Carrier/Notices/1995/fcc95419.html
  • 17-19 for a discussion of proposals to reduce lag time. Footnote 97 Although the IXC tariffs contain many references to 800 service, the IXCs are either non-dominant carriers that file tariffs on one day's notice or, in the case of AT&T, offer 800 service as a streamlined service and file most tariff changes on 14 days' notice. Footnote 98 Section 69.118 of the Commission's Rules, [187]47 C.F.R. 69.118, requires many LECs to establish an 800 database sub-element. Footnote 99 For example, Ameritech will not initially be able to deliver 888 traffic through end office switches. It will have to route all 888 traffic through access tandems for several months until 888 routing capability is installed in its end offices. Consequently, Ameritech
• http://www.fcc.gov/Bureaus/Common_Carrier/Notices/1999/fcc99235.doc
  • becomes effective, which tariff results in an API value (calculated pursuant to § 61.46) that exceeds the currently applicable PCI value, the PCI value shall be adjusted upward to equal the API value. (h) [Removed and reserved.] (i) (1) Price cap local exchange carriers that are recovering revenues through rates pursuant to §§ 69.106, 69.108, 69.109, 69.110, 69.111, 69.112, 69.113, 69.118, 69.123, 69.124, 69.125, 69.129 or § 69.155 of this chapter shall target, to the extent necessary to reduce the Average Traffic Sensitive Charge to the Target Rate for the first time, any PCI reductions associated with the dollar impact of the Common Line, Traffic Sensitive, Trunking and Marketing baskets' GDP-PI and productivity factor, as those items are described in paragraph
• http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.doc http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.pdf http://www.fcc.gov/Bureaus/Common_Carrier/Orders/2000/fcc00193.txt
  • price cap tariff becomes effective, which tariff results in an API value (calculated pursuant to § 61.46) that exceeds the currently applicable PCI value, the PCI value shall be adjusted upward to equal the API value. (h) [Reserved] (i)(1)(i) Price cap local exchange carriers that are recovering revenues through rates pursuant to §§ 69.106, 69.108, 69.109, 69.110, 69.111, 69.112, 69.113, 69.118, 69.123, 69.124, 69.125, 69.129, or § 69.155 of this chapter shall target, to the extent necessary to reduce the ATS Charge to the Target Rate as set forth in § 61.3(qq) for the first time, any PCI reductions associated with the dollar impact of application of the (GDPPI-X) portion of the formula in § 61.45(b)(1)(i) to the traffic sensitive and