FCC Report 495 A Forecast of Investment Usage Report

Forecast of Investment Usage Report and Actual Usage of Investment Report

0410_FCC Report 495a s07_Automated Report Specifications_123107

Forecast of Investment Usage Report and Actual Usage of Investment Report

OMB: 3060-0410

⚠️ Notice: This form may be outdated. More recent filings and information on OMB 3060-0410 can be found here:

2011-07-25 - Extension without change of a currently approved collection

Document [pdf]

Download: pdf | pdf

FCC Report 495A - Automated Report Specifications

December 2007

Page 1 of 24

A. Introduction
This document contains the detailed automated data processing (ADP) specifications for the
automated report to be filed as FCC Report 495A, the Forecast of Investment Usage Report.
B. General Format
1. Electronically-Filed Data
a. For data reporting years 1990 and beyond, carriers must file their ARMIS Reports and
related documents electronically. Electronic submission of both is made through the
Internet by selecting the “Upload ARMIS Data” link on the EAFS Home Page, at
http://www.fcc.gov/wcb/eafs/.
b. All files must be coded in ASCII. Header records in the ARMIS Report data files must
include the report number, company, study area, period, COSA code, version, and
submission number. A higher number (2, 3, etc.) and a new data entry date must be used
each time a change occurs to denote a new submission.
c. A separate ASCII file must be prepared for each report. More than one ASCII file can
be included in the same electronic upload file – which is created by the data validation
program – as long as they are for the same report and cover the same period and version
(different submission numbers and multiple reasons for correcting data are allowed).
d. The electronic submission will serve as the carrier’s official filing.
2. ASCII File Name – each file has six components:
a. the four letter COSA code (CO = Company, SA = Study Area, see the 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 letters “ JF”
d. a decimal point
e. the letter “P”, “C”, or “U” to indicate whether this is the Public version, the Confidential
version, or the Unrestricted version
f. two digits (zero filled) for the submission number: Submission 00 is for test data
purposes only; Submission 01 is for the first submission of a year’s data
For example, the file name for the Unrestricted Version of the initial Forecast of
Investment Usage Report data file to be submitted by Illinois Bell to cover the calendar
year 2008 would be LBIL08JF.U01:

FCC Report 495A - Automated Report Specifications
LBIL
08
JF
.
U
01

December 2007

Page 2 of 24

COSA for Illinois Bell
Data for calendar year 2008
Forecast of Investment Usage Report data file
Decimal point
Unrestricted version
First submission of this year’s data

C. Filing Requirement
1. Proprietary Treatment: Carriers seeking proprietary treatment for some data must provide
two electronic versions of the automated report. The Confidential Version must contain all
the required information. Confidential Treatment Data Records must be provided to identify
confidential data but are not a substitute for applying for confidential treatment with this
Commission following established Commission procedures. The Public Version should
neither include data for which the carrier is seeking proprietary treatment nor Confidential
Treatment Data Records.
Carriers not seeking proprietary treatment for any data should provide only one electronic
version which should be identified as the Unrestricted Version.
2. Data Items That Are "Not Available," "Withheld," or Are “Irretrievable” – See
Sections B and C of the 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,” “Withheld,” or are “Irretrievable.”
3. Related Documents – These documents are required by Commission Order to be filed with
specific ARMIS reports. The electronic submission of these documents must be converted
to Adobe Acrobat’s Portable Document Format (PDF), prior to submitting the documents to
the Commission.
Document Conversion Requirements: Convert directly through a word-processing
application or through the use of a scanning device. Other than a letterhead graphic, the
documents to be converted should consist of text only—no graphics. Conversion of a
document to PDF should result in a black and white document with a resolution no greater
than 300 dpi, and having a file size no more than 40 to 50 Kb per page.
The related documents to be included in the electronic upload file for Report 495A are
described below:
a. Transmittal Letter – Each ARMIS report submission must be accompanied by a letter
of transmittal. When filing confidential data, a separate letter is required. These letters
must be on official company letterhead and be included in each electronic upload file.
The transmittal letter must list only COSAs included in the submission. See Section G.2
of the Reporting Procedures for a description of the information to be provided in the
transmittal letter.

FCC Report 495A - Automated Report Specifications

December 2007

Page 3 of 24

b. Data Certification Statement – Carriers must certify the accuracy of the data submitted
in the ARMIS Reports by including one certification statement, signed by a corporate
officer, in each electronic upload file. The certification statement must list all COSAs
required for a specific ARMIS report. See Section G.3 of the Reporting Procedures for a
description of the information to be included in the statement.
c. 495 “No Data” Letters – Large incumbent local exchange carriers with no data to report
in ARMIS Reports 495A and 495B must file this letter instead of an ASCII file. One
495 “No Data” letter is required for both reports. The letter must be signed by the
company’s responsible officer, certifying that there is no data to report, and must be on
official company letterhead. In addition, the letter must list all operating company and
study area COSAs impacted by the filing. See Section G.3 of the Reporting Procedures
for a description of the information to be provided in the letter. As stated below, the data
validation program will create the electronic upload file for this letter. The electronic
submission of the 495 “No Data” letter will serve as the carrier’s official filing.
4. Data Validation Programs
a. Each reporting carrier must validate its data by using the most recent edit check
program(s), provided by the Commission, for the reporting year. When an error is
detected, the carrier must correct the error prior to submitting the report to the
Commission.
b. The edit check program creates the electronic upload file to be used as the carrier’s
official filing. It will normally contain the following:
1
2.
3.
4.
5.

The ASCII file(s)
Text files that will be stored in the database
The edit check results (“the Discrepancy Report”)
The comparison utility results for roll-up comparisons (“the Detailed Error Report”)
Related documents – one each per upload file, when applicable – in PDF

If a carrier has no data to report, the upload file will contain only one file, a 495 “No
Data” letter in PDF, as described in Section C.3, above.
5. Upload Comment Field: Enter the reason for the filing, which must include a brief
description of ALL data (including footnotes) that have been added, removed, or
modified since the previous submission. This description must agree with what is being
filed. The comments should not contain references to IATD letters. Maximum comment
length is 245 characters (including spaces). If comment length will exceed 245
characters, include in the comments a reference to the associated transmittal letter by its
date, for additional information.

FCC Report 495A - Automated Report Specifications

December 2007

Page 4 of 24

D. Data Entry Conventions
1. Give each record a unique record number, beginning with 1001 and incrementing by one,
with no numbers skipped.
2. Assign a unique row number to each row of the table, beginning with 1 and incrementing by
one, with no numbers skipped.
3. Begin each data record in column 1 and make each record the proper length as specified in
the 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. 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).
4. Do NOT include “$”, “%”, embedded commas, decimal points, quotes or other formatting
characters in any numeric data fields, except for row numbers and percentage fields, which
will include a decimal point but not a percent sign.
5. If a “Public Version” is filed, enter -88888 in any numeric data field and “W/H” in any text
data field for which data are “Withheld” to indicate that confidential treatment has been
requested. These entries must be formatted according to the format rules for the particular
data field; e.g., in the percentage fields, -99999 is entered as -99999.00 and text fields are
enclosed in double quotation marks.
E. Rounding Conventions
1. As specified in the Report Definition, all monetary figures must be rounded to the nearest
thousand dollars.
2. All ratio fields must be entered as in the following example and rounded to 4 decimal places.
Example: 0.12345678 must be entered as 0.1235
F. Footnotes
1. General:
a. For initial (annual) filings, if any data for the current period differ materially from
those for the previous period and the difference is not self-explanatory but was
caused by unusual circumstances, the carrier must include detailed footnote text to
explain the specific circumstances. For resubmission filings, footnotes must be
provided for all changed data, which includes changed footnotes. When a summary

