NOTICE ********************************************************* NOTICE ********************************************************* This document was originally prepared in Word Perfect. If the original document contained-- * Footnotes * Boldface & Italics --this information is missing in this version The document format (spacing, margins, tabs, etc.) is changed too. If you need the complete document, download the Word Perfect version. For information about downloading documents (FTP) see file how2ftp. File how2ftp (.txt & .wp) is in directory \pub\Public_Notices\Miscellaneous. ***************************************************************** ******** $// MO&O, Reporting Requirements on Video Dialtone Costs, DA 95-2036 //$ $/ Part 32, USOA /$ $/ Part 36, Jurisdictional Separations Procedures /$ FOR RECORD ONLY Before the FEDERAL COMMUNICATIONS COMMISSION Washington, D.C. 20554 In the Matter of ) ) Reporting Requirements on Video Dialtone ) DA 95-2036 Costs and Jurisdictional Separations for ) AAD No. 95-59 Local Exchange Carriers Offering ) Video Dialtone Services ) MEMORANDUM OPINION AND ORDER Adopted: September 29, 1995; Released: September 29, 1995 By the Chief, Common Carrier Bureau: I. INTRODUCTION 1. In the Video Dialtone Reconsideration Order ("VDT Recon Order"), the Commission required that local exchange carriers ("LECs") establish subsidiary accounting records to capture the costs and revenue arising from the provision of video dialtone service ("VDT"). In that order, the Commission also delegated authority to the Common Carrier Bureau ("Bureau") to determine the content and format of the subsidiary accounting records and quarterly reports for VDT. On June 23, 1995, the Bureau released an Order Inviting Comments that solicited comment on the proposed content and format of the reports LECs must file. In this Order, we adopt and implement the reporting requirements proposed by the OIC with certain modifications designed to reduce the LECs' reporting burden. The reports we adopt in this Order include the following: (i) a quarterly report that would contain wholly dedicated and shared VDT cost captured in subsidiary accounting records; and (ii) an expanded fourth quarter report that would contain VDT cost and revenue data disaggregated by regulated and nonregulated classifications and by jurisdictional categories. Reporting requirements defined in this item apply to all LECs offering VDT market or technical trials as well as commercial VDT. We also require LECs to include in the expanded fourth quarter report data that would enable the Commission to monitor the impact of VDT on local telephone rates. In addition, we adopt streamlined reporting requirements for LECs' VDT planning and development costs that are incurred by carriers prior to receiving Section 214 authorization to provide VDT in a study area. Finally, we make certain modifications to our previously proposed reporting requirements. II. BACKGR OUND 2. Beginning in 1991, the Commission adopted policies and rules to permit LECs to assume an expanded role in the provision of video services in their telephone service areas. In its 1991 and 1992 orders, the Commission established a regulatory framework called "video dialtone" enabling telephone companies to deliver video programming on a common carrier basis and provide various VDT-related nonregulated services, consistent with the cross- ownership restrictions imposed by the Cable Communications Policy Act of 1984 ("1984 Cable Act"). 3. On November 7, 1994, the Commission issued the VDT Recon Order. In that Order, the Commission reaffirmed the basic framework adopted in the Second Report and Order, and, among other things, set forth accounting and reporting requirements for LECs that offer VDT. In the VDT Recon Order, the Commission required carriers offering VDT to establish two sets of subsidiary accounting records: one to capture the investment, expense, and revenue wholly dedicated to VDT; the other to capture the investment, expense, and revenue shared between VDT and other services. The Commission also required LECs authorized to provide VDT to file summaries of these subsidiary accounting records with the Commission on a quarterly basis. The Commission stated that LECs would be required to file VDT quarterly reports as a condition of their Section 214 authorization. The Commission delegated to the Bureau the authority to determine the content and format of the VDT subsidiary accounting records and the quarterly reports. In addition, the Commission directed the Bureau to develop a data collection program to track the impact of VDT on both local telephone rates and the results of the jurisdictional separations process. 4. On June 23, 1995, the Bureau issued an Order Inviting Comments (OIC) soliciting comments on the proposed content and format of the reports LECs must file under the Commission's VDT Recon Order, when providing VDT. The OIC also proposed to implement a data collection program to measure the impact of VDT on local telephone rates and the jurisdictional separations process. III. DISCUSSION A. Goals of the Reporting Requirements 5. The reporting requirements we adopt today are designed to advance two important Commission goals. First, we establish a data collection system that is necessary to ensure that telephone ratepayers do not bear the costs of VDT and that would also help to protect cable operators from potential LEC anti-competitive conduct. These data will be especially useful during the tariff review process. In crafting these uniform VDT reporting requirements, we seek to implement the requirements enunciated in the Commission's VDT Recon Order in a manner that is least burdensome on carriers. In every LEC monitoring program, we balance our informational needs against the costs and burdens LEC compliance with these informational requests impose. We seek the minimal reporting requirement that will enable us to meet our statutory responsibilities. This has caused us to re-evaluate the reporting requirements proposed in the OIC and eliminate those data that we determined are not essential to meet the Commission's goals of protecting telephone ratepayers and preventing anti-competitive activities. Our re-evaluation was made after reviewing comments made by LECs and their trade associations that asserted that the proposed reporting requirements in the OIC were too burdensome and over-regulatory and comments offered by the cable industry, their trade associations, and several representatives of states' interests that found our proposed reports to be not burdensome and in need of expansion. We believe that the reporting requirements we adopt herein strike an appropriate balance between these conflicting positions. B. RAO Letter 25 6. On April 3, 1995, the Bureau's Accounting and Audits Division issued RAO Letter 25, which sets forth specific guidelines on the requirements for accounting classifications, subsidiary records, and amendments to cost allocation manuals ("CAMs") for LECs that receive Section 214 authorization to provide VDT. In the OIC, we proposed the content and format of the reports LECs would file when offering VDT. LECs would generate these reports based on the subsidiary accounting records prescribed by RAO Letter 25. BellSouth, GTE, Southwestern Bell, US West, United, and USTA argue that it is premature for the Bureau to address the comments and reply comments regarding the OIC until the pending Applications for Review of RAO Letter 25 are addressed. These commenters believe that the issues of subsidiary recordkeeping and reporting requirements require that the Commission first address the legitimacy of the subsidiary recordkeeping requirements of RAO Letter 25 before either the Commission or the Bureau addresses the reporting requirements proposed by the Bureau in its OIC. 7. In light of the fact that the Commission has already approved 26 Section 214 applications to provide VDT either commercially or on a trial basis, we believe that it is necessary to establish VDT reporting requirements and to receive information that will enable the Commission to analyze the VDT operations without delay. The information that we would collect is particularly critical in the tariff review process. While the Commission, at its discretion, may modify the subsidiary accounting records provided in RAO Letter 25, the basic information needs of the Commission, consistent with the VDT Recon Order, will not change. In this Order, therefore, we adopt reporting requirements in accordance with the Commission's goals. We intend to re-evaluate these reporting requirements as we gain experience in VDT and will modify the reporting requirements when circumstances allow us to do so. In addition, if the Commission decides to amend the requirements of RAO Letter 25 in such a way that will affect the VDT reporting requirements, we will modify our reporting requirements accordingly. In the meantime, we believe it is paramount that we receive the VDT reports as adopted herein. C. Modifications to Proposed Reporting Requirements 1. Carrier Proposed Structural Changes 8. In the OIC, we proposed the format and content of quarterly and annual VDT reports. Bell Atlantic, NYNEX, and Southwestern Bell argue that the Bureau should amend its proposed VDT reporting requirements; each submitted alternative reporting requirements for consideration. Bell Atlantic proposed to replace the annual report and quarterly reports contained in the OIC with one report consisting of four columns that would present total dedicated VDT costs, total shared costs, VDT portion of shared costs, and fully distributed costs to VDT. Only the last column of Bell Atlantic's proposed report would provide cost data after the jurisdictional separations process. Bell Atlantic claims that this column would represent the fully distributed cost allocations resulting from applying Parts 36 and 69 of the Commission's cost allocation rules to wholly dedicated and shared VDT costs. Bell Atlantic's proposed report would also contain only 30 lines in contrast to the 64 lines and 67 lines in the OIC's proposed quarterly and annual report. In the three columns relating to unseparated data, Bell Atlantic would enter data on only two of their 30 lines that represent categories of costs and revenues. Bell Atlantic claims that its proposed report would be consistent with the requirements specified in the VDT Recon Order and that it would be easier to prepare. 9. NYNEX argues that the Bureau's proposed VDT reports are premature and unnecessarily formal and detailed. NYNEX contends that, because VDT is in its infancy, the Bureau should create a more informal report. NYNEX proposes changes to the quarterly report that would eliminate certain line items related to federal income taxes, other operating items, nonoperating items, and certain revenue detail. NYNEX also proposes to include additional detail regarding shared costs. Instead of reporting all shared costs in one column as the OIC proposed, NYNEX proposes to disaggregate shared costs into two separate categories based upon whether those costs are identified by field reporting codes. 10. Southwestern Bell proposes quarterly reports in addition to an annual report. Southwestern Bell's proposed quarterly report contains the same three columns proposed by the OIC, except that Southwestern Bell's report would only provide information for 26 categories of costs and revenues. For example, its report would not include line items for separate revenue categories, non-operating items, and federal, state and local tax data. Southwestern Bell's proposed annual report would contain only two columns: interstate costs with VDT and interstate costs without VDT. Southwestern Bell's annual report does not show the impact of VDT on the intrastate jurisdiction. 11. We have reviewed the reports proposed by Bell Atlantic, NYNEX and Southwestern Bell and do not believe that any of the reports would achieve the Commission's goals or advance the public interest. Bell Atlantic's report only proposes to provide data on 2 of 30 line items with respect to dedicated VDT costs, total shared costs, and VDT portion of shared costs. Bell Atlantic's proposal to eliminate the annual report would prevent us from collecting data to gauge the impact of VDT on local telephone rates. NYNEX's proposed report would provide no data with respect to either the separations process or local telephone rates. As a result, Bell Atlantic's and NYNEX's reports would not provide us with the information necessary to meet the Commission's goals to effectively monitor VDT implementation to protect telephone ratepayers from absorbing VDT costs and cable operators from facing anti-competitive activities. We also believe that Southwestern Bell's proposal, while most similar to our proposed reporting requirements, is also deficient because it would fail to provide us with information concerning the impact of VDT on intrastate operations. 12. We believe that the formats and content of the report we now adopt are more comprehensive than that proposed by Southwestern Bell. We believe, however, that one of Southwestern Bell's recommendations with respect to the incorporation and treatment of Part 36 separations data in our VDT reports has merit. Southwestern Bell proposes that we use a methodology to apply Part 36 jurisdictional cost allocation procedures to total costs and then to apply those Part 36 rules to total costs less the costs captured in the VDT subsidiary records. Southwestern Bell contends that this approach would provide information about VDT's impact on the costs allocated to the interstate jurisdiction. We believe that once a LEC has made the computations suggested by Southwestern Bell, it should be able to make a reasonable estimate of the impact on the costs allocated to the intrastate jurisdiction, which we also require to be detailed in the fourth quarter report. 13. We also believe that we should incorporate one of Bell Atlantic's suggestions. In particular, Bell Atlantic suggests that the Bureau's report include a column for the amounts of shared costs and revenues that are allocated to VDT. We believe this additional information would provide information on a quarterly basis that would further assist the Commission in the VDT tariff review process by providing information on a quarterly basis concerning LECs' total VDT costs, both direct and allocated. We, therefore, add a column to FCC Report 43-09A and FCC Report 43-09B, the VDT Quarterly Report and Fourth Quarter Report, that provides data concerning the amount of shared costs and revenue that are attributable to VDT. 2. Service Data 14. A number of commenters criticized the OIC for requiring carriers to separate investment, expense, and revenue data by service. NYNEX states that the Part 36 separations process does not provide for allocations of investment, expense, reserve, and revenue categories between jurisdictions by service. Bell Atlantic claims that none of the ARMIS reports require service information and that, by superimposing separate columns for VDT direct and shared costs, the proposed reports seek information that does not exist. Bell Atlantic also states that the Commission rejected product-specific accounting for regulated VDT in the VDT Recon Order. BellSouth states that, with its reporting requirements, the Bureau mistakenly assumes that the Part 36 process is a cost of service process where a specific service such as VDT can be tracked through each and every separations category and allocation algorithm. GTE concurs that LECs are not required to record separate types of investments by technology for purposes of jurisdictional separations under Part 36. GTE also states that the OIC proposes that certain data be disaggregated at a level more detailed than that provided in ARMIS or required by Part 36 separations rules. 15. NARUC comments that monitoring LEC infrastructure improvements is necessary to achieve the Commission's pro-competitive goals. NARUC also argues that, to effectively monitor VDT investments and expenses separately from telephone service, the ARMIS report needs to reflect any new technologies used to provide VDT services. MCI states that temporary accounting and reporting requirements are necessary to allow the Commission, as well as other interested parties and access ratepayers, to verify that VDT costs are not being misallocated to telephony. 16. In the VDT Recon Order, the Commission stated that it was not necessary to adopt comprehensive, VDT-specific accounting and cost accounting rules before authorizing VDT. The Commission further stated that while it chose not to amend Parts 32, 64, 36, and 69 of the Commission's rules, adjustments would be needed to fit VDT into the Commission's regulatory program. VDT subsidiary accounting recordkeeping requirements are one example of the type of regulatory adjustment made in order to monitor LEC development of VDT. Neither the Commission, nor the Bureau has mandated specific cost accounting and allocation rules for VDT. The Commission is simply requiring LECs to indicate how they are accounting for VDT, to identify dedicated and shared VDT costs, and to disclose the impact of VDT on the jurisdictional separations process and local telephone rates. 17. With respect to those LECs asserting that the Bureau is requesting data that do not exist, we again note that RAO Letter 25 has set forth guidance on the required subsidiary accounting records that LECs should maintain in order to capture VDT costs and revenues. LECs that have already received Section 214 authorization to provide VDT must comply with RAO Letter 25's directives on how to capture VDT costs and revenues in appropriate subsidiary accounting records. In addition, we do not mandate any particular methodology for reporting the impact of VDT on the separations process. In response to comments regarding the need for VDT specific cost data, we do not, in this Order, revisit the Commission's decision in the VDT Recon Order to require LECs to file VDT cost information. That issue is beyond the scope of this proceeding. 3. Explanations of the Application of Accounting and Cost Allocation Rules 18. In the VDT Recon Order, the Commission directed the Bureau to require all LECs to submit detailed explanations of how they are applying the Commission's accounting and cost allocation rules to VDT investment and expenses. MCI and Comcast claim that the OIC reporting requirements are insufficient in that they do not require that LECs fully explain how they are separating VDT investment and expenses under Part 36 and applying Parts 32, 61, and 64. 19. We disagree with MCI and Comcast that the Bureau will not receive the information on the application by LECs of Parts 32, 61, and 64 to VDT costs and revenue. First, with respect to Part 32, the Bureau's RAO Letter 25 sets forth guidance concerning the subsidiary accounting records required to capture VDT costs and revenue. LECs present the necessary explanations as they comply with the subsidiary accounting records requirement of RAO Letter 25. Second, the Commission has recently adopted the VDT Price Cap Order which requires LECs to establish a separate price cap basket for VDT. This item provides guidance to LECs on how to apply Part 61 to VDT costs and revenue. Finally, LECs are required to amend their cost accounting manuals (CAMs) to reflect both the regulated and nonregulated costs incurred in the provision of VDT. As a result, through the combination of the RAO Letter 25 subsidiary records, VDT reporting, and CAM amendment processes, the Bureau will receive detailed explanations of the application of how the LECs have applied Parts 32, 61, and 64 to VDT costs and revenue, as required by the Commission. 20. We do, however, agree with MCI and Comcast that the Bureau is not receiving information concerning the application of Part 36 to VDT costs and revenue. Accordingly, we require that each LEC that has received Section 214 authorization to provide VDT shall include a detailed explanation of how it is applying the Part 36 rules to VDT costs and revenues. The explanation must be provided in an addendum to the first quarterly report that LECs are required to file after the release of this Order. 4. Fourth Quarter Report 21. The OIC proposed that LECs file an annual report in which they collect and summarize VDT investment, expense and revenue data disaggregated by regulated and nonregulated classifications and also by jurisdictional categories. In its reply comments, BellSouth questions the Bureau's authority to require an annual report in addition to quarterly reports. BellSouth maintains that the VDT Recon Order only authorized quarterly reports. 22. We disagree with BellSouth's argument that the Bureau lacks the authority to require an annual report in addition to the quarterly VDT reports. The Commission directed the Bureau to initiate a data collection program to procure data that would enable the Commission to measure the impact of VDT on the jurisdictional separations process and on local telephone rates. The Bureau proposed to collect these data through a single annual report, as opposed to the proposed four quarterly reports. Furthermore, as suggested by Comcast, we could require the information contained in the proposed annual report to be filed in each quarterly report and forego an annual report. 23. In response to LEC concerns that the proposed VDT reports would be potentially burdensome, we have decided to revise the reporting requirements proposed in the OIC. The OIC had proposed that LECs providing VDT submit one annual report and four quarterly reports. We now modify our original proposal by adopting a reporting structure that would require LECs providing VDT to submit three quarterly reports, prepared on a cumulative basis in a manner similar to our existing ARMIS Report 43-01, and an expanded, cumulative fourth quarter report that would encompass the same annual report requirements detailed in the OIC as adjusted herein. We, thus, no longer require both an annual report and a fourth quarter report as proposed by the OIC because we believe our data collection directives can be achieved through the use of an expanded fourth quarter report. As a result, we believe that our proposed reporting requirements are consistent with the Commission's directive and would also satisfy our goal to reduce LECs' reporting burden. 5. Specific Line Items 24. In the OIC, we proposed to require reporting at a similar level of detail to that currently required in the FCC Report 43-01, ARMIS Quarterly Report. The areas in which the OIC proposed to require LECs to provide additional data include: basic local service revenue for which we proposed three additional line items; and, plant-in-service, for which we proposed to disaggregate cable and wire facilities into metallic cable, non-metallic cable, and other plant. The 43-01 data that we proposed to eliminate as a part of our VDT reporting were miscellaneous and rate of return data. 25. The LECs generally argue that we should eliminate additional lines of data because they are not relevant to VDT. The cable industry and others argue that additional detail is necessary. Based on our review of the record and the Commission's VDT reporting goals, we have decided that the level of detail that we currently employ in FCC Report 43-01, ARMIS Quarterly Report, is most appropriate for LEC VDT reports. This level of detail is specified in Part 32 of the Commission's rules and is generally equivalent to that which Class B carriers must provide in their accounting systems. 26. After reviewing the record and the Commission's goals, we have decided to eliminate lines 1001, 1002, and 1005 of the OIC's proposed annual report, because we do not believe our need for the information outweighs the associated LEC reporting burden. These lines are also not included in the FCC Report 43-01. We would still receive aggregated revenue data that is satisfactory for our VDT monitoring needs. We also are eliminating lines 1510 through 1550 which, although they are contained in FCC Report 43-01, do not represent accounts used directly to determine VDT costs. These lines are instead used to make federal income tax calculations, and accordingly, are not needed as a part of the regular VDT reports. Finally, we eliminate lines 1110 and 1610, Equal access expenses and Equal access investment. These costs are totally unrelated to the provision of VDT and, therefore, are not needed. 27. While we generally adopt the level of detail used in FCC Report 43-01, we will require a more disaggregated breakdown for cable and wire facilities' costs. We note that LEC VDT Section 214 applications filed with the Commission have generally sought authorization for VDT system architectures based on coaxial and fiber optics systems. We are cognizant that VDT facilities' cost data are an essential component of the tariff review process. Consequently, we will not eliminate or modify the line items for metallic and non-metallic cable and wire facilities. We do, however, agree with the LEC commenters that the mechanics of our existing Part 36 jurisdictional separations rules make a disaggregation between metallic and non-metallic cable costs extremely difficult. We believe that to require LECs to report this information after the separations process would be unnecessarily burdensome. We accordingly change our expanded fourth quarter report to maintain line items for metallic and non-metallic wire cable; but we enter "N/A" in the columns of the report that no longer require LEC data entries. 6. Planning and Development Costs 28. In the OIC, we solicited comment on whether we should require LECs filing Section 214 applications for VDT to make separate filings identifying the costs associated with the planning and development of VDT incurred prior to receiving Section 214 authorization. Bell Atlantic objects to the proposed planning and development cost report. Bell Atlantic argues that the proposed filing represents a new report and that the Bureau does not explain the value of this reporting requirement. GTE states that this reporting requirement exceeds the Commission's delegated authority to the Bureau in the VDT Recon Order. NYNEX and Bell Atlantic argue that planning and development costs generally apply to a LEC's total operations overlapping various Section 214 applications; and therefore, these costs cannot be disaggregated to the level of granularity proposed by the Bureau. GTE claims that it has no existing internal mechanisms to identify and track all planning related costs that involve VDT. USTA and Southwestern Bell state that a separate filing to identify planning and development costs for each Section 214 authorization is unnecessary. USTA also suggests that LECs can provide this information in the form of a footnote to the first quarterly report. 29. Chronicle and Comcast support the Bureau's OIC proposal to require LECs to submit a separate filing for planning and development costs. Chronicle contends that the LECs' planning and development costs are substantial and that it is critical that the Bureau impose a separate filing requirement. Comcast states that, without this separate report, LECs could include VDT development costs with the costs of regulated telephone service, and the Commission would be unable to separate or even identify these costs in the telephone ratemaking process. MCI also endorses the Bureau's reporting requirements for planning and development costs because costs associated with VDT platforms are large and the lead times to build out systems are lengthy. 30. We agree with the LECs that planning and development costs may benefit or relate to various Section 214 applications; we do not believe, however, that these costs should go unreported. Planning and development costs are incurred during the initial stages of any new service deployment and such costs may be significant. In the case of VDT planning and development, these costs can be incurred prior to the receipt of a Section 214 authorization to provide VDT service. In the VDT Recon Order, the Commission delegated to the Bureau the authority to direct LECs to identify all direct and shared VDT costs in their subsidiary accounting records. One of our goals in this proceeding is to assure that LECs provide information that meets the Commission's informational requirements. Costs associated with VDT planning and development are among the information needed to monitor VDT operations and to assist the Commission in the tariff review process. We also need this information in order to ensure that regulated ratepayers do not absorb the costs of VDT planning and development. 31. The OIC proposed a requirement that LECs provide VDT planning and development costs for each of their Section 214 VDT applications. LECs generally argue that most of these costs cannot be identified separately by individual Section 214 application. We agree and therefore will not require that such data be submitted by each application. Nevertheless, in order to ensure that no VDT costs are charged to telephone services, LECs must identify and segregate all VDT costs from their telephone service costs. VDT planning and development costs clearly require such treatment. Therefore, we will require LECs to identify and file such data. 32. We have decided that a separate VDT planning and development report is unnecessary and that the required information from LECs can be obtained in a less burdensome manner. We adopt USTA's suggestion that information concerning planning and development costs be filed in a footnote to the first quarterly VDT report submitted pursuant to this Order for each study area. That footnote should identify, by Part 32 account, all costs associated with the planning and development of VDT that are incurred prior to the carrier's receiving the first Section 214 authorization in a study area. 7. Rounding 33. In the OIC, we proposed that LECs report VDT financial data in amounts rounded off to the nearest hundred dollar amount instead of the nearest thousand dollar amount as currently required in the ARMIS Quarterly Report (43-01). Bell Atlantic, BellSouth, GTE, NYNEX, and Southwestern Bell state that rounding to the nearest hundred dollar amount is burdensome and would not improve the Commission's ability to monitor VDT. Comcast supports the hundred dollar rounding requirement but suggests that the amounts should be reported in thousands with one place to the right of the decimal point used to indicate hundreds. 34. We are persuaded by the arguments of the commenters that we can adequately monitor VDT by receiving reports that round amounts to the nearest thousand dollars. This convention is consistent with what we have used for every other ARMIS Report and we believe this convention provides detail adequate for our oversight responsibilities. As a result, we require that the amounts included in the quarterly VDT reports and the fourth quarter VDT report shall be rounded to the nearest thousand dollar. 8. Non-financial Data 35. Several parties recommend that the reports should be revised to include non-financial data. Colorado recommends that the reports include the number of basic telephone subscriber switched access lines in the VDT serving area and an estimate of the VDT shared capacity in new and existing plant. NCTA proposes that the annual report should contain the methodology that LECs use to allocate investment and expense between video and telephony. NARUC recommends that the reporting requirements for VDT providers should include items such as market demographics, statistics on service quality, and system capabilities. 36. In their reply comments, various LECs oppose expanding the scope or detail level of the Bureau's proposed reporting requirements. Bell Atlantic, BellSouth, Southwestern Bell and US West argue that the level of detail sought by these commenters exceed the Commission's information directives included in its VDT Recon Order. Southwestern Bell notes that many of the parties favoring more detailed reporting are current or future competitors of LECs. Bell Atlantic states that cable companies want telephony data included in the reports; but that there are few, if any, such reporting requirements for cable companies that provide telephony. The more burdensome the reporting requirements, Southwestern Bell explains, the more likely it will be that LECs will choose to provide video programming as a cable company under Title VI, rather than to provide VDT subject to Title II regulation. 37. At this time, we adopt none of the recommendations to expand the VDT reporting requirements concerning non-financial data. While many of the parties' suggestions would provide more detailed reports on the LECs' VDT operations, we are concerned that adoption of these recommendations would render the reporting requirements unreasonably burdensome. We believe the level of reporting we adopt in this Order will meet our needs for our monitoring efforts. We believe that the burden of increasing the level of reporting to include all parties' recommendations would outweigh the benefits of the information collected. 9. Service Area Reporting 38. The OIC proposed VDT reporting at the study area level. Chronicle asserts that VDT systems are not authorized at the statewide area. Each system must be authorized based on the specific economic and technical requirements of a particular area. As a result, Chronicle maintains that data aggregated to a statewide or study area level will not provide the Commission the level of detail necessary to monitor Section 214 authorizations or LEC cable franchises meaningfully. Colorado also requests that the VDT reports should obtain information concerning the location in the separation study area at which the VDT investments and expenses have been incurred. 39. In their reply comments, Bell Atlantic, BellSouth, and Southwestern Bell dispute the assertions of Chronicle and Colorado. Bell Atlantic claims that the cable companies propose reports based on service area data that do not exist. Bell Atlantic does, however, state that it is not unreasonable to identify by name those wire centers where VDT investment is included as suggested by Colorado. BellSouth states that service area reporting was rejected by the Commission in the VDT Recon Order. Southwestern Bell believes that service area reports would provide information to its competitors about where a LEC invests so that the competitor can respond effectively to the detected LEC competition. 40. We believe that the expense to the LECs of providing VDT revenue and cost data by VDT service area will outweigh the benefits that may be derived from such reporting. There is little question that such data, to the extent they are known, would be very useful to the Commission in monitoring the LECs' accounting and cost allocation processes and in reviewing VDT tariffs. Most of the LECs' accounting and cost allocation processes, however, operate at the study area level. As a result, their accounting systems do not readily permit the recovery of cost information, VDT or otherwise, at the VDT service area level. Furthermore, many of the Section 214 applications cover only a few thousand homes. If LECs decide to provide VDT over their entire study area, they may establish ten or more VDT service areas. To regularly report VDT data for each of these areas would not appear to be possible. Therefore, we will not require it. Instead, we will require reporting of VDT data by study area, as most ARMIS data are currently reported. 41. We, however, agree with Colorado that information concerning the location of a LEC's individual service areas would be useful and, as Bell Atlantic suggests, not unduly burdensome. As a result, we require that LECs disclose, in a footnote to each quarterly report, the number and locations of Section 214 authorizations to provide VDT within the relevant study area, a brief description of each VDT service area, the location by name or code number of the wire centers serving each area, and the total number of homes passed by each VDT systems. D. Confidentiality 1. Nonregulated Sections of the Reports 42. In the OIC, we proposed that LECs file an annual VDT report that would collect and summarize the LECs' VDT investment, expense, and revenue data disaggregated by regulated and nonregulated classifications. GTE states that nonregulated services are competitive and should not be subject to public disclosure. NYNEX and Southwestern Bell also cite the proprietary concerns regarding competitive services data. 43. We agree with GTE, NYNEX, and Southwestern Bell that nonregulated services are competitive; however, we are not persuaded that any portion of the VDT reports should be kept confidential. The information contained in the VDT reports would be aggregated data covering all VDT nonregulated services. No disaggregation by separate nonregulated services is required. As a result, there is no danger that a LEC's competitor for one nonregulated service will obtain information that can be used to place that LEC in a competitive disadvantage. 44. We intend to include LEC VDT reports in the ARMIS database and we will make these reports available to the public in the same manner as we do other ARMIS Reports. If LECs believe that they will experience competitive harm through the release to the public of information contained in the reports, they should follow the procedures established in the Commission's rules to request the confidentiality of such information. 2. Product-specific Reporting 45. USTA, US West, Bell Atlantic, GTE, and Southwestern Bell criticize the OIC proposals by claiming that they would amount to product specific reporting for nonregulated activities. USTA and US West cite the Commission's Joint Cost Order that states that the pricing for nonregulated products and services is outside the Commission's statutory mandate. 46. The Joint Cost Order specifically stated that the purpose of our cost allocation rules is to make sure that all of the costs of nonregulated activities are removed from both the rate base and allowable expenses for interstate regulated services. Our cost allocation rules must also ensure that nonregulated VDT costs are removed from regulated VDT service cost. Nonregulated VDT can include numerous services for which the Commission has not required separate accounting treatment. Nonregulated VDT data are not disaggregated for each nonregulated VDT service, but are instead presented in toto. Information with respect to nonregulated services is already required in the LECs' CAMs that are subject to public comment and our approval. We have not adopted cost allocation rules for nonregulated VDT and are not receiving information regarding the pricing of nonregulated VDT. As a result, we do not believe our VDT reports request product specific information with respect to nonregulated VDT and; thus, the OIC does not violate Commission principles outlined in the Joint Cost Order. E. Procedural Matters 47. In the OIC, we proposed that LECs file their first quarterly VDT report 90 days after the end of the calendar quarter in which they receive authorization to provide VDT pursuant to Section 214. GTE and BellSouth request that we clarify that the VDT Quarterly Report for LECs that have already received Section 214 authorization to provide VDT is due 90 days after the end of the calendar quarter in which the final report form is adopted. Comcast requests that we specify that diskettes be provided in a Lotus 1-2-3 format so that the reports may be easily reviewed by interested parties. NARUC requests that the VDT Reports be available for electronic access by state regulators via dial-up access. 48. We require LECs to file a quarterly VDT report after they receive their first Section 214 authorization in each study area. We clarify that the first quarterly report is due on the last day of the calendar quarter following the quarter in which a LEC receives its first Section 214 authorization in a study area. We further clarify that LECs that have already received Section 214 authorizations and have been awaiting finalized reporting requirements must submit their quarterly reports on the last day of the calendar quarter following the quarter in which this Order is adopted. LECs must also file all previous quarterly reports on that date with all of the information required by this Order. LECs that previously have filed quarterly reports will not be required to resubmit those reports. LECs must file their future quarterly reports in accordance with the procedures set forth in the Appendices to this Order. 49. We are incorporating FCC Reports 43-09A and 43-09B, the VDT quarterly reports and expanded fourth quarter report, into the Commission's ARMIS data base; interested parties will be able to gain access to these reports when they gain access to the ARMIS data base. We, accordingly, do not require that LECs submit diskettes in Lotus 1-2-3 format in addition to the ASCII format used for ARMIS reporting purposes. F. Sunset Date for Reporting Requirements 50. In the OIC, we solicited comments concerning how and when we should terminate the proposed VDT reporting requirements. Several of the commenters suggest that the VDT reporting requirements should terminate at some specific time. Southwestern Bell states that the reporting requirements should be eliminated for a particular LEC as soon as the Bureau has received sufficient information to determine the impact of VDT on telephone rates and/or separations. Southwestern Bell further states that this process should only take two to three years. Southwestern Bell also believes that a carrier subject to price cap regulation that has elected a "no sharing" option should be exempt from the reporting requirements. Bell Atlantic also believes that once VDT is subject to price cap regulation, there is no justification for ongoing reporting requirements. GTE proposes that the quarterly reporting requirement be terminated no later than one year from the date when an exchange carrier's VDT services are included under price cap regulation. NYNEX believes that the reporting requirements should be streamlined or eliminated at the earliest possible time in light of factors such as alternate video systems like wireless cable or direct broadcast satellites, price cap regulation resulting in local rate freezes, or federal legislation that eliminates regulatory barriers to effective competition. NYDPS states that the VDT reporting requirements would be obsolete when there is competition in the telecommunications marketplace. NYDPS does not, however, believe that the necessary level of competition has yet been attained. 51. Specifically opposing the elimination of reporting requirements are Colorado and NCTA. Colorado notes that the development of competition in VDT will not in itself provide an opportunity to lift or modify the reporting requirements. Colorado emphasizes that existing or potential competition is the very reason why these reporting requirements should remain in place for the foreseeable future. Colorado also states that several years of experience with the type of data reporting contemplated by the OIC are required to assess the effects of the requirement. NCTA states that the reporting requirements should not be eliminated unless they are replaced by a more comprehensive mechanism for supervising VDT investment, expenses, and revenue or the provision of telephone service is deemed competitive. 52. We believe it is necessary to gather data concerning VDT in order to monitor the implementation of VDT, to collect information to measure the impact of VDT on the jurisdictional separations process, to minimize the risk of cross-subsidization, to assist in the tariff review process, and to gauge the effect, if any, on local telephone rates. We are not in a position to say that we will eliminate the reporting requirements at any particular time. We do, however, agree with the comments of Colorado that several years of experience with the reporting requirements will be necessary to gauge their effectiveness. As we gain that experience, we will re-evaluate our reporting requirements to determine the point at which we can, subject to our delegated authority, minimize or eliminate VDT reporting requirements. If such minimization or elimination of reporting requirements is outside the scope of our delegated authority, but appropriate based on future circumstances, we would propose to the Commission that those reporting requirements be amended. IV. NARUC MOTION 53. In its reply comments, NARUC included a motion requesting that the Commission immediately initiate a comprehensive review of its Part 36 rules to reflect changes in technology, market conditions, and industry structure. NARUC also moved that the Commission refer issues raised by RAO Letter 25 and the comments in this proceeding to the Separations Joint Board. Bell Atlantic filed in opposition to NARUC's motion. 54. In the VDT Recon Order, the Commission stated that it would initiate an inquiry concerning the implications for the jurisdictional separations process of the introduction of new technologies, including broadband technologies, into local exchange networks. The Commission plans to address matters raised by NARUC's motion when it shortly opens its broadband technologies inquiry. In accordance with Section 0.291(h) of the Commission's rules, the Bureau does not have the authority concerning investigatory proceedings such as notices of inquiry. Action with respect to NARUC's Motion, thus, lies beyond the scope of our delegated authority. V. PROCE DURAL MATTERS A. Regulatory Flexibility 55. We certify that the Regulatory Flexibility Act of 1980 does not apply to this because there will not be a significant impact on a substantial number of small business entities, as defined by Section 601(3) of the Regulatory Flexibility Act. These requirements concern reporting requirements of LECs and interexchange carriers that are engaged in the provision of VDT. These entities are generally large corporations, affiliates of large corporations or are dominant in their fields of operation, and, thus, are not "small entities" as defined by the Act. VI. ORDERING CLAUSES 56. Accordingly, IT IS ORDERED that, pursuant to Sections 1, 2, 4(i), 201- 205, 218-220, and 403 of the Communications Act of 1934, as amended, 47 U.S.C.  151, 152, 154(i), 201-205, 218-220, and 403, and Sections 0.91 and 0.291 of the Commission's rules, 47 C.F.R. 0.91 and 0.291, the policies, rules, and requirements set forth herein are ADOPTED. FEDERAL COMMUNICATIONS COMMISSION Kathleen M.H. Wallman Chief, Common Carrier Bureau Appendix A Comments have been filed by the following: Bell Atlantic Telephone Companies (Bell Atlantic) BellSouth Telecommunications, Inc. (BellSouth) California Cable Television Association (CCTA) Chronicle Publishing Company, the Texas Cable TV Association and The New Jersey Cable Television Association (Chronicle) Colorado Office of Consumer Counsel (Colorado) Comcast Cable Communications, Inc., Cox Enterprises, Inc. and Jones Intercable, Inc. (Comcast) GTE Service Corporation (GTE) MCI Telecommunications Corporation (MCI) National Cable Television Association (NCTA) New York State Department of Public Service (NYDPS) New England Telephone and Telegraph Company, New York Telephone Company (NYNEX) Organization for the Protection and Advancement of Small Telephone Companies (OPASTCO) Southwestern Bell Telephone Company (Southwestern Bell) United States Telephone Association (USTA) US West Communications, Inc. (US West) Wisconsin State Telephone Association (WTA) Reply comments have been filed by the following: Bell Atlantic BellSouth Chronicle Comcast GTE NARUC NCTA Southwestern Bell US West United 57. Appen dix B Approved by OMB 3060-0680 Expires 12/31/96 Est. Avg. Burden Hours Per Response: 15-20 Hours FCC Report 43-09A - Instructions September 1995 Page 1 of 1 This document provides the instructions for FCC Report 43-09A, the ARMIS Video Dialtone Quarterly Report, which was adopted by the Common Carrier Bureau to establish reporting requirements on video dialtone costs for local exchange carriers offering video dialtone service. The instructions consist of the following five sections, which are attached: 1. Reporting Procedures - details on the specific procedures to be followed when submitting this report to the Commission. 2. Reporting Definition - an illustration of the rows and columns to be reported and their definitions. 3. Automated Report Specifications - the detailed automated data processing (ADP) specifications for the automated report to be filed. 4. Paper Report Specifications - the page layout and detailed specifications for the paper report to be filed. 5. COSA Code Table - the list of four letter COSA codes (CO = Company, SA = Study Area). A. Introduction This document contains details on the specific procedures to be followed when submitting FCC Report 43-09A, the ARMIS Video Dialtone Quarterly Report, to the Commission. B. General Information 1. FCC Report 43-09A was adopted by the Common Carrier Bureau to establish the reporting requirements on video dialtone costs for local exchange carriers offering video dialtone service. The report is prescribed for every local exchange carrier that has obtained Section 214 Authorization(s) from the Commission to provide video dialtone trials or commercial services. 2. Affected carriers shall file by June 30, September 30 and December 31 of each year the report for the previous calendar quarter. The initial report will be filed 90 days after the end of the calendar quarter in which a carrier received authorization. (For example, a LEC receiving Section 214 authorization to provide video dialtone service on September 15, 1996, would be required to file its first quarterly report for the quarter ending September 30, 1996 on December 31, 1996. 3. The report shall be filed on a study area (jurisdiction) basis. 4. Carriers seeking proprietary treatment for some data must provide two versions of each paper and automated report. The Confidential Version must contain all the required information (Confidential Treatment Tables/Data Records are provided to identify confidential data). The Public Version should not include data for which the carrier is seeking proprietary treatment. The carrier should prominently label the paper report and the diskette containing information subject to a claim of confidentiality to prevent inadvertent disclosure. 5. Carriers not seeking proprietary treatment for any data should provide only one version of each paper report and diskette, and the paper report and the diskette should be labeled the Unrestricted Version. 6. The Confidential Treatment Tables/Data Records are to be included in all reports but are not a substitute for applying for confidential treatment with this Commission following established Commission procedures. 7. Each report and diskette must be clearly labeled to include the report number, company, study area, period, COSA code, version and submission number. The report number is 43-09A, which identifies the filing as the ARMIS Video Dialtone Quarterly Report. The period identifies the year and quarter covered by the data. See the attached COSA Code Table (CO = Company, SA = Study Area) for a list of companies and their respective COSAs. The version refers to whether the filing is the Confidential, Public or Unrestricted Version. The submission number is defined as follows: Submission 0 is for test data purposes only. Submission 1 is the first submission of a quarter's data. Higher numbers (2, 3, etc.) would be used if needed for successive revisions to correct that quarter's submission. 8. All correspondence and pleadings shall identify the proceeding as Reporting Requirements on Video Dialtone Costs and Jurisdictional Separations for Local Exchange Carriers Offering Video Dialtone Services, AAD No. 95-59. C. Data Items That Are "Not Available" or Are "Withheld" 1. The term "Not Available" is used below to refer only to those items which the Commission ruled are not applicable to a particular row/column or are not required for a particular filing entity. The Confidential Version must contain values for all of the data items except those items which are "Not Available." If, in addition to the required study area reports, a carrier submits a report which combines data for more than one study area, and this report includes a field such as a sum, a ratio, or a percentage that cannot be computed completely and accurately because it relies on another item which the Commission has ruled is a "Not Available" item, then that field is also considered to be "Not Available." 2. The term "Withheld" is used below to refer only to those items for which the carrier has applied for confidential treatment with the Commission and is only applicable to the Public Version. If a field such as a sum, a ratio or percentage relies on an item or items which have been withheld and that field is not also withheld, then it must include the withheld amount. For example, a carrier could withhold the individual values for two of three numbers which are totaled. If the carrier does not also apply for confidential treatment for the total, then that total must be the sum of all three numbers, not just the one which was not withheld. The Public Version must contain values for all of the data items except those items which are "Not Available" or those items which have been "Withheld". 3. See paragraph C.11 in the attached Automated Report Specifications and paragraph C.7 in the attached Paper Report Specifications for data entry conventions for these items. D. Where to File 1. Carriers submitting FCC Report 43-09A should consult the schedule below which details the number of copies required and the location to which those copies should be delivered. 2. Carriers are reminded that they must serve a copy of either the Unrestricted Version or the Public Version of both the paper report and the automated report (diskette) on the FCC contractor for public records duplication. NUMBER OF COPIES FOR CARRIERS NOT SEEKING PROPRIETARY TREATMENT Unre-Unre- Trans- stricted stricted mittal PaperAutomated Letter Report Report (diskette) FCC Secretary 1919 M Street, N.W. Room 222 Washington, D.C. 20554 1 - - FCC Common Carrier Bureau Accounting & Audits Div. 2000 L Street, N.W. Room 812 Washington, D.C. 20554 2 2 2 FCC Common Carrier Bureau Industry Analysis Div. 1919 M Street, N.W. Room 534 Washington, D.C. 20554 1 1 1 International Transcription Service, Inc. (ITS) 2100 M Street N.W. Suite 140 Washington, D.C. 20037 1 1 1 FOR CARRIERS SEEKING PROPRIETARY TREATMENT Confi- Confi- Trans- dential dential Public Public mittal Paper Automated Paper Automated Letter Report Report Report Report (diskette) (diskette) FCC Secretary 1919 M Street, N.W. Room 222 Washington, D.C. 20554 1 - - - - FCC Common Carrier Bureau Accounting & Audits Div. 2000 L Street, N.W. Room 812 Washington, D.C. 20554 3 1 1 2 2 FCC Common Carrier Bureau Industry Analysis Div. 1919 M Street, N.W. Room 534 Washington, D.C. 20554 1 - - 1 1 International Transcription Service, Inc. (ITS) 2100 M Street N.W. Suite 140 Washington, D.C. 20037 1 - - 1 1 E. Footnotes 1. If any data for the current period differs materially from those for the previous period or the corresponding period of the preceding year and the difference is not self-explanatory but was caused by unusual circumstances, the filing carrier must include footnote text to explain the specific circumstances fully. 2. Footnotes must contain full explanations. EXAMPLE: Do not say, "Data are compiled using a more inclusive process than in previous filing." Do say, "Data are compiled using a process that includes xxx, which was not included in previous filings. The impact of including xxx in this row inflates this number by x% over the previous reporting period." 3. If the reporting carrier does not follow the procedures described in the row and column instructions of the attached Report Definition, it must fully explain any deviations from those procedures. EXAMPLE: Do not say, "This value was not calculated pursuant to the instructions." Do, say "This value was calculated using the xxx method rather than the method described in the instructions because..." 4. Fully explain means the footnote will provide enough information for the data user to understand the circumstances. EXAMPLES: Do not say, "Corrected Data." Do say, "$xxxx is changed to $xxxx because ...." Do not say, "Waiver" or Waiver Granted." Do say, "Waiver of Part xx.xxx was granted in CC Docket No. xx-xxx, x FCC Rcd, xxxx (1992) to allow Any Company to .... because...." 5. Do not include explanatory footnotes in the transmittal letter. The Footnote text must be included in the Footnote Text Records and the Footnote Table as specified in the attached Automated Report Specifications and the attached Paper Report Specifications. F. Errata 1. Carriers are under a legal obligation to correct any erroneous data discovered in FCC Report 43-09A. Submissions containing corrected data must include references to indicate which data items were corrected since previous submission. 2. These references must be included in the Erratum Records and the Erratum Table as specified in the attached Automated Report Specifications and the attached Paper Report Specifications. G. Certification 1. Carriers must certify the accuracy of the data submitted in FCC Report 43-09A by including a signed certification statement as the last page of the paper report. 2. The text of the certification statement is included on page 12 of the attached Report Definition. H. Waivers 1. If a carrier determines that it will be unable to provide data required by FCC Report 43-09A, it must file an application for waiver with the Commission following established Commission procedures. All such requests from a carrier should be included in a single application. The application must demonstrate good cause for reporting a different or lower level of detail and indicate how these deficiencies will be corrected. 2. Carriers are strongly encouraged to comply with the requirements. Omission of individual data items or entries, without request for waiver, is unacceptable. One reason that compliance with the full requirements is so important is that omission of any single data entry by any carrier will jeopardize the accuracy of aggregate industry information. I. Public Information 1. The public or unrestricted versions of the paper reports filed as Report 43-09A may be examined by the public from 9:00 to 12:00 p.m. and from 1:00 to 4:00 p.m., Monday through Friday, in Room 812, 2000 L Street, N.W., Washington, D.C. 2. Copies of the public or unrestricted versions of the paper or automated reports filed as FCC Report 43-09A may be obtained from the FCC's contractor for public records duplication, ITS at 2100 M Street, N.W. Suite 140, Washington, D.C. 20037. Parties should contact Wilbur Thomas or ITS (202) 857-3800. For further information regarding these procedures, contact: Ken Ackerman FCC Common Carrier Bureau Accounting and Audits Division (202) 418-0810 Estimated Average Burden Hours Per Response: 15-20 Approved by OMB OMB NUMBER 3060-0680 Expires 12/31/96 SUMMARY This document provides the Report Definition for FCC Report 43-09A, the ARMIS VDT Quarterly Report, and lists all wholly dedicated and shared investment, expense, and revenue data related to local exchange carrier provision of video dialtone service. Carriers must provide these data on a quarterly basis by study area. It contains the following: Pages Table 1 - Video Dialtone Costs and Revenue Data 2 through 4 Row and Column Descriptions 5 through 11 Certification 12 All dollar amounts must be rounded to the nearest thousand dollar amount. All percentage amounts must be rounded to two decimal places. Unless otherwise indicated, line items must reflect the results of video dialtone operations as of the end of the reporting period. Items which need not be reported because they do not apply are designated by "N/A". All other fields must be populated. If there are no dollar amounts related to video dialtone operations for a given field, enter zero. Do not include explanatory notes in the transmittal letter; such notes must be included in the footnote section of the filing. NOTICE: The ARMIS Video Dialtone Quarterly Report collects highly aggregated financial data reflecting accounting results for the investment, expense, and revenue related to the provision of video dialtone service as required by the Video Dialtone Reconsideration Order and in accordance with Part 32 and Responsible Accounting Officer Letter 25 ("RAO Letter 25"). The ARMIS Video Dialtone Quarterly Report specifies information requirements in a consistent format and is essential for the FCC's efforts to monitor video dialtone deployment and its effect on telephone ratepayers. Carriers must file this response upon receiving Section 214 authorizations to provide video dialtone service. Your response is mandatory. Public reporting burden for this collection of information is estimated to average 15-20 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden to the Federal Communications Commission, Records Management Branch, Washington, D.C. 20554. GENERAL INSTRUCTIONS FCC Report 43-09A requires the quarterly reporting of data for 4 columns and for 57 rows. The rows generally correspond to rows contained in FCC Report 43-01 ARMIS Quarterly Report. Some rows may not apply to video dialtone, these rows are designated "N/A". Carriers should place a zero in any cell that have no dollar amounts related to their video dialtone operations. COLUMN INSTRUCTIONS Column b Total - This column contains the amount the carrier reports in each corresponding row of column (b) in its FCC Report 43-01, ARMIS Quarterly Report, for the corresponding quarter and study area. c Shared - This column reports the amount in column (b) that is recorded in the carriers' subsidiary accounting records established to capture the investment, expenses and revenue shared between video dialtone and the provision of other services. d Shared Allocated to VDT - This column reflects the amount of column(c) that is allocated to video dialtone. e Dedicated VDT - This column reports the amount in column (b) that is recorded in the carriers' subsidiary accounting records established to capture the investment, expenses and revenue wholly dedicated to the provision of video dialtone service. ROW INSTRUCTIONS Each row below is a summary of accounts described in Part 32 of the Commission's Rules. Because Part 32 does not require the same level of account detail for Class A and Class B carriers, the instructions listed below indicate, where applicable, different reporting for these carriers. Row Revenues 1010 Basic Local Service - Class A: The total of accounts 5001 through 5060. Class B: The total of account 5000. 1020 Network Access Services - Class A and Class B: The total of accounts 5081 through 5084. 1030 Toll Network Services - Class A: The total of accounts 5100, 5110 and 5121 through 5160, exclusive of account 5129. Class B: The total of accounts 5100. 1040 Miscellaneous - Class A: The total of accounts 5230 through 5250, 5261 through 5264, 5270 and 5280. Class B: The total of accounts 5200 and 5280. 1050 Settlements - The total of accounts 5069, 5129, 5169 and 5269. Carriers which do not retain the Class A accounts throughout separations reporting will include these amounts in the Class B accounts reported on rows 1010, 1030 and 1040. 1060 Uncollectibles - Class A: The total of accounts 5301 and 5302. Class B: The total of account 5300. 1090 Net Revenues - Class A and Class B: The total of rows 1010 through 1050 less row 1060. Expenses 1120 Plant Specific - Class A: The total of accounts 6112 through 6116, 6121 through 6124, 6211 through 6220, 6231, 6232, 6311 through 6362, and 6411 through 6441. Class B: The total of accounts 6110, 6120, 6210, 6220, 6230, 6310, and 6410. 1130 Plant Non-Specific - Class A: The total of accounts 6511, 6512 and 6531 through 6535. Class B: The total of accounts 6510 and 6530. 1140 Customer Operations Marketing - Class A: The total of accounts 6611 through 6613. Class B: The total of account 6610. 1150 Customer Operations Services - Class A: The total of accounts 6621 through 6623. Class B: The total of account 6620. 1160 Corporate Operations - Class A: The total of accounts 6711, 6712, 6721 through 6728 and 6790. Class B: The total of accounts 6710, 6720, and 6790. 1170 Access - Class A and Class B: The balance of account 6540. 1180 Depreciation/Amortization - Class A: The total of accounts 6561 through 6565. Class B: The total of account 6560. 1185 FCC Expense Adjustment - This amount shall contain the net of: (1) expense and other tax items not included above which the Commission has expressly allowed for ratemaking purposes; and (2) expense and other tax items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net allowance and a negative value represents a net disallowance. 1190 Total Operating Expenses - Class A and Class B: The total of rows 1120 through 1185. Other Operating Items 1290 Other Operating Income/Losses - Class A: This amount shall contain the net of accounts 7110 through 7160 and 7990. Class B: This amount shall contain the net of accounts 7100 and 7990. A positive value represents income and a negative value represents loss. Non-operating Items 1320 Income Effects of Jurisdictional Ratemaking Differences (Net) - Class A and Class B: The balance of account 7910. A positive value represents an increase to net income and a negative value represents a decrease to net income. 1330 Extraordinary Items - Class A: The total of accounts 7610 through 7640. Class B: The total of account 7600. Amounts excluded from ratemaking are removed in row 1370. A positive value represents an income credit and a negative value represents an income charge. 1340 Allowance for Funds Used During Construction - Class A: The balance of account 7340. Amounts excluded from ratemaking are removed in row 1370. Class B: Not applicable. 1350 Special Charges - Class A: The balance of account 7370. Amounts excluded from ratemaking are removed in row 1370. Class B: Not applicable. 1360 All Other Non-Operating Items - Class A: The total amount of accounts 7310 through 7330, 7350 and 7360. Class B: The balance of account 7300. Amounts excluded from ratemaking are removed in row 1370. A positive value represents income and a negative value represents a loss. 1370 FCC Non-Operating Adjustment - This amount shall contain the net of: (1) non- operating items not included above which the Commission has expressly allowed for ratemaking purposes; and (2) non-operating items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net allowance and a negative value represents a net disallowance. 1390 Total Non-Operating Items - Class A and Class B: The total of rows 1350 and 1370 less rows 1320, 1330, 1340 and 1360. Other Taxes 1410 State and Local - Class A: The total of accounts 7230 and the appropriate portion of account 7250 for column (b). Class B: Follow Class B instructions using relevant portion of account 7200. 1420 Other State and Local - The total of account 7240 for column (b). 1490 Total Other Taxes - The total of rows 1410 and 1420. Federal Income Taxes 1590 Federal Income Taxes - Class A: For column (b), enter the total of account 7220 and the appropriate portion of account 7250 minus the appropriate amount of amortization in account 7210. Class B: Follow the instructions of Class A using the relevant portion of account 7200. Plant in service 1620 Support Plant - Class A: The total of accounts 2111 through 2124. Class B: The total amount in account 2110. 1630 Operator Systems Equipment - Class A and Class B: The balance of account 2220. 1640 Central Office Equipment-Switching - Class A: The balance of accounts 2211 through 2215. Class B: The balance of account 2210. 1650 Central Office Equipment-Transmission - Class A: The total of accounts 2231 and 2232. Class B: The balance in account 2230. 1660 Cable and Wire Facilities-Total - Class A: The total of accounts 2411 through 2441. This amount also equals the total of rows 1661, 1662 and 1663. Class B: The balance in account 2410. 1661 Cable and Wire Facilities-Metallic Cable - Class A: The total of the metallic subsidiary record categories in accounts 2421, 2422, 2423, 2424, 2425 and 2426. Class B: Not applicable. 1662 Cable and Wire Facilities-Non-Metallic Cable - Class A: The total of the non- metallic subsidiary record categories in accounts 2421, 2422, 2423, 2424, 2425 and 2426. Class B: Not applicable. 1663 Cable and Wire Facilities-Other - Class A: The total of accounts 2411, 2431, and 2441. Class B: Not applicable. 1670 Information Origination/Termination Equipment - Class A: The total of accounts 2311 through 2362. Class B: The balance of account 2310. 1680 Amortizable Assets - Class A: The total of accounts 2681, 2682 and 2690. Class B: The total of accounts 2680 and 2690. 1690 Total Plant - Class A and Class B: The total of rows 1620, 1630, 1640, 1650, 1660, 1670 and 1680. Other Investments 1705 Other Jurisdictional Assets-Net - Class A and Class B: The balance of Account 1500. A positive value represents an increase to assets and a negative value represents a decrease to assets. 1710 Property Held for Future Telecommunications Use - Class A and Class B: The balance of account 2002. 1720 Telecommunications Plant Under Construction - Class A and Class B: The total of accounts 2003. Amounts excluded from ratemaking are removed in row 1780. 1730 Plant Acquisition Adjustment - Class A and Class B: The balance of account 2005. Amounts excluded from ratemaking are removed in row 1780. 1740 Investment in Nonaffiliated Companies - Class A and Class B: The balance of account 1402. The amount directly related to Class B Rural Telephone Back Stock shall be included in the rate base. Amounts excluded from ratemaking are removed in row 1780. 1750 Other Deferred Charges - Class A and Class B: The total of accounts 1437, 1438 and 1439. Amounts excluded from ratemaking are removed in row 1780. 1760 Inventories - Class A and Class B: The balance of account 1220. 1770 Cash Working Capital - This amount equals that portion of investment required to meet current expenses. The calculation of this amount shall take into account revenue and expense items which are received or paid for before the service is rendered and expense items received or disbursed after the service is rendered. This amount must be developed pursuant to CC Docket 86-497. 1780 FCC Investment Adjustment - This amount shall contain the net of: (1) investment items not included above which the Commission has expressly allowed for ratemaking purposes; and (2) investment items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net asset allowance and a negative value represents a net disallowance. 1790 Total Other Investment - Class A and Class B: The total of rows 1705 through 1780. Reserves 1820 Accumulated Depreciation - Class A and Class B: The total of accounts 3100 and 3200. 1830 Accumulated Amortization - Class A: The total of accounts 3410, 3420, 3500 and 3600. Class B: The total of accounts 3400, 3500 and 3600. 1840 Deferred Federal Income Taxes - Class A and Class B: The total of accounts 4100 and 4340. 1850 Customer Deposits - Class A and Class B: The balance of account 4040. 1870 Other Deferred Credits - Class A and Class B: The balance of account 4360. Amounts excluded from ratemaking are removed in row 1885. 1880 Other Jurisdictional Liabilities and Deferred Credits-Net - Class A and Class B: The balance of accounts 4310 and 4370. 1885 FCC Reserve Adjustment - This amount shall contain the net of: (1) reserve items not included above which the Commission has expressly included for ratemaking purposes; and (2) reserve items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net reserve allowance and a negative value represents a net reserve disallowance. 1890 Total Reserves - Class A and Class B: The total of rows 1820 through 1885. CERTIFICATION I certify that I am an officer of ___________________________________________________; that I have examined the foregoing report and that to the best of my knowledge, information, and belief, all statements of fact contained in this report are true and that said report is an accurate statement of the affairs of the above named respondent in respect to the data set forth herein for the period from ____________________ to __________________. PRINTED NAME POSITION SIGNATURE DATE (Persons making willful false statements in this report form can be punished by fine or imprisonment under the Communications Act, 47 U.S.C. 220(e).) CONTACT PERSON TELEPHONE NUMBER A. Introduction This document contains the detailed automated data processing (ADP) specifications for the automated report to be filed as FCC Report 43-09A, the ARMIS Video Dialtone Quarterly Report. B. General Format and Media 1. All data must be submitted on 3.5 inch double-sided high density IBM-PC compatible diskettes. 2. All files must be coded in ASCII. 3 See sections B and C on pages 1 and 2 of the accompanying Reporting Procedures for a discussion of the Confidential Version, the Public Version, and the Unrestricted Version of this report and for a definition and discussion of data items that are "Not Available" or are "Withheld." 4. The file name for each file has seven components: a. the four letter COSA code (CO = Company, SA = Study Area, see attached COSA Code Table for a list of companies and their respective COSAs). b. the last two digits of the year which is covered by the data. c. the letter "V". d. the number of the quarter which is covered by the data. e. a decimal point. f. the letter "P", "C", or "U" to indicate whether this is the Public version, the Confidential version, or the only (Unrestricted) version since all data is non-confidential. g. two digits (zero filled) for the submission number. Submission 0 is for test data purposes only. Submission 1 is for the first submission of a quarter's data. Higher numbers (2,3,etc.) would be used if needed for successive revisions to correct that quarter's submission. For example, the file name for the Unrestricted Version of the initial quarterly report data file to be submitted by Illinois Bell to cover the first quarter of calendar year 1995, would be LBIL95V1.U01: LBIL COSA for Illinois Bell 95 Data for calendar year 1995 V Video Dialtone Report Data File 1 Data for the first quarter . Decimal point U Unrestricted version 01 First submission of this quarter's data 5. A separate file must be prepared for each report. More than one file can be placed on the same diskette, as long as they cover the same period, version, and submission number. C. Data Entry Conventions 1. If an entry is to be a subtraction, indicate so by placing a minus sign in the column, immediately preceding the numeric data, e.g., use -4, NOT - 4 or (4). 2. Begin each data record in column 1 and make each record the proper length as specified in the accompanying record layouts. Commas are used as delimiters between fields. All numeric fields are right justified and space filled, e.g. use 123, NOT 123 . All non-numeric fields are enclosed in double quotation marks and are left justified and space filled within these quotation marks, e.g. use "John Doe ". 3. Give each record a unique record number, beginning with 1001 and incrementing by one, with no numbers skipped. 4. Do NOT include "$" or "%" or embedded commas, decimal points, spaces, quotes or other formatting characters in any numeric data fields, except for row number and percentage field, which will include a decimal point but not a percent sign. 5. In any numeric data field designated by N/A, enter -99999. If a "Public Version" diskette is filed, enter -88888 in any numeric data field for which data are "Withheld". DO NOT override N/As. If a reporting carrier wishes to apply data to a field containing an N/A, the carrier should enter as a footnote to the field, the amount(s) and an explanation. The amount(s) must not be entered in the N/A's field. All other fields must be populated. If there are no dollar amounts related to video dialtone operations for an open field, enter zero. These entries must be formatted according to the format rules for the particular data field; e.g., in the percentage fields, -99999 would be entered as -99999.00. D. Rounding Conventions 1. As specified in the accompanying Report Definition, all monetary figures must be rounded to the nearest thousand dollars. 2. All percentage amounts must be entered in percent and must be rounded to 2 decimal places. Example: 23.70516 should be entered as 23.71 E. Footnotes 1. If any data for the current period differs materially from those for the previous period and the difference is not self-explanatory but was caused by unusual circumstances not explained in a previous report, then include footnote text to explain the specific circumstances. 2. If the reporting carrier does not follow the procedures described in the row and column instructions of the attached Report Definition, it must explain any deviations from those procedures in an explanatory fonote. Such footnotes must provide detailed explanations of the procedures actually used by the carrier and its specific reasons for deviating from procedures prescribed by the Commission's Rules. This provision should not be interpreted to mean that deviations from the prescribed rules will automatically be approved by the Commission. 3. Footnotes must be included in the footnote text record(s) of the automated report. F. Errata 1. Carriers are under a legal obligation to correct any erroneous data discovered in FCC Report 43-09A. Submission containing corrected data must include references to indicate which data items were corrected since previous submission. 2. These references must be included in the erratum record(s) of the automated report. G. Data Record Descriptions The seven data record types are described below. See pages 6 through 15 for record layouts. The automated file will consist of the following record Types: Record Type H1 Header Record One Type H1 record per file. The first record of each file. Contains identifying data. See page 6 for record layout. Record Type L1 Label Record One Type L1 record per file. The second record of each file. Contains report number, carrier name, study area name, etc. See page 7 for record layout. Record Type I1 Costs and Revenue 57 Type I1 records per file. Data Record One record for each of the 57 rows shown on Pages 2-4 & 6-11 of the accompanying Report Definition. Each record contains data values reflecting accounting results prepared on a cumulative basis for the investment, expense and revenue related to the provision of video dialtone service. See page 8 for record layout Record Type C1 Confidential One or more Type C1 records per Treatment Record file. Contains information to identify the data for which the carrier is seeking confidential treatment or to verify that the carrier is not seeking any confidential treatment. See pages 9 & 10 for record layout. Record Type F1 Footnote Record One or more Type F1 records per file. Contains explanatory footnote text. See pages 11 & 12 for record layout. Record Type E1 Erratum Record Zero Type E1 records in the first submission of a quarter's data. One or more Type E1 records per file in revisions filed to correct that quarter's submission. Contains information to identify the data which was corrected in the submission. See pages 13 & 14 for record layout. Record Type T1 Trailer Record One Type T1 record per file. The last record of each file. Contains contact person, etc. See page 15 for record layout. FCC Report 43-09A - Automated Report Specifications September 1995 Page 6 of 15 RECORD TYPE H1 - HEADER RECORD Field Item Example Position Description 1 Record Number 1001 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. (see attached COSA Code Table) Format: Include quotation marks. 3 Record Type "H1" 13-16 Always contains the letter H capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 File Name "LBIL95V1.U01"18-31 The name of the ASCII file. Format: See page 1, paragraph B.4 above. Include quotation marks. 5 Year 1995 33-36 The year covered by the data. 6 Quarter # 1 38 The quarter number covered by the data on a cumulative basis. 1 for January to March 2 for April to June 3 for July to September 7 Data Entry Date 19950513 40-47 The date on which the data were last entered or revised. Format: YYYYMMDD. 8 Version "U" 49-51 The version letter (P, C or U) capitalized (for Public, Confidential or Unrestricted) Format: Include quotation marks. 9 Submission # 1 53-54 0 for test data purposes only. 1 or first submission of a quarter's data. Higher numbers (2, 3, etc.) would be used if needed for successive revisions to correct that quarter's submission. Format: Right justified and space filled. 10 End of Record Code "XQ" 56-59 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. The ruler lines (123456789 etc.) included below and following with sample records are included only to assist the reader. Do not include ruler lines as records in the electronic filing. ___________________________________________________________ 1 2 3 4 5 . . . . . Ruler Line 12345678901234567890123456789012345678901234567890123456789 . . . . . Ruler line Sample record: 1001,"LBIL","H1","LBIL95V1.U01",1995,1,19950513,"U", 1,"XQ" FCC Report 43-09A - Automated Report Specifications September 1995 Page 7 of 15 RECORD TYPE L1 - LABEL RECORD Field Item Example Position Description 1 Record Number 1002 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "L1" 13-16 Always contains the letter L capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Report Number "FCC REPORT 43-09A" 18-36 Always contains "FCC REPORT 43-09A" capitalized. Format: Include quotation marks. 5 Carrier "Illinois Bell " 38-69 Name of the carrier. (spaces until pos. 69) Format: Left justified and space filled. Include quotation marks. 6 Study Area "Illinois " 71-92 Name of the study area. Format: Left justified and space filled. Include quotation marks. 7 Period Covered "Jan 1995 to Mar 1995" 94-115 Period covered by the data. Format: "mmm yyyy to mmm yyyy" Include quotation marks. 8 End of Record Code "XQ" 117-120 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 9 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567890123 Sample record: 1002,"LBIL","L1","FCC REPORT 43-09A","Illinois Bell ","Illinois ", 1 1 1 9 0 1 2 456789012345678901234567890 Continuation of sample record: "Jan 1995 to Mar 1995","XQ" FCC Report 43-09A - Automated Report Specifications September 1995 Page 8 of 15 RECORD TYPE I1 - VIDEO DIALTONE COSTS AND REVENUE DATA RECORD Field Item Example Position Description 1 Record Number 1009 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "I1" 13-16 Always contains the letter I capitalized and the number 1 with no space between them Format: Include quotation marks. 4 Row Number 1090.0 18-23 Row number as identified on pages 2-4 and 6-11 of the accompaning Report Definition. Valid range: 1010.0 to 1890.0 Format: Right justified and space filled. 5 Column (b) data 31219 25-33 This field contains the data corresponding to column (b) as shown on Pages 2-4 and 5 of the accompanying Report Definition. Format: Right justified and space filled. Enter -99999 in integer rows where a field is designated by N/A. All other fields must be populated. If there are no data applicable to an open field enter zero. Enter -88888 in integer rows on the "public version" diskette to indicate that confidential treatment has been requested. 6 Column (c) data 56890 35-43 Column (c) data Format: See Field 5 above. 7 Column (d) data 1521 45-53 Column (d) data Format: See Field 5 above. 8 Column (e) data 41521 55-63 Column (e) data Format: See Field 5 above. 9 End of Record Code "XQ" 65-68 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. Footnote records are needed if any data for the current period differ materially from those for the previous period or the corresponding period of the preceding year and the difference is not self-explanatory but was caused by unusual circumstances. Footnote records are also needed if the procedures described in the row and column instructions are not followed. The carrier must include footnote text to fully explain the specific circumstances or any deviations from the procedures. See section D of the accompanying Reporting Procedures for a discussion of footnotes. Add one or more Type F1 record(s) after the remaining Type I1 and C1 records. 1 2 3 4 5 6 12345678901234567890123456789012345678901234567890123456789012345 678 Sample record: 1009,"LBIL","I1",1090.0, 31219, 56890, 1521, 41521,"XQ" FCC Report 43-09A - Automated Report Specifications September 1995 Page 9 of 15 RECORD TYPE C1 - CONFIDENTIAL TREATMENT RECORD Field Item Example Position Description 1 Record Number 1060 1-4 The sequential number of this record (for this record) within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "C1" 13-16 Always contains the letter C capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Record Number 1009 18-21 This field contains the record number (for the confidential of the record which contains the data) data for which the carrier is seeking confidential treatment. If the request is for the entire column(s) or the entire submission, use 9999. If no confidential treatment is being requested, then use 0. Format: Right justified and space filled. 5 Table Number "I " 23-28 This field contains the table number (Roman numerals)of the table in which the the confidential data appear. If the request is for the entire submission, enter "ZZZZ". If no confidential treatment is being requested then enter " ". Format: Include quotation marks. Left justified and space filled. 6 Row Number 1090.0 30-35 This field contains the row number of the row which contains the confidential data as identified in the accompanying Report Definition. If the request is for the entire column(s), an entire table or the entire submission, enter 9999.0. If no confidential treatment is being requested then use 0.0. Format: Right justified and space filled, with one decimal place. 7 Column Label "C " 37-40 This field contains the column letter of the confidential data as identified in the accompanying Report Definition. If the request is for an entire row, an entire table, or the entire submission, enter "ZZ". If the request is for more than one column but less than the entire row, then populate this field and as many as needed of fields 8 thru 26. If no confidential treatment is requested, then enter " " in all of fields 7 thru 26. Format: Include quotation marks. Left justified and space filled. 8 Second Column Label "C " 42-45 ..... 9 Third Column Label "D " 47-50 . Fields 8 thru 26 are similar . . to Field 7 and are used . . when the request is for . . the same row and more than . . one column. 26 Twentieth Col. Label " " 132-135 ..... Otherwise, enter " ". FCC Report 43-09A - Automated Report Specifications September 1995 Page 10 of 15 RECORD TYPE C1 - CONFIDENTIAL TREATMENT RECORD (continued) Field Item Example Position Description 27 End of Record Code "XQ" 137-140 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 9 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567890123456 Sample records: 1060,"LBIL","C1",1009,"I ",1090.0,"B ","C "," "," "," "," "," "," "," "," "," "," ", 1061,"LBIL","C1",9999,"I ",9999.0,"B "," "," "," "," "," "," "," "," "," "," "," ", 1062,"LBIL","C1",1018,"I ",1190.0,"ZZ"," "," "," "," "," "," "," "," "," "," "," ", - OR - 1060,"LBIL","C1", 0," ", 0.0," "," "," "," "," "," "," "," "," "," "," "," ", __ 1 1 1 1 1 9 0 1 2 3 4 78901234567890123456789012345678901234567890 Continuation of sample records: " "," "," "," "," "," "," "," ","XQ" " "," "," "," "," "," "," "," ","XQ" " "," "," "," "," "," "," "," ","XQ" - OR - " "," "," "," "," "," "," "," ","XQ" FCC Report 43-09A - Automated Report Specifications September 1995 Page 11 of 15 RECORD TYPE F1 - FOOTNOTE TEXT RECORD Field Item Example Position Description 1 Record Number 1063 1-4 The sequential number of this record (for this record) within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "F1" 13-16 Always contains the letter F capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Record Number 1003 18-21 This field contains the record number of (for the footnoted the record which contains the footnoted data) data. If the footnote pertains to the entire column(s), an entire table, or the entire submission, use 9999. Format: Right justified and space filled. 5 Table Number "I " 23-28 This field contains the table number (Roman numerals) of the table in which the footnoted data appear. If the footnote pertains to an entire table or the entire submission, use "ZZZZ". Format: Include quotation marks. Left justified and space filled. 6 Row Number 1090.0 30-35 This field contains the row number of the row which contains the footnoted data as identified in the accompanying Report Definition. If the footnote pertains to the entire column(s), an entire table, or the entire submission, enter 9999.0. Format: Right justified and space filled, with one decimal place. 7 Column Label "ZZ" 37-40 This field contains the column letter(s) of the footnoted data as identified in the accompanying Report Definition. If the footnote pertains to an entire row, an entire table, or the entire submission, enter "ZZ". Format: Include quotation marks. Left justified and space filled. 8 Footnote Number 1 42-44 The number of this particular footnote. Valid range: 1 to 999. Format: Right justified and space filled. 9 Sequence Number 1 46-47 The sequence number of the record within the footnote. In other words, the order of the specific record in the sequence of records which, when combined, will provide the entire footnote. Valid range: 1 to 99. Format: Right justified and space filled. 10 Footnote Text "Footnote text " 49-105 The text of the footnote or of the (Spaces until pos. 105) continuation line. Footnote text must be explained fully. Format: Include quotation marks at the beginning and end of this field and left justify within these quotation marks. FCC Report 43-09A - Automated Report Specifications September 1995 Page 12 of 15 RECORD TYPE F1 - FOOTNOTE TEXT RECORD (continued) Field Item Example Position Description 11 End of Record Code "XQ" 107-110 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. Footnote records are needed if any data for the current period differ materially from those for the previous period or the corresponding period of the preceding year and the difference is not self-explanatory but was caused by unusual circumstances. Footnote records are also needed if the procedures described in the row and column instructions are not followed. The carrier must include footnote text to fully explain the specific circumstances or any deviations from the procedures. See section D of the accompanying Reporting Procedures for a discussion of footnotes. 1 1 1 2 3 4 5 6 7 8 9 0 1 12345678901234567890123456789012345678901234567890123456789012345 678901234567890123456789012345678901234567890 Sample records: 1063,"LBIL","F1",1009,"I ",1090.0,"ZZ", 1, 1,"Footnote text for footnote 1 ","XQ" 1064,"LBIL","F1",1009,"I ",1090.0,"ZZ", 1, 2,"continuation text for footnote 1 ","XQ" 1065,"LBIL","F1",1009,"I ",1090.0,"ZZ", 1, 3,"last line of footnote 1 ","XQ" 1066,"LBIL","F1",1018,"I ",1190.0,"B ", 2, 1,"Footnote 2 pertains to column B of Table I row 1190.0 ","XQ" 1067,"LBIL","F1",9999,"I ",9999.0,"C ", 3, 1,"Footnote 3 pertains to all rows of Table I column C ","XQ" FCC Report 43-09A - Automated Report Specifications September 1995 Page 13 of 15 RECORD TYPE E1 - ERRATUM RECORD Field Item Example Position Description 1 Record Number 1068 1-4 The sequential number of this record (for this record) within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "E1" 13-16 Always contains the letter E capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Record Number 1009 18-21 This field contains the record number (for the corrected of the record which contains the data) data which were corrected in this submission. If the entire column(s), an entire table, or the entire submission was corrected, use 9999. Format: Right justified and space filled. 5 Table Number "I " 23-28 This field contains the table number (Roman numerals) of the table in which the corrected data appear. If an entire table or submission was corrected, use "ZZZZ". Format: Include quotation marks. Left justified and space filled. 6 Row Number 1090.0 30-35 This field contains the row number of the of the row which contains the corrected data as identified in the accompanying Report Definition. If the entire column(s), an entire table, or the entire submission was corrected, enter 9999.0. Format: Right justified and space filled, with one decimal place. 7 Column Label "ZZ" 37-40 This field contains the column letter of the corrected data as identified in the accompanying Report Definition. If an entire row, an entire table, or the entire submission was corrected, enter "ZZ". If more than one column but less than the entire row was corrected, then populate this field and as many as needed of fields 8 thru 26. Format: Include quotation marks. Left justified and space filled. 8 Second Column Label "B " 42-45 ..... 9 Third Column Label "C " 47-50 . Fields 8 thru 26 are similar . . to Field 7 and are used . . when the correction is in . . the same row and more than . . one column. 26 Twentieth Col. Label " " 132-135 ..... Otherwise, enter " ". 27 Footnote Number 1 137-139 This field contains the footnote number that explains the correction. If there is no footnote, use a zero. Format: Right justified and space filled. FCC Report 43-09A - Automated Report Specifications September 1995 Page 14 of 15 RECORD TYPE E1 - ERRATUM RECORD (continued) Field Item Example Position Description 28 End of Record Code "XQ" 141-144 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 9 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567890123456 Sample records: 1068,"LBIL","E1",1009,"I ",1090.0,"ZZ"," "," "," "," "," "," "," "," "," "," "," ", 1069,"LBIL","E1",1018,"I ",1190.0,"B ","C "," "," "," "," "," "," "," "," "," "," ", 1070,"LBIL","E1",9999,"I ",9999.0,"C "," "," "," "," "," "," "," "," "," "," "," ", 1 1 1 1 1 90 1 2 3 4 789012345678901234567890123456789012345678901234 Continuation of sample records: " "," "," "," "," "," "," "," ", 1,"XQ" " "," "," "," "," "," "," "," ", 2,"XQ" " "," "," "," "," "," "," "," ", 3,"XQ" FCC Report 43-09A - Automated Report Specifications September 1995 Page 15 of 15 RECORD TYPE T1 - TRAILER RECORD Field Item Example Position Description 1 Record Number 1071 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "T1" 13-16 Always contains the letter T capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Contact Person "John Doe " 18-59 The name of the person to contact (spaces until pos. 59) if there are questions about the report. Format: Include quotation marks. 5 Telephone # "(202) 555-1212 x123 " 61-82 The Contact Person's telephone number. Format: Include quotation marks. 6 End of Record Code "XQ" 84-87 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567 Sample record: 1071,"LBIL","T1","John Doe ","(202) 555-1212 x123 ","XQ" A. Introduction This document contains the page layout and detailed specifications for the paper report to be filed as FCC Report 43-09A, the ARMIS Video Dialtone Quarterly Report. B. General Instructions 1. See sections B and C on pages 1 and 2 of the accompanying Reporting Procedures for a discussion of the Confidential Version, the Public Version, and the Unrestricted Version of this report and for a definition and discussion of data items that are "Not Available" or are "Withheld." 2. The ruler lines included on the page layouts with the column titles are included only to assist the reader. Do not include ruler lines as lines in the report. 3. The paper report must be printed on 8 1/2 inch by 11 inch paper. For ease of preparation, an original may be produced on larger paper and reduced to this size for submission. Copies filed must be legible and permanent, in black ink. The report may be printed in portrait mode (8 1/2 inches across the top of the page) or landscape mode (11 inches across the top of the page). In portrait mode, the printing should not be smaller than 17 characters per inch and 8 lines per inch; in landscape mode, the printing should not be smaller than 15 characters per inch and 10 lines per inch. C. Data Entry Conventions 1. If an entry is to be a subtraction, indicate so by placing a minus sign in the column immediately preceding the numeric data, e.g., use -4 or (4), NOT - 4. 2. Items that need not be reported because they do not apply are designated by N/A. If a "Public Version" report is filed, enter W/H in any numeric data field for which data are "Withheld". DO NOT override N/As. If a reporting carrier wishes to apply data to a field containing an N/A, the carrier must enter, as a footnote to the field, the amount(s) and an explanation. All other fields must be populated. If there are no data applicable to an open field enter zero. 3. Unless otherwise indicated, line items must reflect the results of video dialtone operations as of the end of the reporting period. D. Rounding Conventions 1. As specified in the accompanying Report Definition, all dollar amounts must be rounded to the nearest thousand dollars. 2. All percentage amounts must be entered in percent and must be rounded to two places. Example: 23.70561 should be entered as 23.71 E. Footnotes 1. If any data for the current period differs materially from those for the previous period and the difference is not self-explanatory but was caused by unusual circumstances not explained in a previous report, then include footnote text to explain the specific circumstances. 2. If the reporting carrier does not follow the procedures described in the row and column instructions of the attached Report Definition, it must explain any deviations from those procedures in an explanatoy footnote. Such footnotes must provide detailed explanations of the procedures actually used by the carrier and its specific reasons for deviating from procedures prescribed by the Commission's Rules. This provision should not be interpreted to mean that deviations from the prescribed rules will automatically be approved by the Commission. 3. Footnotes must be included in the footnote table(s) of the paper report, not on individual table pages. F. Errata 1. Carriers are under a legal obligation to correct any erroneous data discovered in FCC Report 43-09A. Submission containing corrected data must include references to indicate which data items were corrected since previous submission. 2. These references must be included in the erratum table(s) of the paper report. E. Page Layouts 1. The page layout for this report is illustrated in the Forms Section of the accompanying Report Definition. 2. The following note must appear at the bottom of all pages, where applicable. THE COMPANY HAS REQUESTED CONFIDENTIAL TREATMENT FOR SOME DATA ON THIS PAGE. SEE THE CONFIDENTIAL TREATMENT TABLE FOR SPECIFIC INFORMATION. 4. The Paper Report will consist of the following pages in order: Illustrated in Paper Report Specs. on Page The Cover Page 4 Illustrated in Report Definition Forms on Page Table 1 - Video Dialtone Costs and Revenue Data 2 through 4 Illustrated in Paper Report Specs. on Page The Confidential Treatment Table (at least one page and as many pages as needed) 5 The Footnote Table (at least one page and as many pages as needed) 6 The Erratum Table (for submission number 2 or higher, as many as needed) 7 The Certification Page 8 FCC Report 43-09A - Paper Report Specifications Sept. 1995 Page 4 of 8 FCC Report 43-09A Approved by OMB September 1995 3060-0680 Expires 12/31/96 Estimated Avg. Burden Per Response: 15-20 Hrs FEDERAL COMMUNICATION COMMISSION WASH INGTON, D.C. 20554 ARMI S Video Dialtone Quarterly REPO RT For the ______ Quarter of 19 Name of Company: Address of Company: FCC Report 43-09A is prescribed for every local exchanage carrier that has obtained Section 214 Authorization(s) from the Commission to provide video dialtone trials or commercial services. The ARMIS Video Dialtone Quarterly Report collects highly aggregated financial data reflecting accounting results for the investment, expense, and revenue related to the provision of video dialtone service as required by the Video Dialtone Reconsideration Order and in accordance with Part 32 and Responsible Accounting Officer Letter 25 ("RAO Letter 25"). The ARMIS Video Dialtone Quarterly Report specifies information requirements in a consistent format and is essential for the FCC's efforts to monitor video dialtone deployment and its effect on telephone ratepayers. Carriers must file this response upon receiving Section 214 authorizations to provide video dialtone service. Your response is mandatory. Public reporting burden for this collection of information is estimated to average 15-20 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden to the Federal Communications Commission, Records Management Branch, Washington, D.C. 20554. FCC REPORT 43-09A Approved by OMB ARMIS VDT QUARTERLY REPORT 3060-0680 Expires 12/31/96 COMPANY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx VERSION STUDY AREA: xxxxxxxxxxxxxxxxxxxx SUBMISSION x PERIOD: From mmm yyyy to mmm yyyy CONF. TREATMENT TABLE COSA: xxxx PAGE 1 OF x CONFIDENTIAL TREATMENT TABLE Table Row Column(s) ----------- ----------------------------------------------------------- (a) (b) (c) xxxx 1234.1 xx,xx,xx,xx, x, x, x, x, x, x, x, x, x, x, x, x,... Ruler Line sample entries: I 1090.0 B ,C , I ALL B I 1190.0 ALL THE COMPANY HAS REQUESTED CONFIDENTIAL TREATMENT FOR THE ABOVE DATA IN THIS REPORT. -OR- THE COMPANY HAS NOT REQUESTED CONFIDENTIAL TREATMENT FOR ANY DATA IN THIS REPORT. FCC REPORT 43-09A Approved by OMB ARMIS VDT QUARTERLY REPORT 3060-0680 Expires 12/31/96 COMPANY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx VERSION STUDY AREA: xxxxxxxxxxxxxxxxxxxx SUBMISSION x PERIOD: From mmm yyyy to mmm yyyy FOOTNOTE TABLE COSA: xxxx PAGE 1 OF x FOOTNOTE TABLE Table Row Col FN# Footnote ---- ------ --- -- ------------------------------------------------------- (a) (b) (c) (d) (e) xxxx 1234.1 xxx 12 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ... Ruler Line sample entries: I 1090.0 ALL 1 Footnote text for footnote 1 continuation text for footnote 1 last line of footnote 1 I 1190.0 B 2 Footnote 2 pertains to column B of Table I row 1190.0 I ALL C 3 Footnote 3 pertains to all rows of Table I column C -OR- THERE ARE NO FOOTNOTES FOR THIS SUBMISSION. FCC REPORT 43-09A Approved by OMB ARMIS VDT QUARTERLY REPORT 3060-0680 Expires 12/31/96 COMPANY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx VERSION STUDY AREA: xxxxxxxxxxxxxxxxxxxx SUBMISSION x PERIOD: From mmm yyyy to mmm yyyy ERRATUM TABLE COSA: xxxx PAGE 1 OF x ERRATUM TABLE TableRow Column(s) FN# ---- ------ ----------------------------------------------- --- (a) (b) (c) (d) xxxx 1234.1 xx,xx,xx,xx, x, x, x, x, x, x, x, x, x, x, x, x, 12 ... Ruler Line sample entries: I 1090.0 ALL 1 I 1190.0 B 2 I ALL C 3 THE ABOVE DATA HAVE BEEN CORRECTED IN THIS SUBMISSION. SEE THE FOOTNOTE TABLE FOR FOOTNOTES WHERE APPLICABLE. CERTIFICATION I certify that I am an officer of ; that I have examined the foregoing report and that to the best of my knowledge, information, and belief, all statements of fact contained in this report are true and that said report is an accurate statement of the affairs of the above named respondent in respect to the data set forth herein for the period from to . PRINTED NAME POSITION SIGNATURE DATE (Persons making willful false statements in this report form can be punished by fine or imprisonment under the Communications Act, 47 U.S.C. 220(e).) CONTACT PERSON TELEPHONE NUMBER Company and Study Area Code (COSA) Table September 1995 Page 1 of 6 DIVESTED BOC INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code Ameritech AMTR 1. Illinois Bell - Illinois LBIL 2. Indiana Bell - Indiana NBIN 3. Michigan Bell - Michigan MBMI 4. Ohio Bell - Ohio OBOH 5. Wisconsin Bell - Wisconsin WTWI Bell Atlantic Network Serv. Corp. BATR 1. the Chesapeake and Potomac Telephone Companies CPTC 1. C&P (D.C.) - Dist. of Columbia CDDC 2. C&P of Maryland - Maryland CMMD 3. C&P of Virginia - Virginia CVVA 4. C&P of West Virginia - West Virginia CWWV 2. Bell of PA and Diamond State PDTC 5. Diamond State Telephone - Delaware DSDE 6. Bell of Pennsylvania - Pennsylvania PAPA 7. New Jersey Bell - New Jersey NJNJ BellSouth Telecommunications, Inc. BSTR - Florida SBFL - Georgia SBGA - North Carolina SBNC - South Carolina SBSC - Alabama SCAL - Kentucky SCKY - Louisiana SCLA - Mississippi SCMS - Tennessee SCTN NYNEX NXTR 1. New England Telephone NETC - Maine NEME - Massachusetts NEMA - New Hampshire NENH - Rhode Island NERI - Vermont NEVT 2. New York Telephone - New York NYNY Pacific Telesis PTTR 1. Pacific Bell - California PTCA 2. Nevada Bell - Nevada PTNV Company and Study Area (COSA) List September 1995 Page 2 of 6 DIVESTED BOC INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code Southwestern Bell Telephone Co. SWTR - Arkansas SWAR - Kansas SWKS - Missouri SWMO - Oklahoma SWOK - Texas SWTX all except Kansas SWAG U.S. West Communications, Inc. USTR - Arizona MSAZ - Colorado MSCO - Idaho MSID - Montana MSMT - New Mexico MSNM - Utah MSUT - Wyoming MSWY - Iowa NWIA - Minnesota NWMN - Nebraska NWNE - North Dakota NWND - South Dakota NWSD - Idaho PNID - Oregon PNOR - Washington PNWA Total Divested Bell Operating Companies TBOC Company and Study Area (COSA) List September 1995 Page 3 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code Alascom, Inc. - Alaska AKAK Cincinnati Bell Telephone - Ohio & Kentucky CBTC Citizens Telecom CTTC 1. Citizens Utilities - California CUCA 2. Citizens Telcom of New York - New York CTNY - Upstate CTUP - Red Hook CTRH - Western Counties CTWC 3. Citizens Telcom of West Virg. - Contel/West Virginia CTCW 4. Citizens Telcom of West Virg. - GTE/West Virginia CTGW 5. Citizens Telcom of Tennessee - Tennessee CTTN 6. Citizens Telcom of Arizona - Arizona CTAZ 7. Citizens Telcom of Arizona - Contel/Arizona CTCZ Commonwealth Telephone Co. - Pennsylvania CWTC GTE Service Operations GTTC 1. GTE California Inc. - California GTCA 2. GTE Florida Inc. - Florida GTFL 3. GTE Northwest Inc. GTNW - Idaho GTID - Montana GTMT - Oregon GTOR - Washington GTWA - West Coast CA GNCA - Contel/Oregon COOR - Contel/Washington COWA 4. GTE South Inc. GTSO - Alabama GTAL - Georgia GTGA - Kentucky GTKY - North Carolina GTNC - South Carolina GTSC - Virginia GTVA - Illinois GLIL 5. GTE Southwest Inc. GTSW - Arkansas GTAR - New Mexico GTNM - Oklahoma GTOK - Texas GTTX Company and Study Area (COSA) List September 1995 Page 4 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code GTE Service Corporation 6. GTE North Inc. GTMW - Illinois GTIL - Indiana GTIN - Michigan GTMI - Ohio GTOH - Pennsylvania GTPA - Wisconsin GTWI - General Offices GTGO - Contel/Illinois COIL - Contel/Indiana COIN - Contel of Pennsylvania COPT - Pennsylvania COPA - Quaker State COQS 7. GTE Midwest Inc. GTMD - Iowa GTIA - Minnesota GTMN - Missouri GTMO - Nebraska GTNE - Contel of Iowa Comp. COIT - Contel/Iowa COIA - Contel/Systems of Iowa COSI - Contel of Missouri Comp. COMT - Contel/Missouri COMO - Contel/Systems of Missouri COCM - Contel/Eastern Missouri COEM 8. GTE Hawaiian Tel. Co. Inc. - Hawaii GTHI 9. GTE Alaska - Alaska GTAK 1. Continental Telephone Company COTC 1. Contel of Texas COTX 2. Contel of Virginia COVA 3. Contel of California COCT - Contel Cal/California COCA - Contel Cal/Nevada CONV 4. Contel of the South COSO - Contel So/Alabama COAL - Indiana GLIN - Michigan GLMI - Contel/Kentucky COKY - Contel/Minnesota COMN - Contel/North Carolina CONC - Contel/South Carolina COSC Company and Study Area (COSA) List September 1995 Page 5 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code - Contel of Arkansas Total COAT - Contel of Arkansas COAR - Systems of Arkansas COSA Lincoln Telephone Company - Nebraska LTNE Puerto Rico Telephone Company - Puerto Rico PRPR Rochester Telephone Operating Companines RTTC 1. Rochester Telephone - New York RTNY 2. Ausable Valley Telephone - New York RTAV 3. Breezewood Telephone - Pennsylvania RTBT 4. CC&S Telco - Michigan RTCM - Ohio RTCO 5. Canton Telephone - Pennsylvania RTCT 6. Enterprise Telephone - Pennsylvania RTET 7. Highland Telephone - New York RTHT 8. Inland Telephone - Illinois RTIT 9. Lakeshore Telephone - Wisconsin RTLW 10. Lakeside Telephone - Illinois RTLI 11. Lakewood Telephone - Pennsylvania RTLP 12. Monroeville Telephone - Alabama RTMA 13. Mt. Pulaski Telephone - Illinois RTMP 14. Midland Telephone - Illinois RTMT 15. Midway Telephone - Michigan RTMM 16. Mondovi Telephone - Wisconsin RTMW 17. Ontonogan Telephone - Michigan RTOT 18. Oswayo River Telephone - Pennsylvania RTOS 19. Prairie Telephone - Illinois RTPT 20. S & A Telephone - Kansas RTKS 21. Senca Gorham Telephone - New York RTSG 22. Sylvan Lake Telephone - New York RTSL 23. Southland Telephone - Alabama RTSA - Florida RTSF 24. Schuyler Telephone - Iowa RTSO - Illinois RTSI 25. Thorntown Telephone - Indiana RTTT 26. Urban Telephone - Wisconsin RTUW Southern New England Telephone - Connecticut SNCT Company and Study Area (COSA) List September 1995 Page 6 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code SPRINT/Centel Telephone Company CETC 1. Central of Florida - Florida CEFL 2. Central of Illinois - Illinois CEIL 3. Central of Virginia - Virginia CEVA 4. Central Telephone Company CETO - North Carolina CENC - Nevada CENV 5. Central of Texas - Texas CETX SPRINT/United Telephone Company UTTC 1. United Tel. Co. of Florida - Florida UTFL 2. United Tel. Co. of Indiana - Indiana UTIN 3. United Tel. Co. of Kansas - Kansas UTKS 4. United Tel. Co. of Minn. - Minnesota UTMN 5. United Tel. Co. of Missouri - Missouri UTMO 6. United Tel. Co. of Neb. - Nebraska UTNE 7. United Tel. Co. of N. Jer. - New Jersey UTNJ 8. Carolina Tel. and Tel. Co. - North Carolina UTNC 9. United Tel. Co. of Ohio - Ohio UTOH 10. United of the Northwest UTNW - Oregon UTOR - Washington UTWA 11. United Tel. Co. of Penn. - Pennsylvania UTPA 12. United Tel. Co. of S. C. - South Carolina UTSC 13. United Tel. Co. of Texas - Texas UTTX 14. United Tel. Co. of Wyoming - Wyoming UTWY 15. United of the Southeast Inc UTIM - Tennessee UTTN - Virginia UTVA Altel Telephone Company Total ALTC 1. Altel of Pennsylvania - Pennsylvania ALPA 2. Georgia Communication Corp - Georgia ALGC AT&T Communications ATTC Vista Telephone Companies VITC Western Reserve Telephone WRTC Total Independent Companies TICO Total Industry TOTL Appendix C Approved by OMB 3060- 0680 Expires 12/31/96 Est. Avg. Burden Hours Per Response: 45-55 Hours FCC Report 43-09B - Instructions September 1995 Page 1 of 1 This document provides the instructions for FCC Report 43-09B, the ARMIS Video Dialtone Fourth Quarter Report, which was adopted by the Common Carrier Bureau to establish reporting requirements on video dialtone costs and jurisdictional separations for local exchange carriers offering video dialtone service. The instructions consist of the following five sections, which are attached: 1.Reporting Procedures - details on the specific procedures to be followed when submitting this report to the Commission. 2.Reporting Definition - an illustration of the rows and columns to be reported and their definitions. 3.Automated Report Specifications - the detailed automated data processing (ADP) specifications for the automated report to be filed. 4.Paper Report Specifications - the page layout and detailed specifications for the paper report to be filed. 5.COSA Code Table - the list of four letter COSA codes (CO = Company, SA = Study Area). A. Introduction This document contains details on the specific procedures to be followed when submitting FCC Report 43- 09B, the ARMIS Video Dialtone Fourth Quarter Report, to the Commission. B. General Information 1. FCC Report 43-09B was adopted by the Common Carrier Bureau to establish the reporting requirements on video dialtone costs and jurisdictional separations for local exchange carriers offering video dialtone service. The report is prescribed for every local exchange carrier that has obtained Section 214 Authorization(s) from the Commission to provide video dialtone trials or commercial services. 2. Affected carriers shall file by March 31 of each year the report for the previous calendar year. 3. The report shall be filed on a study area (jurisdiction) basis. 4. Carriers seeking proprietary treatment for some data must provide two versions of each paper and automated report. The Confidential Version must contain all the required information (Confidential Treatment Tables/Data Records are provided to identify confidential data). The Public Version should not include data for which the carrier is seeking proprietary treatment. The carrier should prominently label the paper report and the diskette containing information subject to a claim of confidentiality to prevent inadvertent disclosure. 5. Carriers not seeking proprietary treatment for any data should provide only one version of each paper report and diskette, and the paper report and the diskette should be labeled the Unrestricted Version. 6. The Confidential Treatment Tables/Data Records are to be included in all reports but are not a substitute for applying for confidential treatment with this Commission following established Commission procedures. 7. Each report and diskette must be clearly labeled to include the report number, company, study area, period, COSA code, version and submission number. The report number is 43-09B, which identifies the filing as the ARMIS Video Dialtone Quarterly Report. The period identifies the year and quarter covered by the data. See the attached COSA Code Table (CO = Company, SA = Study Area) for a list of companies and their respective COSAs. The version refers to whether the filing is the Confidential, Public or Unrestricted Version. The submission number is defined as follows: Submission 0 is for test data purposes only. Submission 1 is the first submission of a quarter's data. Higher numbers (2, 3, etc.) would be used if needed for successive revisions to correct that quarter's submission. 8. All correspondence and pleadings shall identify the proceeding as Reporting Requirements on Video Dialtone Costs and Jurisdictional Separations for Local Exchange Carriers Offering Video Dialtone Services, AAD No. 95-59. C. Data Items That Are "Not Available" or Are "Withheld" 1. The term "Not Available" is used below to refer only to those items which the Commission ruled are not applicable to a particular row/column or are not required for a particular filing entity. The Confidential Version must contain values for all of the data items except those items which are "Not Available." If, in addition to the required study area reports, a carrier submits a report which combines data for more than one study area, and this report includes a field such as a sum, a ratio, or a percentage that cannot be computed completely and accurately because it relies on another item which the Commission has ruled is a "Not Available" item, then that field is also considered to be "Not Available." 2. The term "Withheld" is used below to refer only to those items for which the carrier has applied for confidential treatment with the Commission and is only applicable to the Public Version. If a field such as a sum, a ratio or percentage relies on an item or items which have been withheld and that field is not also withheld, then it must include the withheld amount. For example, a carrier could withhold the individual values for two of three numbers which are totaled. If the carrier does not also apply for confidential treatment for the total, then that total must be the sum of all three numbers, not just the one which was not withheld. The Public Version must contain values for all of the data items except those items which are "Not Available" or those items which have been "Withheld". 3. See paragraph C.11 in the attached Automated Report Specifications and paragraph C.7 in the attached Paper Report Specifications for data entry conventions for these items. D. Where to File 1. Carriers submitting FCC Report 43-09B should consult the schedule below which details the number of copies required and the location to which those copies should be delivered. 2. Carriers are reminded that they must serve a copy of either the Unrestricted Version or the Public Version of both the paper report and the automated report (diskette) on the FCC contractor for public records duplication. NUMBER OF COPIES FOR CARRIERS NOT SEEKING PROPRIETARY TREATMENT Unre- Unre- Trans- stricted stricted mittal Paper Automated Letter Report Report (diskette) FCC Secretary 1919 M Street, N.W. Room 222 Washington, D.C. 20554 1 - - FCC Common Carrier Bureau Accounting & Audits Div. 2000 L Street, N.W. Room 812 Washington, D.C. 20554 2 2 2 FCC Common Carrier Bureau Industry Analysis Div. 1919 M Street, N.W. Room 534 Washington, D.C. 20554 1 1 1 International Transcription Service, Inc. (ITS) 2100 M Street N.W. Suite 140 Washington, D.C. 20037 1 1 1 FOR CARRIERS SEEKING PROPRIETARY TREATMENT Confi- Confi- Trans- dential dential Public Public mittal Paper Automated Paper Automated Letter Report Report Report Report (diskette) (diskette) FCC Secretary 1919 M Street, N.W. Room 222 Washington, D.C. 20554 1 - - - - FCC Common Carrier Bureau Accounting & Audits Div. 2000 L Street, N.W. Room 812 Washington, D.C. 20554 3 1 1 2 2 FCC Common Carrier Bureau Industry Analysis Div. 1919 M Street, N.W. Room 534 Washington, D.C. 20554 1 - - 1 1 International Transcription Service, Inc. (ITS) 2100 M Street N.W. Suite 140 Washington, D.C. 20037 1 - - 1 1 E. Footnotes 1. If any data for the current period differs materially from those for the previous period or the corresponding period of the preceding year and the difference is not self-explanatory but was caused by unusual circumstances, the filing carrier must include footnote text to explain the specific circumstances fully. 2. Footnotes must contain full explanations. EXAMPLE: Do not say, "Data are compiled using a more inclusive process than in previous filing." Do say, "Data are compiled using a process that includes xxx, which was not included in previous filings. The impact of including xxx in this row inflates this number by x% over the previous reporting period." 3. If the reporting carrier does not follow the procedures described in the row and column instructions of the attached Report Definition, it must fully explain any deviations from those procedures. EXAMPLE: Do not say, "This value was not calculated pursuant to the instructions." Do, say "This value was calculated using the xxx method rather than the method described in the instructions because..." 4. Fully explain means the footnote will provide enough information for the data user to understand the circumstances. EXAMPLES: Do not say, "Corrected Data." Do say, "$xxxx is changed to $xxxx because ..." Do not say, "Waiver" or Waiver Granted." Do say, "Waiver of Part xx.xxx was granted in CC Docket No. xx-xxx, x FCC Rcd, xxxx (1992) to allow Any Company to .... because...." 5. Do not include explanatory footnotes in the transmittal letter. The Footnote text must be included in the Footnote Text Records and the Footnote Table as specified in the attached Automated Report Specifications and the attached Paper Report Specifications. F. Errata 1. Carriers are under a legal obligation to correct any erroneous data discovered in FCC Report 43-09B. Submissions containing corrected data must include references to indicate which data items were corrected since previous submission. 2. These references must be included in the Erratum Records and the Erratum Table as specified in the attached Automated Report Specifications and the attached Paper Report Specifications. G. Certification 1. Carriers must certify the accuracy of the data submitted in FCC Report 43-09B by including a signed certification statement as the last page of the paper report. 2. The text of the certification statement is included on page 17 of the attached Report Definition. H. Waivers 1. If a carrier determines that it will be unable to provide data required by FCC Report 43-09B, it must file an application for waiver with the Commission following established Commission procedures. All such requests from a carrier should be included in a single application. The application must demonstrate good cause for reporting a different or lower level of detail and indicate how these deficiencies will be corrected. 2. Carriers are strongly encouraged to comply with the requirements. Omission of individual data items or entries, without request for waiver, is unacceptable. One reason that compliance with the full requirements is so important is that omission of any single data entry by any carrier will jeopardize the accuracy of aggregate industry information. I. Public Information 1. The public or unrestricted versions of the paper reports filed as Report 43-09B may be examined by the public from 9:00 to 12:00 p.m. and from 1:00 to 4:00 p.m., Monday through Friday, in Room 812, 2000 L Street, N.W., Washington, D.C. 2. Copies of the public or unrestricted versions of the paper or automated reports filed as FCC Report 43-09B may be obtained from the FCC's contractor for public records duplication, ITS at 2100 M Street, N.W. Suite 140, Washington, D.C. 20037. Parties should contact Wilbur Thomas or ITS (202) 857-3800. For further information regarding these procedures, contact: Ken Ackerman FCC Common Carrier Bureau Accounting and Audits Division (202) 418-0810 Estimated Average Burden Hours Per Response: 45-55 Approved by OMB OMB NUMBER 3060-0680 Expires 12/31/96 SUMMARY This document provides the Report Definition for FCC Report 43-09B, the ARMIS VDT Fourth Quarter Report, and lists all wholly dedicated and shared investment, expenses, revenue, and jurisdictional separations data related to local exchange carrier provision of video dialtone service. Carriers must provide these data for all four quarters by study area. Pages Table 1 - Video Dialtone Costs and Revenue Data 3 through 8 Row and Column Descriptions 9 through 16 Certification 17 All monetary figures must be rounded to the nearest thousand dollar amount. All percentage amounts must be rounded to two decimal places. Unless otherwise indicated, line items must reflect the results of video dialtone operations as of the end of the reporting period. Items which need not be reported because they do not apply are designated by "N/A". All other fields must be populated. If there are no dollar amounts related to video dialtone operations for a given field, enter zero. Do not include explanatory notes in the transmittal letter; such notes must be included in the footnote section of the filing. NOTICE: FCC Report 43-09B collects highly aggregated financial data reflecting accounting results for the investment, expense, revenue and separations related to the provision of video dialtone service as required by the Video Dialtone Reconsideration Order and in accordance with Parts 32, 36 and Responsible Accounting Officer Letter 25 ("RAO Letter 25"). FCC Report 43-09B specifies information requirements in a consistent format and is essential to the FCC to monitor video dialtone deployment and its effect on subscribers to basic local telephone service. Carriers must file this annual report after receiving Section 214 authorization to provide video dialtone service. Public reporting burden for this collection of information is estimated to average 45-55 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Federal Communications Commission, Records Management Branch, Washington, D.C. 20554. GENERAL INSTRUCTIONS This FCC Report 43-09B requires the annual reporting of data for 14 columns and 57 rows. The rows generally correspond to rows contained in FCC Report 43-01 ARMIS Quarterly Report. Some rows may not apply to video dialtone. These rows are designated "N/A". Carriers should place a zero in any cell that have no dollar amounts related to their video dialtone operations. COLUMN INSTRUCTIONS Column b Total - This column contains the end-of-year balance for each row item included in this report. c Shared - This column reflects the total amount in each row contained in the carriers' subsidiary accounting records established to capture the investment, expenses and revenue shared between video dialtone and the provision of other services. d Shared Allocated to VDT - This column reflects the amount of column (c) that is allocated to video dialtone. e Dedicated VDT - This column reflects the amount in each row contained in the carriers' subsidiary accounting records established to capture the investment, expenses and revenue wholly dedicated to the provision of video dialtone service. f Total VDT - This column reflects the total of column (d) plus column (e). g VDT % Total - This column reflects the result of column (f) divided by column (b) x 100. The result should be rounded to two decimal places. For example 23.70516 should be shown as 23.71. h Nonregulated VDT - This column reflects the amount of each row that relates to the provision of nonregulated video dialtone service. This column equals column (f) minus column (i). i Regulated VDT - This column reflects the amount of each row that is related to the provision of regulated video dialtone service. This column equals column (f) minus column (h). j Adjustments - This column reflects adjustments necessary to arrive at the amount subject to separations. Examples of such adjustments are SNFAs, intra-company adjustments, prior period adjustments and accounting adjustments. k VDT Subject to Separations - This column reflects the portion of each row that must be allocated between state and interstate jurisdictions pursuant to Part 36 of the Commission's Rules. This column equals column (i) minus column (j). This column should also equal column (l) plus column (m). l VDT State Separations - This column reflects the portion of each row allocated to the state jurisdiction pursuant to Part 36 of the Commission's Rules. m VDT Interstate Separations - This column reflects the portion of each row allocated to the interstate jurisdiction pursuant to Part 36 of the Commission's Rules. n State % Separations - This column reflects the result of column (l) divided by column (k) x 100. The result should be rounded to two decimal places. For example 23.70516 should be shown as 23.71. o Interstate % Separations - This column reflects the result of column (m) divided by column (k) x 100. The result should be rounded to two decimal places. For example 23.70516 should be shown as 23.71. ROW INSTRUCTIONS Each row listed below is a summary of accounts described in Part 32 of the Commission's Rules. Because Part 32 does not require the same level of account detail for Class A and Class B carriers, the instructions listed below indicate, where applicable, different reporting for these carriers. Row Revenues 1010 Basic Local Service - Class A: The total of accounts 5001 through 5060. Class B: The total of account 5000. 1020 Network Access Services - Class A and Class B: The total of accounts 5081 through 5084. 1030 Toll Network Services - Class A: The total of accounts 5100, 5110 and 5121 through 5160, exclusive of account 5129. Class B: The total of account 5100. 1040 Miscellaneous - Class A: The total of accounts 5230 through 5250, 5261 through 5264, 5270 and 5280. Class B: The total of accounts 5200 and 5280. 1050 Settlements - The total of accounts 5069, 5129, 5169 and 5269. Carriers which do not retain the Class A accounts throughout separations reporting will include these amounts in the Class B accounts reported on rows 1010, 1030 and 1040. 1060 Uncollectibles - Class A: The total of accounts 5301 and 5302. Class B: The total of account 5300. 1090 Net Revenues - Class A and Class B: The total of rows 1010 through 1050 less row 1060. Expenses 1120 Plant Specific - Class A: The total of accounts 6112 through 6116, 6121 through 6124, 6211 through 6220, 6231, 6232, 6311 through 6362, and 6411 through 6441. Class B: The total of accounts 6110, 6120, 6210, 6220, 6230, 6310, and 6410. 1130 Plant Non-Specific - Class A: The total of accounts 6511, 6512 and 6531 through 6535. Class B: The total of accounts 6510 and 6530. 1140 Customer Operations Marketing - Class A: The total of accounts 6611 through 6613. Class B: The total of account 6610. 1150 Customer Operations Services - Class A: The total of accounts 6621 through 6623. Class B: The total of account 6620. 1160 Corporate Operations - Class A: The total of accounts 6711, 6712, 6721 through 6728 and 6790. Class B: The total of accounts 6710, 6720, and 6790. 1170 Access - Class A and Class B: The balance of account 6540. 1180 Depreciation/Amortization - Class A: The total of accounts 6561 through 6565. Class B: The total of account 6560. 1185 FCC Expense Adjustment - This amount shall contain the net of: (1) expense and other tax items not included above which the Commission has expressly allowed for ratemaking purposes; and (2) expense and other tax items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net allowance and a negative value represents a net disallowance. 1190 Total Operating Expenses - Class A and Class B: The total of rows 1120 through 1185. Other Operating Items 1290 Other Operating Income/Losses - Class A: This amount shall contain the net of accounts 7110 through 7160 and 7990. Class B: This amount shall contain the net of accounts 7100 and 7990. A positive value represents income and a negative value represents loss. Non-operating Items 1320 Income Effects of Jurisdictional Ratemaking Differences (Net) - Class A and Class B: The balance of account 7910. A positive value represents an increase to net income and a negative value represents a decrease to net income. 1330 Extraordinary Items - Class A: The total of accounts 7610 through 7640. Class B: The total of account 7600. Amounts excluded from ratemaking are removed in row 1370. A positive value represents an income credit and a negative value represents an income charge. 1340 Allowance for Funds Used During Construction - Class A: The balance of account 7340. Amounts excluded from ratemaking are removed in row 1370. Class B: Not applicable. 1350 Special Charges - Class A: The balance of account 7370. Amounts excluded from ratemaking are removed in row 1370. Class B: Not applicable. 1360 All Other Non-Operating Items - Class A: The total amount of accounts 7310 through 7330, 7350 and 7360. Class B: Total of account 7300. Amounts excluded from ratemaking are removed in row 1370. A positive value represents income and a negative value represents a loss. 1370 FCC Non-Operating Adjustment - This amount shall contain the net of: (1) non-operating items not included above which the Commission has expressly allowed for ratemaking purposes; and (2) non-operating items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net allowance and a negative value represents a net disallowance. 1390 Total Non-Operating Items - Class A and Class B: The total of rows 1350 and 1370 less rows 1320, 1330, 1340 and 1360. Other Taxes 1410 State and Local Income - Class A: The total of accounts 7230 and the appropriate portion of account 7250 for column(b). For column (h) enter the amount calculated pursuant to the reporting carrier's Cost Allocation Manual. Enter the amount applicable to SNFAs and intra-company transactions in column (j). For column (k) through (m) allocate this amount between the state and intrastate jurisdictions pursuant to Section 36.412. Class B: Follow Class A instructions using relevant portion of account 7200. 1420 Other State and Local - Class A: The total of account 7240 for column (b). For column (h) enter the amount calculated pursuant to the reporting carrier's Cost Allocation Manual. Enter the amount applicable to SNFAs and intracompany transactions in column (j). Calculate this amount for the remaining columns pursuant to Section 36.412. Class B: Follow Class A instructions using relevant portion of account 7200. 1490 Total Other Taxes - The total of rows 1410 and 1420. Federal Income Taxes 1590 Federal Income Taxes - Class A: For column (b), enter the total of account 7220 and the appropriate portion of account 7250 minus the appropriate amount of amortization in account 7210. Class B: Follow Class A instructions using the relevant portion of account 7200. Plant in service All investment data reported in columns (k) through (m) must be calculated by one of two methods: (1) divide the sum of average monthly investments by the number of months in the reporting period; (2) divide the sum of the investment balance for the end of the previous year and the end of the month investment balance for each month in the current reporting period by the number of months in the reporting period plus 1. Investment data reported in columns (b), (h) and (j) are reported as booked. 1620 Support Plant - Class A: The total of accounts 2111 through 2124. Class B: The total amount in account 2110. 1630 Operator Systems Equipment - Class A and Class B: The balance of account 2220. 1640 Central Office Equipment-Switching - Class A: The total of accounts 2211 through 2215. Class B: The total of account 2210. 1650 Central Office Equipment-Transmission - Class A: The total of accounts 2231 and 2232. Class B: The total of account 2230. 1660 Cable and Wire Facilities-Total - Class A: The total of accounts 2411 through 2441. This amount also equals the total of rows 1661, 1662 and 1663. Class B: The total of account 2410. 1661 Cable and Wire Facilities-Metallic Cable - Class A: The total of the metallic subsidiary record categories in accounts 2421, 2422, 2423, 2424, 2425 and 2426. Class B: Not applicable. 1662 Cable and Wire Facilities-Non-Metallic Cable - Class A: The total of the non-metallic subsidiary record categories in accounts 2421, 2422, 2423, 2424, 2425 and 2426. Class B: Not applicable. 1663 Cable and Wire Facilities-Other - Class A: The sum of accounts 2411, 2431, and 2441. Class B: Not applicable. 1670 Information Origination/Termination Equipment - Class A: The total of accounts 2311 through 2362. Class B: The total of account 2310. 1680 Amortizable Assets - Class A: The total of accounts 2681, 2682 and 2690. Class B: The total of accounts 2680 and 2690. 1690 Total Plant - Class A and Class B: The total of rows 1620, 1630, 1640, 1650, 1660, 1670 and 1680. Other Investments 1705 Other Jurisdictional Assets-Net - Class and Class B: The balance of Account 1500. A positive value represents an increase to assets and a negative value represents a decrease to assets. 1710 Property Held for Future Telecommunications Use - Class A and Class B: The total of account 2002. 1720 Telecommunications Plant Under Construction - Class A and Class B: The total of account 2003. Amounts excluded from ratemaking are removed in row 1780. 1730 Plant Acquisition Adjustment - Class A and Class B: The balance of account 2005. Amounts excluded from ratemaking are removed in row 1780. 1740 Investment in Nonaffiliated Companies - Class A and Class B: The balance of account 1402. The amount directly related to Class B Rural Telephone Back Stock shall be included in the rate base. Amounts excluded from ratemaking are removed in row 1780. 1750 Other Deferred Charges - Class A and Class B: The total of accounts 1437, 1438 and 1439. Amounts excluded from ratemaking are removed in row 1780. 1760 Inventories - Class A and Class B: The balance of account 1220. 1770 Cash Working Capital - This amount equals that portion of investment required to meet current expenses. The calculation of this amount shall take into account revenue and expense items which are received or paid for before the service is rendered and expense items received or disbursed after the service is rendered. This amount must be developed pursuant to CC Docket 86-497. 1780 FCC Investment Adjustment - This amount shall contain the net of: (1) investment items not included above which the Commission has expressly allowed for ratemaking purposes; and (2) investment items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net asset allowance and a negative value represents a net disallowance. 1790 Total Other Investment - Class A and Class B: The total of rows 1705 through 1780. Reserves 1820 Accumulated Depreciation - Class A and Class B: The total of accounts 3100 and 3200. 1830 Accumulated Amortization - Class A: The total of accounts 3410, 3420, 3500 and 3600. Class B: The total of accounts 3400, 3500 and 3600. 1840 Deferred Federal Income Taxes - Class A and Class B: The total of accounts 4100 and 4340. 1850 Customer Deposits - Class A and Class B: The balance of account 4040. This amount is separated between state and interstate by application of the interstate plant factor or special study. The interstate plant factor is calculated by dividing interstate plant-in-service by total plant-in- service. 1870 Other Deferred Credits - Class A and Class B: The balance of account 4360. Amounts excluded from ratemaking are removed in row 1885. 1880 Other Jurisdictional Liabilities and Deferred Credits-Net - Class A and Class B: The balance of accounts 4310 and 4370. 1885 FCC Reserve Adjustment - This amount shall contain the net of: (1) reserve items not included above which the Commission has expressly included for ratemaking purposes; and (2) reserve items included above which the Commission has expressly excluded for ratemaking purposes. A positive value represents a net reserve allowance and a negative value represents a net reserve disallowance. 1890 Total Reserves - Class A and Class B: The total of rows 1820 through 1885. CERTIFICATION I certify that I am an officer of _____________________________________________________; that I have examined the foregoing report and that to the best of my knowledge, information, and belief, all statements of fact contained in this report are true and that said report is an accurate statement of the affairs of the above named respondent in respect to the data set forth herein for the period from ___________________________ to ____________________________. PRINTED NAME POSITION SIGNATURE DATE (Persons making willful false statements in this report form can be punished by fine or imprisonment under the Communications Act, 47 U.S.C. 220(e).) CONTACT PERSON TELEPHONE NUMBER FCC Report 43-09B - Automated Report Specifications Sept. 1995 Page 1 of 16 A. Introduction This document contains the detailed automated data processing (ADP) specifications for the automated report to be filed as FCC Report 43-09B, the ARMIS Video Dialtone Fourth Quarter Report. B. General Format and Media 1. All data must be submitted on 3.5 inch double-sided high density IBM- PC compatible diskettes. 2. All files must be coded in ASCII. 3. See sections B and C on pages 1 and 2 of the accompanying Reporting Procedures for a discussion of the Confidential Version, the Public Version, and the Unrestricted Version of this report and for a definition and discussion of data items that are "Not Available" or are "Withheld." 4. The file name for each file has seven components: a. the four letter COSA code (CO = Company, SA = Study Area, see attached COSA Code Table for a list of companies and their respective COSAs). b. the last two digits of the fourth quarter which is covered by the data. c. the letter "V". d. the number 4 to indicate fourth quarter data. e. a decimal point. f. the letter "P", "C", or "U" to indicate whether this is the Public version, the Confidential version, or the only (Unrestricted) version since all data is non-confidential. g. two digits (zero filled) for the submission number. Submission 0 is for test data purposes only. Submission 1 is for the first submission of a quarter's data. Higher numbers (2,3,etc.) would be used if needed for successive revisions to correct that quarter's submission. For example, the file name for the Unrestricted Version of the initial quarterly report data file to be submitted by Illinois Bell to cover the fourth quarter 1995, would be LBIL95V4.U01: LBIL COSA for Illinois Bell 95 Data for calendar year 1995 V Video Dialtone Report Data File 4 Data for the fourth quarter . Decimal point FCC Report 43-09B - Automated Report Specifications Sept. 1995 Page 2 of 16 U Unrestricted version 01 First submission of fourth quarter's data 5. A separate file must be prepared for each report. More than one file can be placed on the same diskette, as long as they cover the same period, version, and submission number. C. Data Entry Conventions 1. If an entry is to be a subtraction, indicate so by placing a minus sign in the column, immediately preceding the numeric data, e.g., use -4, NOT - 4 or (4). 2. Begin each data record in column 1 and make each record the proper length as specified in the accompanying record layouts. Commas are used as delimiters between fields. All numeric fields are right justified and space filled, e.g., use 123, NOT 123 . All non-numeric fields are enclosed in double quotation marks and are left justified and space filled within these quotation marks, e.g., use "John Doe ". 3. Give each record a unique record number, beginning with 1001 and incrementing by one, with no numbers skipped. 4. Do NOT include "$" or "%" or embedded commas, decimal points, spaces, quotes or other formatting characters in any numeric data fields, except for row number and percentage field, which will include a decimal point but not a percent sign. 5. In any numeric data field designated by N/A, enter -99999. If a "Public Version" diskette is filed, enter -88888 in any numeric data field for which data are "Withheld". DO NOT override N/As. If a reporting carrier wishes to apply data to a field containing an N/A, the carrier should enter as a footnote to the field, the amount(s) and an explanation. The amount(s) must not be entered in the N/A's field. All other fields must be populated. If there are no dollar amounts related to video dialtone operations for an open field, enter zero. These entries must be formatted according to the format rules for the particular data field; e.g., in the percentage fields, -99999 would be entered as -99999.00. FCC Report 43-09B - Automated Report Specifications Sept. 1995 Page 3 of 16 D. Rounding Conventions 1. As specified in the accompanying Report Definition, all monetary figures must be rounded to the nearest thousand dollars. 2. All percentage amounts must be entered in percent and must be rounded to 2 decimal places. Example: 23.70561 should be entered as 23.71 E. Footnotes 1. If any data for the current period differs materially from those for the previous period and the difference is not self-explanatory but was caused by unusual circumstances not explained in a previous report, then include footnote text to explain the specific circumstances. 2. If the reporting carrier does not follow the procedures described in the row and column instructions of the attached Report Definition, it must explain any deviations from those procedures in an explanatory footnote. Such footnotes must provide detailed explanations of the procedures actually used by the carrier and its specific reasons for deviating from procedures prescribed by the Commission's Rules. This provision should not be interpreted to mean that deviations from the prescribed rules will automatically be approved by the Commission. 3. Footnotes must be included in the footnote text record(s) of the automated report. F. Errata 1. Carriers are under a legal obligation to correct any erroneous data discovered in FCC Report 43-09B. Submission containing corrected data must include references to indicate which data items were corrected since previous submission. 2. These references must be included in the erratum record(s) of the automated report. FCC Report 43-09B - Automated Report Specifications Sept. 1995 Page 4 of 16 G. Data Record Descriptions The seven data record types are described below. See pages 6 through 16 and for record layouts. The automated file will consist of the following record Types: Record Type H1 Header Record One Type H1 record per file. The first record of each file. Contains identifying data. See page 6 for record layout. Record Type L1 Label Record One Type L1 record per file. The second record of each file. Contains report number, carrier name, study area name, etc. See page 7 for record layout. Record Type S1 Costs, Revenue and 57 Type S1 records per file. Separations Data Record One record for each of the 57 rows shown on Pages 3-8 & 11-16 of the accompanying Report Definition. Each record contains data values reflecting accounting results annualized for the investment, expense, revenue and separations related to the provision of video dialtone service. See pages 8 & 9 for record layout. Record Type C1 Confidential One or more Type C1 records per Treatment Record file. Contains information to identify the data for which the carrier is seeking confidential treatment or to verify that the carrier is not seeking any confidential treatment. See pages 10 & 11 for record layout. Record Type F1 Footnote Record One or more Type F1 records per file. Contains explanatory footnote text. See pages 12 & 13 for record layout. FCC Report 43-09B - Automated Report Specifications Sept. 1995 Page 5 of 16 Record Type E1 Erratum Record Zero Type E1 records for the first submission of the fouth quarter's data. One or more Type E1 records per file in revisions filed to correct this quarter's submission. Contains information to identify the data which was corrected in the submission. See pages 14 & 15 for record layout. Record Type T1 Trailer Record One Type T1 record per file. The last record of each file. Contains contact person, etc. See page 16 for record layout. FCC Report 43-09B - Automated Report Specifications September 1995 Page 6 of 16 RECORD TYPE H1 - HEADER RECORD Field Item Example Position Description 1 Record Number 1001 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. (see attached COSA Code Table) Format: Include quotation marks. 3 Record Type "H1" 13-16 Always contains the letter H capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 File Name "LBIL95V4.U01"18-31 The name of the ASCII file. Format: See page 1, paragraph B.4 above. Include quotation marks. 5 Year 1995 33-36 The year covered by the data. 6 Quarter # 4 38 The quarter number covered by the data. Always contain the number 4 since this data are annualized for the fourth quarter. 4 for January to December 7 Data Entry Date 19950315 40-47 The date on which the data were last entered or revised. Format: YYYYMMDD. 8 Version "U" 49-51 The version letter (P, C or U) capitalized (for Public, Confidential or Unrestricted) Format: Include quotation marks. 9 Submission # 1 53-54 0 for test data purposes only. 1 or first submission of a quarter's data. Higher numbers (2, 3, etc.) would be used if needed for successive revisions to correct that quarter's submission. Format: Right justified and space filled. 10 End of Record Code "XQ" 56-59 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. The ruler lines (123456789 etc.) included below and following with sample records are included only to assist the reader. Do not include ruler lines as records in the electronic filing. ___________________________________________________________ 1 2 3 4 5 . . . . . Ruler Line 12345678901234567890123456789012345678901234567890123456789 . . . . . Ruler line Sample record: 1001,"LBIL","H1","LBIL95V4.U01",1995,1,19950315,"U", 1,"XQ" FCC Report 43-09B - Automated Report Specifications September 1995 Page 7 of 16 RECORD TYPE L1 - LABEL RECORD Field Item Example Position Description 1 Record Number 1002 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "L1" 13-16 Always contains the letter L capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Report Number "FCC REPORT 43-09B" 18-36 Always contains "FCC REPORT 43-09B" capitalized. Format: Include quotation marks. 5 Carrier "Illinois Bell " 38-69 Name of the carrier. (spaces until pos. 69) Format: Left justified and space filled. Include quotation marks. 6 Study Area "Illinois " 71-92 Name of the study area. Format: Left justified and space filled. Include quotation marks. 7 Period Covered "Jan 1995 to Dec 1995" 94-115 Period covered by the data. Format: "mmm yyyy to mmm yyyy" Include quotation marks. 8 End of Record Code "XQ" 117-120 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 9 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567890123 Sample record: 1002,"LBIL","L1","FCC REPORT 43-09B","Illinois Bell ","Illinois ", 1 1 1 9 0 1 2 456789012345678901234567890 Continuation of sample record: "Jan 1995 to Dec 1995","XQ" FCC Report 43-09B - Automated Report Specifications September 1995 Page 8 of 16 RECORD TYPE S1 - COSTS, REVENUE AND SEPARATIONS DATA RECORD Field Item Example Position Description 1 Record Number 1009 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "S1" 13-16 Always contains the letter S capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Row Number 1090.0 18-23 Row number as identified on the accompanying Report Definition. Valid ranges: 1010.0 to 1890.0 Format: Right justified and space filled, with one decimal place. Since all applicable row numbers are integers, append .0 to each row number. 5 Column (b) data 62592 25-33 This field contains the data corresponding to column (b) as shown on Pages 3-8 and 11-16 of the accompanying Report Definition. Do NOT override designated N/As. Format: Right justified and space filled Enter -99999 in integer rows and -99999.00 in percentage rows where a field is designated by N/A. All other fields must be populated. If there are no data applicable to an open field enter zero. Enter -88888 in integer rows and -88888.00 in percentage rows on the "public version" diskette to indicate that confidential treatment has been requested. 6 Column (c) data 15432 35-43 Column (c) data Format: See Field 5 above. 7 Column (d) data 1323 45-53 Column (d) data Format: See Field 5 above. 8 Column (e) data 1252 55-63 Column (e) data Format: See Field 5 above. 9 Column (f) data 18663 65-73 Column (f) data Format: See Field 5 above. 10 Column (g) data 29.80 75-83 Column (g) data Format: See Field 5 above. 11 Column (h) data 2367 85-93 Column (h) data Format: See Field 5 above. 12 Column (i) data 16296 95-103 Column (i) data Format: See Field 5 above. 13 Column (j) data 2345 105-113 Column (j) data Format: See Field 5 above. 14 Column (k) data 13951 115-123 Column (k) data Format: See Field 5 above. 15 Column (l) data 4801 125-133 Column (l) data Format: See Field 5 above. 16 Column (m) data 9150 135-143 Column (m) data Format: See Field 5 above. 17 Column (n) data 34.40 145-153 Column (n) data Format: See Field 5 above. 18 Column (o) data 65.58 155-163 Column (o) data Format: See Field 5 above. FCC Report 43-09B - Automated Report Specifications September 1995 Page 9 of 16 RECORD TYPE S1 - COSTS, REVENUE AND SEPARATIONS DATA RECORD(continued) Field Item Example Position Description 19 End of Record Code "XQ" 165-168 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: Separate all fields with commas. Footnote records are needed if any data for the current period differ materially from those for the previous period or the corresponding period of the preceding year and the difference is not self-explanatory but was caused by unusual circumstances. Footnote records are also needed if the procedures described in the row and column instructions are not followed. The carrier must include footnote text to fully explain the specific circumstances or any deviations from the procedures. See section D of the accompanying Reporting Procedures for a discussion of footnotes. Add one or more Type F1 record(s) after the remaining Type S1 and C1 records. 1 1 2 3 4 5 6 7 8 9 0 12345678901234567890123456789012345678901234567890123456789012345 678901234567890123456789012345678901234 Sample records: 1009,"LBIL","S1",1090.0, 62592, 15432, 13231, 1252, 18663, 29.80, 2367, 16296, 1036,"LBIL","S1",1661.0, 10864, 13021, 5432, 1432, 6864, 27.20, -99999, -99999, 1 1 1 1 1 2 3 4 5 6 5678901234567890123456789012345678901234567890123456789012345678 Continuation of sample records: 13951, 4801, 4801, 9150, 34.40, 65.58,"XQ" -99999, -99999, -99999, -99999,-99999.00,-99999.00,"XQ" FCC Report 43-09B - Automated Report Specifications September 1995 Page 10 of 16 RECORD TYPE C1 - CONFIDENTIAL TREATMENT RECORD Field Item Example Position Description 1 Record Number 1060 1-4 The sequential number of this record (for this record) within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "C1" 13-16 Always contains the letter C capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Record Number 1009 18-21 This field contains the record number (for the confidential of the record which contains the data) data for which the carrier is seeking confidential treatment. If the request is for the entire column(s) or the entire submission, use 9999. If no confidential treatment is being requested, then use 0. Format: Right justified and space filled. 5 Table Number "I " 23-28 This field contains the table number (Roman numerals)of the table in which the the confidential data appear. If the request is for the entire submission, enter "ZZZZ". If no confidential treatment is being requested then enter " ". Format: Include quotation marks. Left justified and space filled. 6 Row Number 1090.0 30-35 This field contains the row number of the row which contains the confidential data as identified in the accompanying Report Definition. If the request is for the entire column(s), an entire table or the entire submission, enter 9999.0. If no confidential treatment is being requested then use 0.0. Format: Right justified and space filled, with one decimal place. 7 Column Label "C " 37-40 This field contains the column letter of the confidential data as identified in the accompanying Report Definition. If the request is for an entire row, an entire table, or the entire submission, enter "ZZ". If the request is for more than one column but less than the entire row, then populate this field and as many as needed of fields 8 thru 26. If no confidential treatment is requested, then enter " " in all of fields 7 thru 26. Format: Include quotation marks. Left justified and space filled. 8 Second Column Label "C " 42-45 ..... 9 Third Column Label "D " 47-50 . Fields 8 thru 26 are similar . . to Field 7 and are used . . when the request is for . . the same row and more than . . one column. 26 Twentieth Col. Label " " 132-135 ..... Otherwise, enter " ". FCC Report 43-09B - Automated Report Specifications September 1995 Page 11 of 16 RECORD TYPE C1 - CONFIDENTIAL TREATMENT RECORD (continued) Field Item Example Position Description 27 End of Record Code "XQ" 137-140 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 9 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567890123456 Sample records: 1060,"LBIL","C1",1009,"I ",1090.0,"B ","C "," "," "," "," "," "," "," "," "," "," ", 1061,"LBIL","C1",9999,"I ",9999.0,"B "," "," "," "," "," "," "," "," "," "," "," ", 1062,"LBIL","C1",1036,"I ",1661.0,"ZZ"," "," "," "," "," "," "," "," "," "," "," ", - OR - 1060,"LBIL","C1", 0," ", 0.0," "," "," "," "," "," "," "," "," "," "," "," ", __ 1 1 1 1 1 9 0 1 2 3 4 78901234567890123456789012345678901234567890 Continuation of sample records: " "," "," "," "," "," "," "," ","XQ" " "," "," "," "," "," "," "," ","XQ" " "," "," "," "," "," "," "," ","XQ" - OR - " "," "," "," "," "," "," "," ","XQ" FCC Report 43-09B - Automated Report Specifications September 1995 Page 12 of 16 RECORD TYPE F1 - FOOTNOTE TEXT RECORD Field Item Example Position Description 1 Record Number 1063 1-4 The sequential number of this record (for this record) within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "F1" 13-16 Always contains the letter F capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Record Number 1003 18-21 This field contains the record number of (for the footnoted the record which contains the footnoted data) data. If the footnote pertains to the entire column(s), an entire table, or the entire submission, use 9999. Format: Right justified and space filled. 5 Table Number "I " 23-28 This field contains the table number (Roman numerals) of the table in which the footnoted data appear. If the footnote pertains to an entire table or the entire submission, use "ZZZZ". Format: Include quotation marks. Left justified and space filled. 6 Row Number 1090.0 30-35 This field contains the row number of the row which contains the footnoted data as identified in the accompanying Report Definition. If the footnote pertains to the entire column(s), an entire table, or the entire submission, enter 9999.0. Format: Right justified and space filled, with one decimal place. 7 Column Label "ZZ" 37-40 This field contains the column letter(s) of the footnoted data as identified in the accompanying Report Definition. If the footnote pertains to an entire row, an entire table, or the entire submission, enter "ZZ". Format: Include quotation marks. Left justified and space filled. 8 Footnote Number 1 42-44 The number of this particular footnote. Valid range: 1 to 999. Format: Right justified and space filled. 9 Sequence Number 1 46-47 The sequence number of the record within the footnote. In other words, the order of the specific record in the sequence of records which, when combined, will provide the entire footnote. Valid range: 1 to 99. Format: Right justified and space filled. 10 Footnote Text "Footnote text " 49-105 The text of the footnote or of the (Spaces until pos. 105) continuation line. Footnote text must be explained fully. Format: Include quotation marks at the beginning and end of this field and left justify within these quotation marks. FCC Report 43-09B - Automated Report Specifications September 1995 Page 13 of 16 RECORD TYPE F1 - FOOTNOTE TEXT RECORD (continued) Field Item Example Position Description 11 End of Record Code "XQ" 107-110 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. Footnote records are needed if any data for the current period differ materially from those for the previous period or the corresponding period of the preceding year and the difference is not self-explanatory but was caused by unusual circumstances. Footnote records are also needed if the procedures described in the row and column instructions are not followed. The carrier must include footnote text to fully explain the specific circumstances or any deviations from the procedures. See section D of the accompanying Reporting Procedures for a discussion of footnotes. 1 1 1 2 3 4 5 6 7 8 9 0 1 12345678901234567890123456789012345678901234567890123456789012345 678901234567890123456789012345678901234567890 Sample records: 1063,"LBIL","F1",1009,"I ",1090.0,"ZZ", 1, 1,"Footnote text for footnote 1 ","XQ" 1064,"LBIL","F1",1009,"I ",1090.0,"ZZ", 1, 2,"continuation text for footnote 1 ","XQ" 1065,"LBIL","F1",1009,"I ",1090.0,"ZZ", 1, 3,"last line of footnote 1 ","XQ" 1066,"LBIL","F1",1036,"I ",1661.0,"B ", 2, 1,"Footnote 2 pertains to column B of Table I row 1661.0 ","XQ" 1067,"LBIL","F1",9999,"I ",9999.0,"C ", 3, 1,"Footnote 3 pertains to all rows of Table I column C ","XQ" FCC Report 43-09B - Automated Report Specifications September 1995 Page 14 of 16 RECORD TYPE E1 - ERRATUM RECORD Field Item Example Position Description 1 Record Number 1068 1-4 The sequential number of this record (for this record) within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "E1" 13-16 Always contains the letter E capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Record Number 1009 18-21 This field contains the record number (for the corrected of the record which contains the data) data which were corrected in this submission. If the entire column(s), an entire table, or the entire submission was corrected, use 9999. Format: Right justified and space filled. 5 Table Number "I " 23-28 This field contains the table number (Roman numerals) of the table in which the corrected data appear. If an entire table or submission was corrected, use "ZZZZ". Format: Include quotation marks. Left justified and space filled. 6 Row Number 1090.0 30-35 This field contains the row number of the of the row which contains the corrected data as identified in the accompanying Report Definition. If the entire column(s), an entire table, or the entire submission was corrected, enter 9999.0. Format: Right justified and space filled, with one decimal place. 7 Column Label "ZZ" 37-40 This field contains the column letter of the corrected data as identified in the accompanying Report Definition. If an entire row, an entire table, or the entire submission was corrected, enter "ZZ". If more than one column but less than the entire row was corrected, then populate this field and as many as needed of fields 8 thru 26. Format: Include quotation marks. Left justified and space filled. 8 Second Column Label "B " 42-45 ..... 9 Third Column Label "C " 47-50 . Fields 8 thru 26 are similar . . to Field 7 and are used . . when the correction is in . . the same row and more than . . one column. 26 Twentieth Col. Label " " 132-135 ..... Otherwise, enter " ". 27 Footnote Number 1 137-139 This field contains the footnote number that explains the correction. If there is no footnote, use a zero. Format: Right justified and space filled. FCC Report 43-09B - Automated Report Specifications September 1995 Page 15 of 16 RECORD TYPE E1 - ERRATUM RECORD (continued) Field Item Example Position Description 28 End of Record Code "XQ" 141-144 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 9 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567890123456 Sample records: 1068,"LBIL","E1",1009,"I ",1090.0,"ZZ"," "," "," "," "," "," "," "," "," "," "," ", 1069,"LBIL","E1",1036,"I ",1661.0,"B ","C "," "," "," "," "," "," "," "," "," "," ", 1070,"LBIL","E1",9999,"I ",9999.0,"C "," "," "," "," "," "," "," "," "," "," "," ", 1 1 1 1 1 90 1 2 3 4 789012345678901234567890123456789012345678901234 Continuation of sample records: " "," "," "," "," "," "," "," ", 1,"XQ" " "," "," "," "," "," "," "," ", 2,"XQ" " "," "," "," "," "," "," "," ", 3,"XQ" FCC Report 43-09B - Automated Report Specifications September 1995 Page 16 of 16 RECORD TYPE T1 - TRAILER RECORD Field Item Example Position Description 1 Record Number 1071 1-4 The sequential number of this record within this data file plus 1000. Format: Right justified and space filled. 2 COSA "LBIL" 6-11 The COSA code for the filing entity. Format: Include quotation marks. 3 Record Type "T1" 13-16 Always contains the letter T capitalized and the number 1 with no space between them. Format: Include quotation marks. 4 Contact Person "John Doe " 18-59 The name of the person to contact (spaces until pos. 59) if there are questions about the report. Format: Include quotation marks. 5 Telephone # "(202) 555-1212 x123 " 61-82 The Contact Person's telephone number. Format: Include quotation marks. 6 End of Record Code "XQ" 84-87 Always contains the letters XQ capitalized with no space between them to indicate the end of the record. Format: Include quotation marks. Note: All fields are separated by commas. 1 2 3 4 5 6 7 8 12345678901234567890123456789012345678901234567890123456789012345 6789012345678901234567 Sample record: 1071,"LBIL","T1","John Doe ","(202) 555-1212 x123 ","XQ" FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 1 of 8 A. Introduction This document contains the page layout and detailed specifications for the paper report to be filed as FCC Report 43-09B, the ARMIS Video Dialtone Fourth Quarter Report. B. General Instructions 1. See sections B and C on pages 1 and 2 of the accompanying Reporting Procedures for a discussion of the Confidential Version, the Public Version, and the Unrestricted Version of this report and for a definition and discussion of data items that are "Not Available" or are "Withheld." 2. The ruler lines included on the page layouts with the column titles are included only to assist the reader. Do not include ruler lines as lines in the report. 3. The paper report must be printed on 8 1/2 inch by 11 inch paper. For ease of preparation, an original may be produced on larger paper and reduced to this size for submission. Copies filed must be legible and permanent, in black ink. The report may be printed in portrait mode (8 1/2 inches across the top of the page) or landscape mode (11 inches across the top of the page). In portrait mode, the printing should not be smaller than 17 characters per inch and 8 lines per inch; in landscape mode, the printing should not be smaller than 15 characters per inch and 10 lines per inch. C. Data Entry Conventions 1. If an entry is to be a subtraction, indicate so by placing a minus sign in the column immediately preceding the numeric data, e.g., use -4 or (4), NOT - 4. 2. Items that need not be reported because they do not apply are designated by N/A. If a "Public Version" report is filed, enter W/H in any numeric data field for which data are "Withheld". DO NOT override N/As. If a reporting carrier wishes to apply data to a field containing an N/A, the carrier must enter, as a footnote to the field, the amount(s) and an explanation. All other fields must be populated. If there are no data applicable to an open field enter zero. 3. Unless otherwise indicated, line items must reflect the results of video dialtone operations as of the end of the reporting period. FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 2 of 8 D. Rounding Conventions 1. As specified in the accompanying Report Definition, all dollar amounts must be rounded to the nearest thousand dollars. 2. All percentage amounts must be entered in percent and must be rounded to two places. Example: 23.70561 should be entered as 23.71 E. Footnotes 1. If any data for the current period differs materially from those for the previous period and the difference is not self-explanatory but was caused by unusual circumstances not explained in a previous report, then include footnote text to explain the specific circumstances. 2. If the reporting carrier does not follow the procedures described in the row and column instructions of the attached Report Definition, it must explain any deviations from those procedures in an explanatoy footnote. Such footnotes must provide detailed explanations of the procedures actually used by the carrier and its specific reasons for deviating from procedures prescribed by the Commission's Rules. This provision should not be interpreted to mean that deviations from the prescribed rules will automatically be approved by the Commission. 3. Footnotes must be included in the footnote table(s) of the paper report, not on individual table pages. F. Errata 1. Carriers are under a legal obligation to correct any erroneous data discovered in FCC Report 43-09B. Submission containing corrected data must include references to indicate which data items were corrected since previous submission. 2. These references must be included in the erratum table(s) of the paper report. E. Page Layouts 1. The page layout for this report is illustrated in the Forms Section of the accompanying Report Definition. FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 3 of 8 2. The following note must appear at the bottom of all pages, where applicable. THE COMPANY HAS REQUESTED CONFIDENTIAL TREATMENT FOR SOME DATA ON THIS PAGE. SEE THE CONFIDENTIAL TREATMENT TABLE FOR SPECIFIC INFORMATION. 4. The Paper Report will consist of the following pages in order: Illustrated in Paper Report Specs. on Page The Cover Page 4 Illustrated in Report Definition Forms on Page Table 1 - Video Dialtone Costs, Revenue 3 through 8 and Separations Data Illustrated in Paper Report Specs. on Page The Confidential Treatment Table (at least one page and as many pages as needed) 5 The Footnote Table (at least one page and as many pages as needed) 6 The Erratum Table (for submission number 2 or higher, as many as needed) 7 The Certification Page 8 FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 4 of 8 FCC Report 43-09B Approved by OMB September 1995 3060-0680 Expires 12/31/96 Estimated Avg. Burden Per Response: 45-55 Hrs. FEDERAL COMMUNICATION COMMISSION WASH INGTON, D.C. 20554 ARMI S VIDEO DIALTONE FOURTH QUAR TER REPORT For the Year Ended December 31, 19 Name of Company: Address of Company: FCC Report 43-09B is prescribed for every local exchanage carrier that has obtained Section 214 Authorization(s) from the Commission to provide video dialtone trials or commercial services. The Video Dialtone Fourth Quarter Report collects highly aggregated financial data reflecting accounting results for the investment, expense, revenue and separations related to the provision of video dialtone service as required by the Video Dialtone Reconsideration Order and in accordance with Parts 32, 36 and Responsible Accounting Officer Letter 25 ("RAO Letter 25"). FCC Report 43-09B specifies information requirements in a consistent format and is essential to the FCC to monitor video dialtone deployment and its effect on subscribers to basic local telephone service. Carriers must file this annual report after receiving Section 214 authorization to provide video dialtone service. Public reporting burden for this collection of information is estimated to average 45-55 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Federal Communications Commission, Records Management Branch, Washington, D.C. 20554. FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 5 of 8 FCC REPORT 43-09B Approved by OMB ARMIS VDT FOURTH QUARTER REPORT 3060-0680 Expires 12/31/95 COMPANY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx VERSION STUDY AREA: xxxxxxxxxxxxxxxxxxxx SUBMISSION x PERIOD: From mmm yyyy to mmm yyyy CONF. TREATMENT TABLE COSA: xxxx PAGE 1 OF x CONFIDENTIAL TREATMENT TABLE Table Row Column(s) ----------- ----------------------------------------------------------- (a) (b) (c) xxxx 1234.1 xx,xx,xx,xx, x, x, x, x, x, x, x, x, x, x, x, x,... Ruler Line sample entries: I 1090.0 B ,C , I ALL B I 1661.0 ALL THE COMPANY HAS REQUESTED CONFIDENTIAL TREATMENT FOR THE ABOVE DATA IN THIS REPORT. -OR- THE COMPANY HAS NOT REQUESTED CONFIDENTIAL TREATMENT FOR ANY DATA IN THIS REPORT. FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 6 of 8 FCC REPORT 43-09B Approved by OMB ARMIS VDT FOURTH QUARTER REPORT 3060-0680 Expires 12/31/96 COMPANY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx VERSION STUDY AREA: xxxxxxxxxxxxxxxxxxxx SUBMISSION x PERIOD: From mmm yyyy to mmm yyyy FOOTNOTE TABLE COSA: xxxx PAGE 1 OF x FOOTNOTE TABLE Table Row Col FN# Footnote ---- ------ --- -- ------------------------------------------------------- (a) (b) (c) (d) (e) xxxx 1234.1 xxx 12 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ... Ruler Line sample entries: I 1090.0 ALL 1 Footnote text for footnote 1 continuation text for footnote 1 last line of footnote 1 I 1661.0 B 2 Footnote 2 pertains to column B of Table I row 1661.0 I ALL C 3 Footnote 3 pertains to all rows of Table I column C -OR- THERE ARE NO FOOTNOTES FOR THIS SUBMISSION. FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 7 of 8 FCC REPORT 43-09B Approved by OMB ARMIS VDT FOURTH QUARTER REPORT 3060-0680 Expires 12/31/96 COMPANY: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx VERSION STUDY AREA: xxxxxxxxxxxxxxxxxxxx SUBMISSION x PERIOD: From mmm yyyy to mmm yyyy ERRATUM TABLE COSA: xxxx PAGE 1 OF x ERRATUM TABLE TableRow Column(s) FN# ---- ------ ----------------------------------------------- --- (a) (b) (c) (d) xxxx 1234.1 xx,xx,xx,xx, x, x, x, x, x, x, x, x, x, x, x, x, 12 ... Ruler Line sample entries: I 1090.0 ALL 1 I 1661.0 B 2 I ALL C 3 THE ABOVE DATA HAVE BEEN CORRECTED IN THIS SUBMISSION. SEE THE FOOTNOTE TABLE FOR FOOTNOTES WHERE APPLICABLE. FCC Report 43-09B - Paper Report Specifications Sept. 1995 Page 8 of 8 CERTIFICATION I certify that I am an officer of ; that I have examined the foregoing report and that to the best of my knowledge, information, and belief, all statements of fact contained in this report are true and that said report is an accurate statement of the affairs of the above named respondent in respect to the data set forth herein for the period from to . PRINTED NAME POSITION SIGNATURE DATE (Persons making willful false statements in this report form can be punished by fine or imprisonment under the Communications Act, 47 U.S.C. 220(e).) CONTACT PERSON TELEPHONE NUMBER Company and Study Area Code (COSA) Table September 1995 Page 1 of 6 DIVESTED BOC INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code Ameritech AMTR 1. Illinois Bell - Illinois LBIL 2. Indiana Bell - Indiana NBIN 3. Michigan Bell - Michigan MBMI 4. Ohio Bell - Ohio OBOH 5. Wisconsin Bell - Wisconsin WTWI Bell Atlantic Network Serv. Corp. BATR 1. the Chesapeake and Potomac Telephone Companies CPTC 1. C&P (D.C.) - Dist. of Columbia CDDC 2. C&P of Maryland - Maryland CMMD 3. C&P of Virginia - Virginia CVVA 4. C&P of West Virginia - West Virginia CWWV 2. Bell of PA and Diamond State PDTC 5. Diamond State Telephone - Delaware DSDE 6. Bell of Pennsylvania - Pennsylvania PAPA 7. New Jersey Bell - New Jersey NJNJ BellSouth Telecommunications, Inc. BSTR - Florida SBFL - Georgia SBGA - North Carolina SBNC - South Carolina SBSC - Alabama SCAL - Kentucky SCKY - Louisiana SCLA - Mississippi SCMS - Tennessee SCTN NYNEX NXTR 1. New England Telephone NETC - Maine NEME - Massachusetts NEMA - New Hampshire NENH - Rhode Island NERI - Vermont NEVT 2. New York Telephone - New York NYNY Pacific Telesis PTTR 1. Pacific Bell - California PTCA 2. Nevada Bell - Nevada PTNV Company and Study Area (COSA) List September 1995 Page 2 of 6 DIVESTED BOC INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code Southwestern Bell Telephone Co. SWTR - Arkansas SWAR - Kansas SWKS - Missouri SWMO - Oklahoma SWOK - Texas SWTX all except Kansas SWAG U.S. West Communications, Inc. USTR - Arizona MSAZ - Colorado MSCO - Idaho MSID - Montana MSMT - New Mexico MSNM - Utah MSUT - Wyoming MSWY - Iowa NWIA - Minnesota NWMN - Nebraska NWNE - North Dakota NWND - South Dakota NWSD - Idaho PNID - Oregon PNOR - Washington PNWA Total Divested Bell Operating Companies TBOC Company and Study Area (COSA) List September 1995 Page 3 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code Alascom, Inc. - Alaska AKAK Cincinnati Bell Telephone - Ohio & Kentucky CBTC Citizens Telecom CTTC 1. Citizens Utilities - California CUCA 2. Citizens Telcom of New York - New York CTNY - Upstate CTUP - Red Hook CTRH - Western Counties CTWC 3. Citizens Telcom of West Virg. - Contel/West Virginia CTCW 4. Citizens Telcom of West Virg. - GTE/West Virginia CTGW 5. Citizens Telcom of Tennessee - Tennessee CTTN 6. Citizens Telcom of Arizona - Arizona CTAZ 7. Citizens Telcom of Arizona - Contel/Arizona CTCZ Commonwealth Telephone Co. - Pennsylvania CWTC GTE Service Operations GTTC 1. GTE California Inc. - California GTCA 2. GTE Florida Inc. - Florida GTFL 3. GTE Northwest Inc. GTNW - Idaho GTID - Montana GTMT - Oregon GTOR - Washington GTWA - West Coast CA GNCA - Contel/Oregon COOR - Contel/Washington COWA 4. GTE South Inc. GTSO - Alabama GTAL - Georgia GTGA - Kentucky GTKY - North Carolina GTNC - South Carolina GTSC - Virginia GTVA - Illinois GLIL 5. GTE Southwest Inc. GTSW - Arkansas GTAR - New Mexico GTNM - Oklahoma GTOK - Texas GTTX Company and Study Area (COSA) List September 1995 Page 4 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code GTE Service Corporation 6. GTE North Inc. GTMW - Illinois GTIL - Indiana GTIN - Michigan GTMI - Ohio GTOH - Pennsylvania GTPA - Wisconsin GTWI - General Offices GTGO - Contel/Illinois COIL - Contel/Indiana COIN - Contel of Pennsylvania COPT - Pennsylvania COPA - Quaker State COQS 7. GTE Midwest Inc. GTMD - Iowa GTIA - Minnesota GTMN - Missouri GTMO - Nebraska GTNE - Contel of Iowa Comp. COIT - Contel/Iowa COIA - Contel/Systems of Iowa COSI - Contel of Missouri Comp. COMT - Contel/Missouri COMO - Contel/Systems of Missouri COCM - Contel/Eastern Missouri COEM 8. GTE Hawaiian Tel. Co. Inc. - Hawaii GTHI 9. GTE Alaska - Alaska GTAK 1. Continental Telephone Company COTC 1. Contel of Texas COTX 2. Contel of Virginia COVA 3. Contel of California COCT - Contel Cal/California COCA - Contel Cal/Nevada CONV 4. Contel of the South COSO - Contel So/Alabama COAL - Indiana GLIN - Michigan GLMI - Contel/Kentucky COKY - Contel/Minnesota COMN - Contel/North Carolina CONC - Contel/South Carolina COSC Company and Study Area (COSA) List September 1995 Page 5 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code - Contel of Arkansas Total COAT - Contel of Arkansas COAR - Systems of Arkansas COSA Lincoln Telephone Company - Nebraska LTNE Puerto Rico Telephone Company - Puerto Rico PRPR Rochester Telephone Operating Companines RTTC 1. Rochester Telephone - New York RTNY 2. Ausable Valley Telephone - New York RTAV 3. Breezewood Telephone - Pennsylvania RTBT 4. CC&S Telco - Michigan RTCM - Ohio RTCO 5. Canton Telephone - Pennsylvania RTCT 6. Enterprise Telephone - Pennsylvania RTET 7. Highland Telephone - New York RTHT 8. Inland Telephone - Illinois RTIT 9. Lakeshore Telephone - Wisconsin RTLW 10. Lakeside Telephone - Illinois RTLI 11. Lakewood Telephone - Pennsylvania RTLP 12. Monroeville Telephone - Alabama RTMA 13. Mt. Pulaski Telephone - Illinois RTMP 14. Midland Telephone - Illinois RTMT 15. Midway Telephone - Michigan RTMM 16. Mondovi Telephone - Wisconsin RTMW 17. Ontonogan Telephone - Michigan RTOT 18. Oswayo River Telephone - Pennsylvania RTOS 19. Prairie Telephone - Illinois RTPT 20. S & A Telephone - Kansas RTKS 21. Senca Gorham Telephone - New York RTSG 22. Sylvan Lake Telephone - New York RTSL 23. Southland Telephone - Alabama RTSA - Florida RTSF 24. Schuyler Telephone - Iowa RTSO - Illinois RTSI 25. Thorntown Telephone - Indiana RTTT 26. Urban Telephone - Wisconsin RTUW Southern New England Telephone - Connecticut SNCT Company and Study Area (COSA) List September 1995 Page 6 of 6 INDEPENDENT COMPANY INDEX Combined Combined Operating Study COSA Holding CompanyCompanies Operating Company Areas Study Area Code SPRINT/Centel Telephone Company CETC 1. Central of Florida - Florida CEFL 2. Central of Illinois - Illinois CEIL 3. Central of Virginia - Virginia CEVA 4. Central Telephone Company CETO - North Carolina CENC - Nevada CENV 5. Central of Texas - Texas CETX SPRINT/United Telephone Company UTTC 1. United Tel. Co. of Florida - Florida UTFL 2. United Tel. Co. of Indiana - Indiana UTIN 3. United Tel. Co. of Kansas - Kansas UTKS 4. United Tel. Co. of Minn. - Minnesota UTMN 5. United Tel. Co. of Missouri - Missouri UTMO 6. United Tel. Co. of Neb. - Nebraska UTNE 7. United Tel. Co. of N. Jer. - New Jersey UTNJ 8. Carolina Tel. and Tel. Co. - North Carolina UTNC 9. United Tel. Co. of Ohio - Ohio UTOH 10. United of the Northwest UTNW - Oregon UTOR - Washington UTWA 11. United Tel. Co. of Penn. - Pennsylvania UTPA 12. United Tel. Co. of S. C. - South Carolina UTSC 13. United Tel. Co. of Texas - Texas UTTX 14. United Tel. Co. of Wyoming - Wyoming UTWY 15. United of the Southeast Inc UTIM - Tennessee UTTN - Virginia UTVA Altel Telephone Company Total ALTC 1. Altel of Pennsylvania - Pennsylvania ALPA 2. Georgia Communication Corp - Georgia ALGC AT&T Communications ATTC Vista Telephone Companies VITC Western Reserve Telephone WRTC Total Independent Companies TICO Total Industry TOTL