Intent To Request Renewal From OMB of One Current Public Collection of Information: Pipeline Operator Security Information, 3448-3449 [2016-01174]

Download as PDF 3448 Federal Register / Vol. 81, No. 13 / Thursday, January 21, 2016 / Notices and Health Disparities, National Institutes of Health, 6707 Democracy Blvd., Suite 800, Bethesda, MD 20892– 5465, or call non-toll free number (301– 594–8704 or email your request including your address to: stinsonn@ mail.nih.gov. Formal requests for additional plans and instruments must be requested in writing. Comment Due Date: Comments regarding this information collection are best assured of having their full effect if received March 21, 2016. Proposed Collection: National Institute on Minority Health and Health Disparities Research Endowments— 0925—NEW—Existing Collection In Use without an OMB Number- National Institute on Minority Health and Health 52i.11(d) contain reporting and information collection requirements that are subject to OMB approval under the Paperwork Reduction Act. Title 45 of the CFR, sections 52i.10, 52i.11(a)(1), 52i.11(a)(2), 52i.11(a)(3), 52i.11(a)(4), and 52i.11(b) contain recordkeeping requirements that are subject to OMB review under the Paperwork Reduction Act. The respondents for this notice consist of institutions currently funded under Section 736 or Section 464z–4 of the PHS Act. OMB approval is requested for 3 years. There are no costs to respondents other than their time. The total estimated annualized burden hours are 548. Disparities (NIMHD), National Institutes of Health (NIH). Need and Use of Information Collection: The NIMHD Research Endowment Program builds research capacity and research infrastructure in order to facilitate minority health research and research regarding other health disparity populations at eligible institutions under sections 736 and 464z–4 of the Public Health Service Act (PHS Act). NIH regulations contains requirements that are subject to OMB approval under the Paperwork Reduction Act of 1995, as amended (44 U.S.C. chapter 35). Title 45 of the CFR, sections 52i.3(b)(2), 52i.4(a), 52i.4(c), 52i.5(a), 52i.9(b), 52i.11(b), and ESTIMATED ANNUALIZED BURDEN HOURS Number of respondents Number of responses per respondent 4 4 4 4 4 12 12 ........................ 1 1 1 1 1 1 1 ........................ 4 1 1 22 4 15 2 49 16 4 4 88 16 180 24 332 12 12 12 12 12 12 1 1 1 1 1 1 2 2 2 2 2 8 24 24 24 24 24 96 Subtotal ............................................................................................. ........................ ........................ 18 216 Total ........................................................................................... ........................ ........................ 67 548 Citations Reporting: 52i.3(b)(2) ................................................................................................. 52i.4(a) ...................................................................................................... 52i.4(c) ...................................................................................................... 52i.5(a) ...................................................................................................... 52i.9(b) ...................................................................................................... 52i.11(b) .................................................................................................... 52i.11(d) .................................................................................................... Subtotal ............................................................................................. Recordkeeping: 52i.10 ........................................................................................................ 52i.11(a)(1) ............................................................................................... 52.i11(a)(2) ............................................................................................... 52i11(a)(3) ................................................................................................ 52i11(a)(4) ................................................................................................ 52.i11(b) .................................................................................................... Dated: January 11, 2016. ´ Eliseo Perez-Stable, Director, NIMHD. [FR Doc. 2016–01080 Filed 1–20–16; 8:45 am] BILLING CODE 4140–01–P DEPARTMENT OF HOMELAND SECURITY asabaliauskas on DSK9F6TC42PROD with NOTICES Transportation Security Administration Intent To Request Renewal From OMB of One Current Public Collection of Information: Pipeline Operator Security Information Transportation Security Administration, DHS. ACTION: 60-day Notice. AGENCY: The Transportation Security Administration (TSA) invites public comment on one currently approved SUMMARY: VerDate Sep<11>2014 18:26 Jan 20, 2016 Jkt 238001 Information Collection Request (ICR), Office of Management and Budget (OMB) control number 1652–0055, abstracted below that we will submit to OMB for a revision in compliance with the Paperwork Reduction Act (PRA). The ICR describes the nature of the information collection and its expected burden. Specifically, the collection involves the submission of data concerning pipeline security incidents. DATES: Send your comments by March 21, 2016. ADDRESSES: Comments may be emailed to TSAPRA@dhs.gov or delivered to the TSA PRA Officer, Office of Information Technology (OIT), TSA–11, Transportation Security Administration, 601 South 12th Street, Arlington, VA 20598–6011. FOR FURTHER INFORMATION CONTACT: Christina A. Walsh at the above address, or by telephone (571) 227–2062. PO 00000 Frm 00072 Fmt 4703 Sfmt 4703 Average time per response ( in hours) Total burden hours SUPPLEMENTARY INFORMATION: Comments Invited In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 et seq.), an agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a valid OMB control number. The ICR documentation is available at http://www.reginfo.gov. Therefore, in preparation for OMB review and approval of the following information collection, TSA is soliciting comments to— (1) Evaluate whether the proposed information requirement is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; (2) Evaluate the accuracy of the agency’s estimate of the burden; E:\FR\FM\21JAN1.SGM 21JAN1 Federal Register / Vol. 81, No. 13 / Thursday, January 21, 2016 / Notices (3) Enhance the quality, utility, and clarity of the information to be collected; and (4) Minimize the burden of the collection of information on those who are to respond, including using appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology. asabaliauskas on DSK9F6TC42PROD with NOTICES Information Collection Requirement OMB Control Number 1652–0055; Pipeline Operator Security Information. Under the Aviation and Transportation Security Act (ATSA) (Pub. L. 107–71, 115 Stat. 597 (November 19, 2001)) and delegated authority from the Secretary of Homeland Security, TSA has broad responsibility and authority for ‘‘security in all modes of transportation . . . including security responsibilities . . . over modes of transportation that are exercised by the Department of Transportation.’’ In executing its responsibility for modal security, TSA produced the Pipeline Security Guidelines in December 2010. As the lead Federal agency for pipeline security, TSA desires to be notified of all incidents which are indicative of a deliberate attempt to disrupt pipeline operations or activities that could be precursors to such an attempt. The Pipeline Security Guidelines encourage pipeline operators to notify the Transportation Security Operations Center (TSOC) via phone at 866–615–5150 or email at TSOC.ST@ dhs.gov as soon as possible if any of the following incidents occurs or if there is other reason to believe that a terrorist incident may be planned or may have occurred: • Explosions or fires of a suspicious nature affecting pipeline systems, facilities, or assets. • Actual or suspected attacks on pipeline systems, facilities, or assets. • Bomb threats or weapons of mass destruction (WMD) threats to pipeline systems, facilities, or assets. • Theft of pipeline company vehicles, uniforms, or employee credentials. • Suspicious persons or vehicles around pipeline systems, facilities, assets, or right-of-way. • Suspicious photography or possible surveillance of pipeline systems, facilities, or assets. • Suspicious phone calls from people asking about the vulnerabilities or security practices of a pipeline system, facility, or asset operation. • Suspicious individuals applying for security-sensitive positions in the pipeline company. VerDate Sep<11>2014 18:26 Jan 20, 2016 Jkt 238001 3449 • Theft or loss of Sensitive Security Information (SSI) (detailed pipeline maps, security plans, etc.). • Actual or suspected cyber-attacks that could impact pipeline Supervisory Control and Data Acquisition (SCADA) or enterprise associated IT systems. When contacting the TSOC, the Guidelines request pipeline operators to provide as much of the following information as possible: • Name and contact information (email address, telephone number). • The time and location of the incident, as specifically as possible. • A description of the incident or activity involved. • Who has been notified and what actions have been taken. • The names and/or descriptions of persons involved or suspicious parties and license plates as appropriate. In addition to the reporting of security incident data to the TSOC, the Pipeline Security Guidelines previously included collecting information on recommendations for the voluntary submission of pipeline operator security manager contact information to TSA. TSA is revising the collection of information and will no longer collect the security manager contact information as that information is now available through data maintained by TSA; however, the agency will continue to collect information on the reporting of security incident data to TSOC. TSA expects reporting of pipeline security incidents will occur on an irregular basis. TSA estimates that approximately 40 incidents will be reported annually, requiring a maximum of 30 minutes to collect, review, and submit event information. The potential burden to the public is estimated to be 20 hours. (40 incidents × 30 minutes = 20 hours) SUMMARY: Dated: January 14, 2016. Christina A. Walsh TSA Paperwork Reduction Act Officer, Office of Information Technology. Title of Information Collection: Form HUD–92266 Application for Transfer of Physical Assets (TPA). OMB Approval Number: 2502–0275. Type of Request: Extension of currently approved collection. Form Number: : HUD–92266. Description of the need for the information and proposed use: When the sale andconveyance by deed to an insured mortgage necessitates a substitution of mortgagors, HUD approval of the substitution is required. Respondents (i.e. affected public): Multifamily property owners with loans insured or held by HUD. Estimated Number of Respondents: 14,734. Estimated Number of Responses: 295. Frequency of Response: Once per transfer of physical assets. [FR Doc. 2016–01174 Filed 1–20–16; 8:45 am] BILLING CODE 9110–05–P DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT [Docket No. FR–5909–N–04] 30-Day Notice of Proposed Information Collection:Form HUD–92266 Application for Transfer of Physical Assets (TPA) Office of the Chief Information Officer, HUD. ACTION: Notice. AGENCY: PO 00000 Frm 00073 Fmt 4703 Sfmt 4703 HUD has submitted the proposed information collection requirement described below to the Office of Management and Budget (OMB) for review, in accordance with the Paperwork Reduction Act. The purpose of this notice is to allow for an additional 30 days of public comment. DATES: Comments Due Date: February 22, 2016. ADDRESSES: Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB Control Number and should be sent to: HUD Desk Officer, Office of Management and Budget, New Executive Office Building, Washington, DC 20503; fax: 202–395–5806. Email: OIRA_Submission@omb.eop.gov. FOR FURTHER INFORMATION CONTACT: Colette Pollard, Reports Management Officer, QMAC, Department of Housing and Urban Development, 451 7th Street, SW., Washington, DC 20410; email Colette Pollard at Colette.Pollard@ hud.gov or telephone202–402–3400. This is not a toll-free number. Persons with hearing or speech impairments may access this number through TTY by calling the toll-free Federal Relay Service at(800) 877–8339. Copies of available documents submitted to OMB may be obtained from Ms. Pollard. SUPPLEMENTARY INFORMATION: This notice informs the public that HUD is seeking approval from OMB for the information collection described in Section A. The Federal Register notice that solicited public comment on the information collection for a period of 60 days was published on November 4, 2015 at 80 FR 68331. A. Overview of Information Collection E:\FR\FM\21JAN1.SGM 21JAN1