FCC Report 495A - Automated Report Specifications

December 2007

Page 5 of 24

row value changes because of changes to one or more of its detail rows, the summary
row must also be footnoted.
b. Footnotes should be filed for the entities to which they apply: a footnote might apply
to a holding company COSA only, to a study area COSA only, or to both entities.
(However, footnotes should not be submitted at the holding company level if they
apply only to a company’s study areas.)
c. If the reporting carrier does not follow the procedures described in the row and
column instructions of the applicable 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. See Section E of the
Reporting Procedures for examples of valid footnotes.
d. Footnote entries must provide detailed explanations for only those items reported in
the current submission. Footnotes from prior submissions should be included only if
they remain applicable. In other words, when a resubmission nullifies an existing
footnote, remove the footnote.
e. The footnote text must be included in the Footnote Text Records.
2. Mandatory: Certain items require accompanying footnotes and those items are specified
in the appropriate section of the Report Definition for filing the reports. Such footnotes
are mandatory and must be entered in the Footnote Text Records.
3. Footnote Structure:
Observe the footnote specifications to the letter and strive for an efficient footnote structure.
Reduce the size and number of footnotes by using global and referring footnotes.
Global Footnotes
a. If a footnote applies to an entire table, its row number is 9999.0, and its column letter
is ZZ;
b. If a footnote applies to all columns within a single row, its column letter is ZZ;
c. If a footnote applies to a single column within all rows, its row number is 9999.0;
d. If a footnote applies to a majority of (but not all) columns within a single row, its
column letter is ZZ, and its text should include the identity of the columns to which
the footnote applies;

