Information Collection Being Reviewed by the Federal Communications Commission, 45216-45217 [2020-16205]
Download as PDF
jbell on DSKJLSW7X2PROD with NOTICES
45216
Federal Register / Vol. 85, No. 144 / Monday, July 27, 2020 / Notices
Title: Procedures for Formal
Complaints.
Form Number: FCC Form 485.
Type of Review: Extension of a
currently approved collection.
Respondents: Individuals or
households, business or other for-profit
entities, not-for-profit institutions,
federal government, and state, local, or
tribal governments.
Number of Respondents and
Responses: 5 respondents; 13 responses.
Estimated Time per Response: 1—68
hours.
Frequency of Response:
Recordkeeping requirement, onoccasion reporting requirement, and
third party disclosure requirement.
Obligation to Respond: Required to
obtain or retain benefits. Statutory
authority for this information collection
is contained in 47 U.S.C. 151, 154(i),
154(j), 206, 207, 208, 209, 301, 303, 304,
309, 316, 332, and 1302.
Total Annual Burden: 366 hours.
Total Annual Cost: $ 97,175.
Nature and Extent of Confidentiality:
47 CFR 1.731 provides for confidential
treatment of materials disclosed or
exchanged during the course of formal
complaint proceedings when the
disclosing party has identified the
materials as proprietary or confidential.
In the rare case in which a producing
party believes that section 1.731 will not
provide adequate protection for its
assorted confidential material, it may
request either that the opposing party
consent to greater protection, or that the
staff supervising the proceeding order
greater protection.
Privacy Act Impact Assessment: Yes.
The information collection requirements
may affect individuals or households.
As required by the Privacy Act of 1974,
as amended, 5 U.S.C. 552a, and OMB
regulations, M–03–22 (September 22,
2003), the FCC has completed both a
system of records, FCC/EB–5,
‘‘Enforcement Bureau Activity Tracking
System,’’ and a Privacy Impact
Assessment (PIA), to cover the
collection, maintenance, use, and
disposal of all personally identifiable
information (PII) that may be submitted
as part of a formal complaint filed
against a common carrier:
(a) The system of records notice
(SORN), FCC/EB–5, ‘‘Enforcement
Bureau Activity Tracking System
(EBATS),’’ was published in the Federal
Register on December 14, 2010 (75 FR
77872) and became effective on January
24, 2011. It is posted on the FCC’s
Privacy Act web page at: https://
www.fcc.gov/omd/privacyact/recordssystems.html.
(b) The initial Privacy Impact
Assessment (PIA) was completed on
VerDate Sep<11>2014
19:31 Jul 24, 2020
Jkt 250001
May 22, 2009. Subsequent related
approvals include: (1) FCC/EB–5,
‘‘EBATS,’’ on January 24, 2011: and, (2)
September 21, 2017 was updated.
Needs and Uses: Sections 206–209 of
the Communications Act of 1934, as
amended (the ‘‘Act’’), provide the
statutory framework for adjudicating
formal complaints against common
carriers. To resolve complaints between
providers regarding compliance with
data roaming obligations, Commission
Rule 20.12(e) adopts by reference the
procedures already in place for
resolving Section 208 formal complaints
against common carriers, except that the
remedy of damages, is not available for
complaints against commercial mobile
data service providers.
Section 208(a) authorizes complaints
by any person ‘‘complaining of anything
done or omitted to be done by any
common carrier’’ subject to the
provisions of the Act.
Section 208(a) states that if a carrier
does not satisfy a complaint or there
appears to be any reasonable ground for
investigating the complaint, the
Commission shall ‘‘investigate the
matters complained of in such manner
and by such means as it shall deem
proper.’’ Certain categories of
complaints are subject to a statutory
deadline for resolution. See, e.g., 47
U.S.C. 208(b)(1) (imposing a five-month
deadline for complaints challenging the
‘‘lawfulness of a charge, classification,
regulation, or practice’’); 47 U.S.C. 271
(d)(6) (imposing a 90-day deadline for
complaints alleging that a Bell
Operating Company has ceased to meet
conditions imposed in connection with
approval to provide in-region
interLATA services).
Formal complaint proceedings before
the Commission are similar to civil
litigation in federal district court. In
fact, under section 207 of the Act, a
party claiming to be damaged by a
common carrier may file its complaint
with the Commission or in any district
court of the United States, ‘‘but such
person shall not have the right to pursue
both such remedies’’ (47 U.S.C. 207).
The Commission has promulgated rules
(Formal Complaint Rules) to govern its
formal complaint proceedings that are
similar in many respects to the Federal
Rules of Civil Procedure. See 47 CFR
1.720–1.736. These rules require the
submission of information from the
parties necessary to create a record on
which the Commission can decide
complex legal and factual issues. As
described in section 1.720 of the rules,
the Commission resolves formal
complaint proceedings on a written
record consisting of a complaint, answer
or response, and joint statement of
PO 00000
Frm 00058
Fmt 4703
Sfmt 4703
stipulated facts, disputed facts and key
legal issues, along with all associated
affidavits, exhibits and other
attachments.
This collection of information
includes the process for electronically
submitting a formal complaint against a
common carrier. The Commission uses
this information to determine the
sufficiency of complaints and to resolve
the merits of disputes between the
parties. The Commission bases its
orders in formal complaint proceedings
upon evidence and argument produced
by the parties in accordance with the
Formal Complaint Rules. If the
information were not collected, the
Commission would not be able to
resolve common carrier-related
complaint proceedings, as required by
section 208 of the Act.
In addition, the Commission has
adopted most of this formal complaint
process to govern data roaming
complaints. Specifically, the
Commission has extended, as
applicable, the procedural rules in the
Commission’s Part I, Subpart E rules, 47
CFR 1.716–1.718, 1.720, 1.721, and
1.723–1.735, to disputes arising out of
the data roaming rule contained in 47
CFR 20.12(e). Therefore, in addition to
being necessary to resolve common
carrier-related complaint proceedings,
this collection of information is also
necessary to resolve data roamingrelated complaint proceedings.
Federal Communications Commission.
Marlene Dortch,
Secretary, Office of the Secretary.
[FR Doc. 2020–16204 Filed 7–24–20; 8:45 am]
BILLING CODE 6712–01–P
FEDERAL COMMUNICATIONS
COMMISSION
[OMB 3060–XXXX; FRS 16944]
Information Collection Being Reviewed
by the Federal Communications
Commission
Federal Communications
Commission.
ACTION: Notice and request for
comments.
AGENCY:
As part of its continuing effort
to reduce paperwork burdens, and as
required by the Paperwork Reduction
Act of 1995 (PRA), the Federal
Communications Commission (FCC or
Commission) invites the general public
and other Federal agencies to take this
opportunity to comment on the
following information collections.
Comments are requested concerning:
Whether the proposed collection of
SUMMARY:
E:\FR\FM\27JYN1.SGM
27JYN1
jbell on DSKJLSW7X2PROD with NOTICES
Federal Register / Vol. 85, No. 144 / Monday, July 27, 2020 / Notices
information is necessary for the proper
performance of the functions of the
Commission, including whether the
information shall have practical utility;
the accuracy of the Commission’s
burden estimate; ways to enhance the
quality, utility, and clarity of the
information collected; ways to minimize
the burden of the collection of
information on the respondents,
including the use of automated
collection techniques or other forms of
information technology; and ways to
further reduce the information
collection burden on small business
concerns with fewer than 25 employees.
The FCC may not conduct or sponsor a
collection of information unless it
displays a currently valid Office of
Management and Budget (OMB) control
number. No person shall be subject to
any penalty for failing to comply with
a collection of information subject to the
PRA that does not display a valid OMB
control number.
DATES: Written PRA comments should
be submitted on or before September 25,
2020. If you anticipate that you will be
submitting comments, but find it
difficult to do so within the period of
time allowed by this notice, you should
advise the contact listed below as soon
as possible.
ADDRESSES: Direct all PRA comments to
Nicole Ongele, FCC, via email PRA@
fcc.gov and to Nicole.Ongele@fcc.gov.
FOR FURTHER INFORMATION CONTACT: For
additional information about the
information collection, contact Nicole
Ongele, (202) 418–2991.
SUPPLEMENTARY INFORMATION: OMB
Control Number: 3060–XXXX.
Title: E911 Compliance for Fixed
Telephony and Multi-line Telephone
Systems.
Form Number: N/A.
Type of Review: New information
collection.
Respondents: Business or other forprofit entities.
Number of Respondents and
Responses: 1,275,636 respondents;
38,048,948 responses.
Estimated Time per Response: 0.016
hours (one minute).
Frequency of Response: One-time, on
occasion, third party disclosure
requirement, and recordkeeping
requirement.
Obligation to Respond: Mandatory.
Statutory authority for this information
collection is contained in 47 U.S.C.
151–154, 152(a), 155(c), 157, 160, 201,
202, 208, 210, 214, 218, 219, 222, 225,
251(e), 255, 301, 302, 303, 307, 308, 309,
310, 316, 319, 332, 403, 405, 605, 610,
615, 615 note, 615a, 615b, 615c, 615a-
VerDate Sep<11>2014
19:31 Jul 24, 2020
Jkt 250001
1, 616, 620, 621, 623, 623 note, 721, and
1471.
Total Annual Burden: 634,610 hours.
Total Annual Cost: $1,911,540.
Privacy Act Impact Assessment: No
impact(s).
Nature and Extent of Confidentiality:
There is no need for confidentiality with
this collection of information.
Needs and Uses: The Commission is
obligated by statute to promote ‘‘safety
of life and property’’ and to ‘‘encourage
and facilitate the prompt deployment
throughout the United States of a
seamless, ubiquitous, and reliable endto-end infrastructure’’ for public safety.
Congress has established 911 as the
national emergency number to enable
all citizens to reach emergency services
directly and efficiently, irrespective of
whether a citizen uses wireline or
wireless technology when calling for
help by dialing 911. Efforts by federal,
state and local government, along with
the significant efforts of wireline and
wireless service providers, have resulted
in the nearly ubiquitous deployment of
this life-saving service.
Section 506 of RAY BAUM’S Act
requires the Commission to ‘‘consider
adopting rules to ensure that the
dispatchable location is conveyed with
a 9–1–1 call, regardless of the
technological platform used and
including with calls from multi-line
telephone system.’’ RAY BAUM’S Act
also states that, ‘‘[i]n conducting the
proceeding . . . the Commission may
consider information and conclusions
from other Commission proceedings
regarding the accuracy of the
dispatchable location for a 9–1–1 call
. . . .’’ RAY BAUM’S Act defines a ‘‘9–
1–1 call’’ as a voice call that is placed,
or a message that is sent by other means
of communication, to a Public Safety
Answering Point (PSAP) for the purpose
of requesting emergency services.
As part of implementing Section 506
of RAY BAUM’S Act, on August 1,
2019, the Commission adopted a Report
and Order (2019 Order), set forth rules
requiring Fixed Telephony providers
and MLTS providers to ensure that
dispatchable location is conveyed with
911 calls.
The Commission’s 2019 Order
adopted §§ 9.8(a) and 9.16(b)(3)(i), (ii),
and (iii) to facilitate the provision of
automated dispatchable location. For
Fixed Telephony and in fixed Multi-line
Telephone Systems (MLTS)
environments, respective providers
must provide automated dispatchable
location with 911 calls. For onpremises, non-fixed devices associated
with an MLTS, the MLTS operator or
manager must provide automated
dispatchable location to the appropriate
PO 00000
Frm 00059
Fmt 4703
Sfmt 4703
45217
PSAP when technically feasible;
otherwise they must provide either
dispatchable location based on end-user
manual update, or alternative location
information. For off-premises MLTS
calls to 911, the MLTS operator or
manager must provide (1) dispatchable
location, if technically feasible, or,
otherwise, either 2) manually-updated
dispatchable location, or (3) enhanced
location information, which may be
coordinate-based, consisting of the best
available location that can be obtained
from any available technology or
combination of technologies at
reasonable cost. The requirements
adopted in the 2019 Order account for
variance in the feasibility of providing
dispatchable location for non-fixed
MLTS 911 calls, and the means
available to provide it. The information
collection requirements associated with
these rules will ensure that Fixed
Telephony and MLTS providers have
the means to provide 91l callers’
locations to PSAPs, thus reducing
response times for emergency services.
Federal Communications Commission.
Marlene Dortch,
Secretary, Office of the Secretary.
[FR Doc. 2020–16205 Filed 7–24–20; 8:45 am]
BILLING CODE 6712–01–P
FEDERAL COMMUNICATIONS
COMMISSION
[OMB 3060–XXXX; FRS 16939]
Information Collection Being
Submitted for Review and Approval to
Office of Management and Budget
Federal Communications
Commission.
ACTION: Notice and request for
comments.
AGENCY:
As part of its continuing effort
to reduce paperwork burdens, as
required by the Paperwork Reduction
Act (PRA) of 1995, the Federal
Communications Commission (FCC or
the Commission) invites the general
public and other Federal Agencies to
take this opportunity to comment on the
following information collection.
Pursuant to the Small Business
Paperwork Relief Act of 2002, the FCC
seeks specific comment on how it can
further reduce the information
collection burden for small business
concerns with fewer than 25 employees.
DATES: Written comments and
recommendations for the proposed
information collection should be
submitted on or before August 24, 2020.
ADDRESSES: Comments should be sent to
www.reginfo.gov/public/do/PRAMain.
SUMMARY:
E:\FR\FM\27JYN1.SGM
27JYN1
Agencies
[Federal Register Volume 85, Number 144 (Monday, July 27, 2020)]
[Notices]
[Pages 45216-45217]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2020-16205]
-----------------------------------------------------------------------
FEDERAL COMMUNICATIONS COMMISSION
[OMB 3060-XXXX; FRS 16944]
Information Collection Being Reviewed by the Federal
Communications Commission
AGENCY: Federal Communications Commission.
ACTION: Notice and request for comments.
-----------------------------------------------------------------------
SUMMARY: As part of its continuing effort to reduce paperwork burdens,
and as required by the Paperwork Reduction Act of 1995 (PRA), the
Federal Communications Commission (FCC or Commission) invites the
general public and other Federal agencies to take this opportunity to
comment on the following information collections. Comments are
requested concerning: Whether the proposed collection of
[[Page 45217]]
information is necessary for the proper performance of the functions of
the Commission, including whether the information shall have practical
utility; the accuracy of the Commission's burden estimate; ways to
enhance the quality, utility, and clarity of the information collected;
ways to minimize the burden of the collection of information on the
respondents, including the use of automated collection techniques or
other forms of information technology; and ways to further reduce the
information collection burden on small business concerns with fewer
than 25 employees. The FCC may not conduct or sponsor a collection of
information unless it displays a currently valid Office of Management
and Budget (OMB) control number. No person shall be subject to any
penalty for failing to comply with a collection of information subject
to the PRA that does not display a valid OMB control number.
DATES: Written PRA comments should be submitted on or before September
25, 2020. If you anticipate that you will be submitting comments, but
find it difficult to do so within the period of time allowed by this
notice, you should advise the contact listed below as soon as possible.
ADDRESSES: Direct all PRA comments to Nicole Ongele, FCC, via email
[email protected] and to [email protected].
FOR FURTHER INFORMATION CONTACT: For additional information about the
information collection, contact Nicole Ongele, (202) 418-2991.
SUPPLEMENTARY INFORMATION: OMB Control Number: 3060-XXXX.
Title: E911 Compliance for Fixed Telephony and Multi-line Telephone
Systems.
Form Number: N/A.
Type of Review: New information collection.
Respondents: Business or other for-profit entities.
Number of Respondents and Responses: 1,275,636 respondents;
38,048,948 responses.
Estimated Time per Response: 0.016 hours (one minute).
Frequency of Response: One-time, on occasion, third party
disclosure requirement, and recordkeeping requirement.
Obligation to Respond: Mandatory. Statutory authority for this
information collection is contained in 47 U.S.C. 151-154, 152(a),
155(c), 157, 160, 201, 202, 208, 210, 214, 218, 219, 222, 225, 251(e),
255, 301, 302, 303, 307, 308, 309, 310, 316, 319, 332, 403, 405, 605,
610, 615, 615 note, 615a, 615b, 615c, 615a-1, 616, 620, 621, 623, 623
note, 721, and 1471.
Total Annual Burden: 634,610 hours.
Total Annual Cost: $1,911,540.
Privacy Act Impact Assessment: No impact(s).
Nature and Extent of Confidentiality: There is no need for
confidentiality with this collection of information.
Needs and Uses: The Commission is obligated by statute to promote
``safety of life and property'' and to ``encourage and facilitate the
prompt deployment throughout the United States of a seamless,
ubiquitous, and reliable end-to-end infrastructure'' for public safety.
Congress has established 911 as the national emergency number to enable
all citizens to reach emergency services directly and efficiently,
irrespective of whether a citizen uses wireline or wireless technology
when calling for help by dialing 911. Efforts by federal, state and
local government, along with the significant efforts of wireline and
wireless service providers, have resulted in the nearly ubiquitous
deployment of this life-saving service.
Section 506 of RAY BAUM'S Act requires the Commission to ``consider
adopting rules to ensure that the dispatchable location is conveyed
with a 9-1-1 call, regardless of the technological platform used and
including with calls from multi-line telephone system.'' RAY BAUM'S Act
also states that, ``[i]n conducting the proceeding . . . the Commission
may consider information and conclusions from other Commission
proceedings regarding the accuracy of the dispatchable location for a
9-1-1 call . . . .'' RAY BAUM'S Act defines a ``9-1-1 call'' as a voice
call that is placed, or a message that is sent by other means of
communication, to a Public Safety Answering Point (PSAP) for the
purpose of requesting emergency services.
As part of implementing Section 506 of RAY BAUM'S Act, on August 1,
2019, the Commission adopted a Report and Order (2019 Order), set forth
rules requiring Fixed Telephony providers and MLTS providers to ensure
that dispatchable location is conveyed with 911 calls.
The Commission's 2019 Order adopted Sec. Sec. 9.8(a) and
9.16(b)(3)(i), (ii), and (iii) to facilitate the provision of automated
dispatchable location. For Fixed Telephony and in fixed Multi-line
Telephone Systems (MLTS) environments, respective providers must
provide automated dispatchable location with 911 calls. For on-
premises, non-fixed devices associated with an MLTS, the MLTS operator
or manager must provide automated dispatchable location to the
appropriate PSAP when technically feasible; otherwise they must provide
either dispatchable location based on end-user manual update, or
alternative location information. For off-premises MLTS calls to 911,
the MLTS operator or manager must provide (1) dispatchable location, if
technically feasible, or, otherwise, either 2) manually-updated
dispatchable location, or (3) enhanced location information, which may
be coordinate-based, consisting of the best available location that can
be obtained from any available technology or combination of
technologies at reasonable cost. The requirements adopted in the 2019
Order account for variance in the feasibility of providing dispatchable
location for non-fixed MLTS 911 calls, and the means available to
provide it. The information collection requirements associated with
these rules will ensure that Fixed Telephony and MLTS providers have
the means to provide 91l callers' locations to PSAPs, thus reducing
response times for emergency services.
Federal Communications Commission.
Marlene Dortch,
Secretary, Office of the Secretary.
[FR Doc. 2020-16205 Filed 7-24-20; 8:45 am]
BILLING CODE 6712-01-P