Agencies

[Federal Register Volume 81, Number 13 (Thursday, January 21, 2016)]
[Notices]
[Pages 3448-3449]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2016-01174]


=======================================================================
-----------------------------------------------------------------------

DEPARTMENT OF HOMELAND SECURITY

Transportation Security Administration


Intent To Request Renewal From OMB of One Current Public 
Collection of Information: Pipeline Operator Security Information

AGENCY: Transportation Security Administration, DHS.

ACTION: 60-day Notice.

-----------------------------------------------------------------------

SUMMARY: The Transportation Security Administration (TSA) invites 
public comment on one currently approved Information Collection Request 
(ICR), Office of Management and Budget (OMB) control number 1652-0055, 
abstracted below that we will submit to OMB for a revision in 
compliance with the Paperwork Reduction Act (PRA). The ICR describes 
the nature of the information collection and its expected burden. 
Specifically, the collection involves the submission of data concerning 
pipeline security incidents.

DATES: Send your comments by March 21, 2016.

ADDRESSES: Comments may be emailed to TSAPRA@dhs.gov or delivered to 
the TSA PRA Officer, Office of Information Technology (OIT), TSA-11, 
Transportation Security Administration, 601 South 12th Street, 
Arlington, VA 20598-6011.

FOR FURTHER INFORMATION CONTACT: Christina A. Walsh at the above 
address, or by telephone (571) 227-2062.