FCC Report 495A - Automated Report Specifications

December 2007

Page 6 of 24

e. If a footnote applies to a single column within a majority of (but not all) rows, its
row number is 9999.0, and its text should include the identity of the rows to which
the footnote applies;
Referring (non-Global) Footnotes
f. If a footnote applies to more than one, but less than a majority of rows or columns,
use individual referring footnotes for the rows or columns to refer to a single
explanatory footnote. The referring footnote must include the explanatory footnote’s
number, row, and column;
g. Referring footnotes and the footnotes to which they refer should be in the same table.
Footnote Removal
h. For resubmissions, remove footnotes if they no longer apply, and renumber the
remaining footnotes.
i. When removing one or more footnotes from a table that were erroneously included in
a previous filing, provide a single explanatory footnote that includes a list of the
affected rows and columns. This footnote’s record number for the footnoted data is
9999 (field 4), its table number is ZZZZ, its row number is 9999.0, and its column
letters are ZZ.
G. Errata
1. Carriers are under a legal obligation to correct any erroneous data, which includes footnotes,
reported in ARMIS Reports. Thus, whenever there are changes in table data, footnotes are
added, footnotes are removed because they were erroneously-filed, or the text of an existing
footnote is changed, an erratum (and resubmission) is required. See Section B of the
Reporting Procedures for the use of submission numbers when an erratum occurs.
2. Submissions containing corrected data must include references to indicate which data items
were corrected since the previous submission. If the data items being corrected impact other
data items in the report, then those items must also be corrected and referenced. Erratum
references should reflect only those items corrected in the new submission. References from
prior submissions must not be included in the new submission.
3. Current errata references must be included in the Erratum Record(s).
4. Errata Structure:
Observe the errata record specifications to the letter, and strive for proper structure.

FCC Report 495A - Automated Report Specifications

December 2007

Page 7 of 24

a. An errata record should reference more than one column, if multiple—but not all—
columns are affected for the same row. (Where all columns are affected use “ZZ” as
the column reference.)
b. When a footnote column field contains “ZZ” to indicate multiple—but not all—
columns, the errata record column field should not use “ZZ.” Instead, list the
columns affected in this field.
c. The errata record should reference the footnote number to which it applies.
d. For Submission Number 3 or higher, be careful to clear the errata table of entries
from previous filings, prior to adding new errata entries for the new submission.
e. When removing one or more footnotes from a table that were erroneously included in
a previous filing, the erratum record should refer to a single footnote explaining the
removed footnote(s). In the erratum record, use 9999 for the record number of the
corrected data (field 4), ZZZZ for the table number, 9999.0 for the row number, and
ZZ for the column letters.
H. Data Record Descriptions
The nine data record types are described below. See pages 9 through 24 for record layouts. The file
will consist of the following record types:
1. Record Type H1 - Header Record
One Type H1 record per file. The first record of each file. Contains identifying data.
See page 9 for record layout.
2. Record Type L2 - Label Record
One Type L2 record per file. The second record of each file. Contains report number,
carrier classification, carrier name, study area name, etc. See page 10 for record layout.
3. Record Type U1 – (Table I) Forecast Usage Data Record
One or more Type U1 records per file. One record for each of the 3 rows for each of the
cost categories designated for Table I, as identified on pages 3, 6, & 7 of the Report
Definition. Each record contains forecast unit of use data values for a particular cost
category and forecast year or one type U1 record to verify that there are no application
cost categories. See pages 11 through 13 for record layout.
4. Record Type I1 - (Table II) Forecasted Investment Allocation Data Record
One or more Type I1 records per file. One record for each row, one row for each cost
category designated for Table II, as identified on pages 4 & 8 of the Report Definition.
Each record contains forecasted investment dollars and their allocation or one type I1
record to verify that there are no applicable cost categories. See pages 14 & 15 for
record layout.

FCC Report 495A - Automated Report Specifications

December 2007

Page 8 of 24

5. Record Type S1 – (Table III) Forecasted Investment Summary Data Record
Twenty or more Type S1 records per file. One record for each row, one row for each
cost category, subtotal, and grand total designated for Table III, as identified on pages 5,
9, & 10 of the Report Definition. Each record contains forecasted investment dollars. See
pages 16 & 17 record layout.
6. Record Type C1 – Confidential Treatment Record (Confidential Version only)
One or more Type C1 records per file. Contains information to identify the data for
which the carrier is seeking confidential treatment. Do not include this record type in
the Public or Unrestricted Versions of a report. See pages 18 & 19 for record layout.
7. Record Type F1 - Footnote Record
Optional. Zero or more Type F1 records per file. Contains explanatory footnote text.
Certain items require accompanying mandatory footnotes and those items are
specified in the appropriate section of the instructions for this report. See pages 20 &
21 for record layout.
8. Record Type E1 - Erratum Record
Zero Type E1 records in the first submission of a year’s data. One or more Type E1
records per file in revisions filed to correct that year’s submission. Contains information
to identify the data which was corrected in the submission. See pages 22 & 23 for record
layout.
9. Record Type T1 - Trailer Record
One Type T1 record per file. The last record of each file. Contains contact person, etc.
See page 24 for record layout.

FCC Report 495A - Automated Report Specifications

December 2007

Page 9 of 24

RECORD TYPE H1 - HEADER RECORD
Field

Item

Example

Position

Record Number

1001

1–4

The sequential number of this record within
this data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"H1"

13 – 16

Always contains the letter H capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

File Name

"LBIL08JF.C01"

18 – 31

The name of the ASCII file.
Format: See page 1, paragraph B.2. Include
quotation marks.

Year

2008

33 – 36

The year covered by the data.

Quarter #

Data Entry Date

20080315

40 – 47

The date on which the data were last entered or
revised.
Format: YYYYMMDD.

Version

"C"

49 – 51

The version letter (P, C or U) capitalized
(Public, Confidential or Unrestricted).
Format: Include quotation marks.

Submission #

53 – 54

00 for test data purposes only; 01 for first
submission of a year’s data. Higher numbers
(02, 03, etc.) are used each time a change
occurs to denote a new submission.
Format: Right justified.

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.

Description

Always contains the number 0 since this is an
annual data file.

Note: All fields are separated by commas.
1

12345678901234567890123456789012345678901234567890123456789
Sample record:
1001,"LBIL","H1","LBIL08JF.C01",2008,0,20080315,"C",01,"XQ"

FCC Report 495A - Automated Report Specifications

December 2007

Page 10 of 24

RECORD TYPE L2 - LABEL RECORD

Field

Item

Example

Position

Record Number

1002

1–4

The sequential number of this record within
this data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"L2"

13 – 16

Always contains the letter L capitalized and the
number 2 with no space between them.
Format: Include quotation marks.

Report Number

"FCC REPORT
495A"

18 – 35

Always contains “FCC REPORT 495A”
capitalized.
Format: Include quotation marks.

Account Filing Level

"A"

37 – 39

Account filing level (Class A or B) capitalized.
Format: Include quotation marks.

Carrier

"Illinois Bell "
(spaces until pos.
70)

41 – 71

Name of the carrier.
Format: Left justified and space filled. Include
quotation marks.

Study Area

"Illinois

73 – 95

Name of the study area.
Format: Left justified and space filled. Include
quotation marks.

Period Covered

"Jan 2008 to Dec
2008"

97 – 118

Period covered by the data.
Format: “mmm yyyy to mmm yyyy” Include
quotation marks.

End of Record Code

"XQ"

120 – 123

Always contains the letters XQ capitalized with
no space between them to indicate the end of
the record.
Format: Include quotation marks.

Description

Note: All fields are separated by commas.
1

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456
Sample record:
1002,"LBIL","L2","FCC REPORT 495A ","A","Illinois Bell
1

789012345678901234567890123
Continuation of sample record:
“Jan 2008 to Dec 2008","XQ"

","Illinois

FCC Report 495A - Automated Report Specifications

December 2007

Page 11 of 24

RECORD TYPE U1 (Table I) - FORECASTED USAGE DATA RECORD
Field

Item

Example

Position

Description

Record Number

1003

1–4

The sequential number of this record within this
data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"U1"

13 – 16

Always contains the letter U capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Row Number