SUPPLEMENTARY INFORMATION: 

Comments Invited

    In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 
3501 et seq.), an agency may not conduct or sponsor, and a person is 
not required to respond to, a collection of information unless it 
displays a valid OMB control number. The ICR documentation is available 
at http://www.reginfo.gov. Therefore, in preparation for OMB review and 
approval of the following information collection, TSA is soliciting 
comments to--
    (1) Evaluate whether the proposed information requirement is 
necessary for the proper performance of the functions of the agency, 
including whether the information will have practical utility;
    (2) Evaluate the accuracy of the agency's estimate of the burden;

[[Page 3449]]

    (3) Enhance the quality, utility, and clarity of the information to 
be collected; and
    (4) Minimize the burden of the collection of information on those 
who are to respond, including using appropriate automated, electronic, 
mechanical, or other technological collection techniques or other forms 
of information technology.

Information Collection Requirement

    OMB Control Number 1652-0055; Pipeline Operator Security 
Information. Under the Aviation and Transportation Security Act (ATSA) 
(Pub. L. 107-71, 115 Stat. 597 (November 19, 2001)) and delegated 
authority from the Secretary of Homeland Security, TSA has broad 
responsibility and authority for ``security in all modes of 
transportation . . . including security responsibilities . . . over 
modes of transportation that are exercised by the Department of 
Transportation.'' In executing its responsibility for modal security, 
TSA produced the Pipeline Security Guidelines in December 2010.
    As the lead Federal agency for pipeline security, TSA desires to be 