18 – 21

Row numbers as identified on the Report
Definition.
Valid range: 1 to 9999.
Format: Right justified and space filled.

Cost category
account number
Column (a)

2212

23 – 26

This field contains the account number from
column (a) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled.
Note: Repeat this value in all three rows for
each cost category.

Cost category code
Column (b)

"DES-PS"
(spaces until pos.
34)

28 – 35

This field contains the cost category code from
column (b) as shown on the Form Section of
the Report Definition.
Format: Left justified and space filled. Include
quotation marks.
Note: See note at Field 5 above.

Cost category
descriptive name
Column (b)

"Dig Elec Sw
Packet"
(spaces until pos.
57)

37 – 58

This field contains the cost category descriptive
name from column (b) as shown on the Form
Section of the Report Definition.
Format: Left justified and space filled. Include
quotation marks.
Note: See note at Field 5 above.

Allocator unit of use
Column (c)

"Weighted
Terms "
(spaces until pos.
78)

60 – 79

This field contains the allocator unit of use
from column (c) as shown on the Form Section
of the Report Definition.
Format: Left justified and space filled. Include
quotation marks.
Note: See note at field 5 above.

FCC Report 495A - Automated Report Specifications

December 2007

Page 12 of 24

RECORD TYPE U1 (Table I) - FORECASTED USAGE DATA RECORD (continued)
Field

Item

Example

Position

Description

Forecast year
Column (d)

2008

81 – 84

This field contains the forecast year from
column (d) as shown on the Form Section of
the Report Definition.
Format: “yyyy”. Right justified and space
filled.

Column (e) data

100000

86 – 94

This field contains the data corresponding to
column (e) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled. See
Sections D and E for data entry and rounding
conventions.

Column (f) data

80000

96 – 104

Column (f) data
Format: See Field 10 above.

Column (g) data

20000

106 – 114

Column (g) data
Format: See Field 10 above.

Column (h) data

0.2000

116 – 126

This field contains the data corresponding to
column (h) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled. See
Sections D and E for data entry and rounding
conventions.

Column (i) data

-99999.0000

128 – 138

Column (i) data
Format: See Field 13 above.

End of Record Code

"XQ"

140 – 143

Always contains the letters XQ capitalized with
no space between them to indicate the end of
the record.
Format: Include quotation marks.

FCC Report 495A - Automated Report Specifications

December 2007

Page 13 of 24

RECORD TYPE U1 (Table I) - FORECASTED USAGE DATA RECORD (continued)

Notes: All fields are separated by commas.
If there are no cost categories that require allocation on the basis of a forward looking allocator applicable
to Table I, then include only one Type U1 record. Enter the number 0 in fields 5 and 9, “NONE ” in field 6,
and -99999 in fields 10 thru 14.

12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345
Sample records:
1003,"LBIL","U1",

1,2212,"DES-PS","Dig Elec Sw Packet

","Weighted Terms

",2008,

100000,

1004,"LBIL","U1",

2,2212,"DES-PS","Dig Elec Sw Packet

","Weighted Terms

",2009,

200000,

1005,"LBIL","U1",

3,2212,"DES-PS","Dig Elec Sw Packet

","Weighted Terms

",2010,

300000,

","

-99999,

-OR1003,"LBIL","U1",

0,"NONE

","

678901234567890123456789012345678901234567890123
Continuation of sample records:
80000,

20000,

0.2000,-99999.0000,"XQ"

140000,

60000,

0.3000,-99999.0000,"XQ"

180000,

120000,

0.4000,

0.4000,"XQ"

-OR-99999,

-99999,-99999.0000,-99999.0000,"XQ"

FCC Report 495A - Automated Report Specifications

December 2007

Page 14 of 24

RECORD TYPE I1 (Table II) - FORECASTED INVESTMENT ALLOCATION DATA RECORD
Field

Item

Example

Position

Description

Record Number

1093

1–4

The sequential number of this record within this
data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"I1"

13 – 16

Always contains the letter I capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Row Number

18 – 21

Row numbers as identified on the Report
Definition.
Valid range: 1 to 9999.
Format: Right justified and space filled.

Account number
Column (a)

2212

23 – 26

This field contains the account number from
column (a) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled.

Cost category code
Column (b)

"DES-PS"
(spaces until pos.
34)

28 – 35

This field contains the cost category code from
column (b) as shown on the Form Section of
the Report Definition.
Format: Left justified and space filled. Include
quotation marks.

Cost category
descriptive name
Column (b)

"Dig Elec Sw
Packet"
(spaces until pos.
57)

37 – 58

This field contains the cost category descriptive
name from column (b) as shown on the Form
Section of the Report Definition.
Format: Left justified and space filled. Include
quotation marks.

Column (c) data

0.4000

60 – 70

This field contains the data corresponding to
column (c) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled. See
Sections D and E for data entry and rounding
conventions.

FCC Report 495A - Automated Report Specifications

December 2007

Page 15 of 24

RECORD TYPE I1(Table II) - FORECASTED INVESTMENT ALLOCATION DATA RECORD (continued)
Field

Item

Example

Position

Description

Column (d) data

100000

72 – 80

This field contains the data corresponding to
column (d) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled. See
Sections D and E for data entry and rounding
conventions.

Column (e) data

40000

82 – 90

Column (e) data
Format: See Field 9 above.

Column (f) data

92 – 100

Column (f) data
Format: See Field 9 above.

Column (g) data

40000

102 – 110

Column (g) data
Format: See Field 9 above.

End of Record Code

112 – 115

Always contains the letters XQ capitalized with
no space between them to indicate the end of
the record.
Format: Include quotation marks.

"XQ"

Notes: All fields are separated by commas.
If a waiver to transfer nonregulated investment to regulated activities has been granted, a footnote is
required to identify the date and amount of the investment transferred and the date the waiver was granted.
When total demand has begun to decline and is expected to continue to decline until exhausted, the peak
ratio (calculated as column (g) divided by column (d) on Table II) is frozen at its highest previous level. A
footnote is required to identify the year and the Table II filing date from which the peak ratio is derived.
If there are no cost categories that require allocation on the basis of a forward looking allocator applicable
to Table II, then include only one Type I1 record. Enter the number 0 in field 5, “NONE ” in field 6, and 99999 in fields 8 thru 12.
1
1

12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901
Sample record:
1093,"LBIL","I1",

1,2212,"DES-PS","Dig Elec Sw Packet

0.4000,

100000,

40000,

",-99999.0000,

-99999,

-OR1004,"LBIL","I1",
1

0,"NONE

23456789012345
Continuation of sample records:
40000,"XQ"
-OR-99999,"XQ"

","

FCC Report 495A - Automated Report Specifications

December 2007

Page 16 of 24

RECORD TYPE S1 (Table III) - FORECASTED INVESTMENT SUMMARY DATA RECORD
Field

Item

Example

Position

Description

Record Number

1109

1–4

The sequential number of this record within this
data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"S1"

13 – 16

Always contains the letter S capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Row Number

18 – 21

Row numbers as identified on the Report
Definition.
Valid range: 1 to 9999.
Format: Right justified and space filled.

Account number
Column (a)

2212

23 – 26

This field contains the account number from
column (a) as shown on the Form Section of
the Report Definition.
Format: Right justified and space filled.
Note: Enter 0 in rows where the Report
Definition instructs that the column be left
blank.

Cost category code
Column (b)

"DES-PS"
(spaces until pos.
34)

28 – 35

This field contains the cost category code from
column (b) as shown on the Form Section of
the Report Definition.
Format: Left justified and space filled. Include
quotation marks.

Cost category
descriptive name
Column (b)

"Dig Elec Sw
Packet"
(spaces until pos.
57)

37 – 58

This field contains the cost category descriptive
name from column (b) as shown on the Form
Section of the Report Definition.
Format: Left justified and space filled. Include
quotation marks.

Column (c) data

100000

60 – 68

FCC Report 495A - Automated Report Specifications

December 2007

Page 17 of 24

RECORD TYPE S1 (Table III) - FORECASTED INVESTMENT SUMMARY DATA RECORD (continued)
Field

Item

Example

Position

Description

Column (d) data

40000

70 – 78

Column (d) data
Format: See Field 8 above.

Column (e) data

60000

80 – 88

Column (e) data
Format: See Field 8 above.

End of Record Code

"XQ"

90 – 93

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.

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123
Sample record:
1109,"LBIL","S1",

1,2212,"DES-PS","Dig Elec Sw Packet

100000,

40000,

60000,"XQ"

FCC Report 495A - Automated Report Specifications

December 2007

Page 18 of 24

RECORD TYPE C1 - CONFIDENTIAL TREATMENT RECORD
Field

Item

Example

Position

Description

Record Number
(for this record)