notified of all incidents which are indicative of a deliberate attempt 
to disrupt pipeline operations or activities that could be precursors 
to such an attempt. The Pipeline Security Guidelines encourage pipeline 
operators to notify the Transportation Security Operations Center 
(TSOC) via phone at 866-615-5150 or email at TSOC.ST@dhs.gov as soon as 
possible if any of the following incidents occurs or if there is other 
reason to believe that a terrorist incident may be planned or may have 
occurred:
     Explosions or fires of a suspicious nature affecting 
pipeline systems, facilities, or assets.
     Actual or suspected attacks on pipeline systems, 
facilities, or assets.
     Bomb threats or weapons of mass destruction (WMD) threats 
to pipeline systems, facilities, or assets.
     Theft of pipeline company vehicles, uniforms, or employee 
credentials.
     Suspicious persons or vehicles around pipeline systems, 
facilities, assets, or right-of-way.
     Suspicious photography or possible surveillance of 
pipeline systems, facilities, or assets.
     Suspicious phone calls from people asking about the 
vulnerabilities or security practices of a pipeline system, facility, 
or asset operation.
     Suspicious individuals applying for security-sensitive 
positions in the pipeline company.
     Theft or loss of Sensitive Security Information (SSI) 
(detailed pipeline maps, security plans, etc.).
     Actual or suspected cyber-attacks that could impact 
pipeline Supervisory Control and Data Acquisition (SCADA) or enterprise 
associated IT systems.
    When contacting the TSOC, the Guidelines request pipeline operators 
to provide as much of the following information as possible:
     Name and contact information (email address, telephone 
number).
     The time and location of the incident, as specifically as 
possible.
     A description of the incident or activity involved.
     Who has been notified and what actions have been taken.
     The names and/or descriptions of persons involved or 
suspicious parties and license plates as appropriate.
    In addition to the reporting of security incident data to the TSOC, 
the Pipeline Security Guidelines previously included collecting 
information on recommendations for the voluntary submission of pipeline 
operator security manager contact information to TSA. TSA is revising 
the collection of information and will no longer collect the security 
manager contact information as that information is now available 
through data maintained by TSA; however, the agency will continue to 
collect information on the reporting of security incident data to TSOC.
    TSA expects reporting of pipeline security incidents will occur on 
an irregular basis. TSA estimates that approximately 40 incidents will 
be reported annually, requiring a maximum of 30 minutes to collect, 
review, and submit event information. The potential burden to the 
public is estimated to be 20 hours. (40 incidents x 30 minutes = 20 
hours)

    Dated: January 14, 2016.
Christina A. Walsh
TSA Paperwork Reduction Act Officer, Office of Information Technology.
[FR Doc. 2016-01174 Filed 1-20-16; 8:45 am]
 BILLING CODE 9110-05-P