1175

1–4

The sequential number of this record within
this data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"C1"

13 – 16

Always contains the letter C capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Record Number
(for the confidential
data)

1003

18 – 21

This field contains the record number of the
record which contains the data for which the
carrier is seeking confidential treatment. If the
request is for the entire column(s) or the entire
submission, use 9999.
Format: Right justified and space filled.

Table Number

"I "

23 – 28

This field contains the table number (Roman
numerals) of the table in which the confidential
data appear. If the request is for the entire table,
use “ZZZZ”.
Format: Include quotation marks. Left justified
and space filled.

Row Number

30 – 33

This field contains the row number of the row
which contains the confidential data as identified
in the Report Definition. If the request is for the
entire column(s), an entire table, or the entire
submission, enter 9999.
Format: Right justified and space filled.

Column Label

"C "

35 – 38

This field contains the column letter(s) of the
confidential data as identified in the 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 need for fields
8 thru 13.
Format: Include quotation marks. Left justified
and space filled.

FCC Report 495A - Automated Report Specifications

December 2007

Page 19 of 24

RECORD TYPE C1 - CONFIDENTIAL TREATMENT RECORD (continued)
Field

Item

Example

Position

Second Column
Label

"F "

40 – 43

9
.
.
.
.
.
18

Third Column Label

"K "

45 – 48

Twelfth Col. Label

" "

90 – 93

End of Record Code

"XQ"

95 – 98

Description

Fields 8 through 18 are similar to field 7 and
are used when the request is for the same row
and more than one column.
Otherwise, enter “ ”.

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

12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678
Sample records:
1175,"LBIL","C1",1003,"I

1,"C ","F "," K","

","

","XQ"

1176,"LBIL","C1",1004,"I

2,"G ","H ","

","

","XQ"

1177,"LBIL","C1",9999,"I

",9999,"I ","

","

","XQ"

1178,"LBIL","C1",1093,"II

","

","XQ"

1,"ZZ","

FCC Report 495A - Automated Report Specifications

December 2007

Page 20 of 24

RECORD TYPE F1 - FOOTNOTE TEXT RECORD
Field

Item

Example

Position

Description

Record Number
(for this record)

1179

1–4

The sequential number of this record within
this data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"F1"

13 – 16

Always contains the letter F capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Record Number
(for the footnoted
data)

1003

18 – 21

This field contains the record number of the
record which contains the footnoted data. See
Section F for Footnote structure guidelines.
Format: Right justified and space filled.

Table Number

"I "

23 – 28

This field contains the table number (Roman
numerals) of the table in which the footnoted
data appear. See Section F for Footnote
structure guidelines.
Format: Include quotation marks. Left justified
and space filled.

Row Number

30 – 33

This field contains the row number of the row
which contains the footnoted data as identified
in the Report Definition. See Section F for
Footnote structure guidelines.
Format: Right justified and space filled.

Column Label

"G "

35 – 38

This field contains the column letter(s) of the
footnoted data as identified in the Report
Definition. See Section F for Footnote structure
guidelines.
Format: Include quotation marks. Left justified
and space filled.

Footnote Number

40 – 42

The number of this particular footnote.
Valid range: 1 to 999.
Format: Right justified and space filled.

FCC Report 495A - Automated Report Specifications

December 2007

Page 21 of 24

RECORD TYPE F1 – FOOTNOTE TEXT RECORD (continued)
Field

Item

Example

Position

Description

Sequence Number

44 – 45

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.

Footnote Text

"Footnote text "
(Spaces until pos.
102)

47 – 103

The text of the footnote or of the continuation
line.
Format: Include quotation marks at the
beginning and end of this field and left justify
within these quotation marks.

End of Record Code

"XQ"

105 – 108

Always contains the letters XQ capitalized with
no space between them to indicate the end of
the record.
Format: Include quotation marks.

Notes: All fields are separated by commas.
If a waiver to transfer nonregulated investment to regulated activities has been granted, a footnote is
required to identify the date and amount of the investment transferred and the date the waiver was granted.
When total demand has begun to decline and is expected to continue to decline until exhausted, the peak
ratio (calculated as column (g) divided by column (d) on Table II) is frozen at its highest previous level. A
footnote is required to identify the year and the Table II filing date from which the peak ratio is derived.
See Section F for detailed footnote content and structure guidelines.

1
1

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678
Sample records:
1179,"LBIL","F1",1003,"I

1,"G ",

1, 1,"Footnote text for footnote 1

","XQ"

1180,"LBIL","F1",1003,"I

1,"G ",

1, 2,"continuation text for footnote 1

","XQ"

1181,"LBIL","F1",1003,"I

1,"G ",

1, 3,"last line of footnote 1.

","XQ"

1182,"LBIL","F1",1004,"I

2,"ZZ",

2, 1,"Footnote 2 pertains to all columns of Table I row 2.

","XQ"

1183,"LBIL","F1",9999,"I

",9999,"H ",

3, 1,"Footnote 3 pertains to all rows of Table I column H.

","XQ"

1184,"LBIL","F1",1094,"II

4, 1,"Footnote 4 pertains to Table II row 2 column C.

","XQ"

2,"C ",

FCC Report 495A - Automated Report Specifications

December 2007

Page 22 of 24

RECORD TYPE E1 - ERRATUM RECORD
Field

Item

Example

Position

Description

Record Number
(for this record)

1185

1–4

The sequential number of this record within
this data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"E1"

13 – 16

Always contains the letter E capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Record Number
(for the corrected
data)

1003

18 – 21

This field contains the record number of the
record which contains the data which were
corrected in this submission. See Section G for
Errata structure guidelines.
Format: Right justified and space filled.

Table Number

"I "

23 – 28

This field contains the table number (Roman
numerals) of the table in which the corrected
data appear. See Section G for Errata structure
guidelines.
Format: Include quotation marks. Left justified
and space filled.

Row Number

30 – 33

This field contains the row number of the row
which contains the corrected data as identified
in the Report Definition. See Section G for
Errata structure guidelines.
Format: Right justified and space filled.

Column Label

"G "

35 – 38

This field contains the column letter of the
corrected data as identified in the Report
Definition. See Section G for Errata structure
guidelines. 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 through
18.
Format: Include quotation marks. Left justified
and space filled.

FCC Report 495A - Automated Report Specifications

December 2007

Page 23 of 24

RECORD TYPE E1 - ERRATUM RECORD (continued)
Field

Item

Example

Position

Second Column
Label

" "

40 – 43

Third Column Label

" "

45 – 48

Description

Fields 8 thru 18 are similar to Field 7
and are used when the correction is in
the same row and more than one column.

.
.
.
18

Twelfth Col. Label

" "

90 – 93

Footnote Number

95 – 97

This field contains the footnote number that
explains the correction
Format: Right justified and space filled.

End of Record Code

"XQ"

99 – 102

Always contains the letters XQ capitalized with
no space between them to indicate the end of
the record.
Format: Include quotation marks.

Otherwise, enter “ ”.

Notes: All fields are separated by commas.
When an erratum occurs, carriers must use higher submission numbers and a new data entry date to denote
a new submission.
See Section G for detailed errata content and structure guidelines.
1
1

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012
Sample records:
1185,"LBIL","E1",1003,"I

1,"G ","

","

1,"XQ"

1186,"LBIL","E1",1004,"I

2,"ZZ","

","

2,"XQ"

1187,"LBIL","E1",9999,"I

",9999,"H ","

","

3,"XQ"

1188,"LBIL","E1",1094,"II

","

4,"XQ"

2,"C ","

FCC Report 495A - Automated Report Specifications

December 2007

Page 24 of 24

RECORD TYPE T1 - TRAILER RECORD
Field

Item

Example

Position

Description

Record Number

1189

1–4

The sequential number of this record within
this data file plus 1000.
Format: Right justified and space filled.

COSA

"LBIL"

6 – 11

The COSA code for the filing entity.
Format: Include quotation marks.

Record Type

"T1"

13 – 16

Always contains the letter T capitalized and the
number 1 with no space between them.
Format: Include quotation marks.

Contact Person

"John Doe
"
(spaces until pos.
58)

18 – 59

The name of the person to contact if there are
questions about the report.
Format: Include quotation marks.

Telephone #

"(202) 555-1212
x123 "

61 – 82

End of Record Code

"XQ"

84 – 87

The Contact Person’s telephone number.
Format: Include quotation marks.
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.

123456789012345678901234567890123456789012345678901234567890123456789012345678901234567
Sample record:
1189,"LBIL","T1","John Doe

","(202) 555-1212 x123 ","XQ"

File Type	application/pdf
File Title	Microsoft Word - specifications495a_final07.doc
File Modified	2008-01-24
File Created	2008-01-24