A75-HUD Central Accounting and Program System (HUDCAPS) Privacy Act of 1974; System of Records, 11240-11242 [2018-05070]
Download as PDF
<![CDATA[
11240
Federal Register / Vol. 83, No. 50 / Wednesday, March 14, 2018 / Notices
[FR Doc. 2018–05089 Filed 3–13–18; 8:45 am]
BILLING CODE 9110–05–P
DEPARTMENT OF HOMELAND
SECURITY
Transportation Security Administration
Intent To Request Renewal From OMB
of One Current Public Collection of
Information: Law Enforcement Officer
(LEO) Reimbursement Request
Transportation Security
Administration, DHS.
ACTION: 60-Day notice.
AGENCY:
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–0063,
abstracted below that we will submit to
OMB for an extension in compliance
with the Paperwork Reduction Act
(PRA). The ICR describes the nature of
the information collection and its
expected burden. The collection
involves the reimbursement of expenses
incurred by airport operators for the
provision of law enforcement officers to
support airport checkpoint screening.
DATES: Send your comments by May 14,
2018.
ADDRESSES: Comments may be emailed
to TSAPRA@tsa.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:
daltland on DSKBBV9HB2PROD with NOTICES
SUMMARY:
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 will be
available at https://www.reginfo.gov
upon its submission to OMB. 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;
VerDate Sep<11>2014
18:17 Mar 13, 2018
Jkt 244001
(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.
Consistent with the requirements of
Executive Order (E.O.) 13771, Reducing
Regulation and Controlling Regulatory
Costs, and E.O. 13777, Enforcing the
Regulatory Reform Agenda, TSA is also
requesting comments on the extent to
which this request for information could
be modified to reduce the burden on
respondents.
Information Collection Requirement
OMB Control Number 1652–0063; Law
Enforcement Officer (LEO)
Reimbursement Request. Pursuant to 49
U.S.C. 114(m), and secs. 106(l) and (m),
TSA has authority to enter into
agreements with participants to
reimburse expenses incurred by airport
operators for the provision of LEOs in
support of screening at airport
checkpoints. Consistent with this
authority, TSA created the LEO
Reimbursement Program, which is run
by the Office of Law Enforcement/
Federal Air Marshal Service (OLE/
FAMS).
TSA OLE/FAMS requires that
participants in the LEO Reimbursement
Program record the details of all
reimbursements sought. In order to
provide for the orderly tracking of
reimbursements, the LEO
Reimbursement Program uses TSA Form
3503, LEO Reimbursement Request,
which captures and tracks
reimbursement information.
The LEO Reimbursement Request
form is available at www.tsa.gov. Upon
completion, participants submit the
LEO Reimbursement Request form
directly to the OLE/FAMS LEO
Reimbursement Program via fax,
electronic upload (via scanning the
document), mail, or in person. The OLE/
FAMS LEO Reimbursement Program
reviews all request for reimbursement
forms received. Based on the prior year
participation, TSA estimates that there
will be 294 participant responses
monthly or 3,528 yearly, which is a
decrease from the 2015 submission of
326 monthly participants.
TSA estimates each respondent will
spend approximately one hour to
complete the request for reimbursement
form, for a total annual hour burden of
3,528 hours.
PO 00000
Frm 00073
Fmt 4703
Sfmt 4703
Dated: March 7, 2018.
Christina A. Walsh,
TSA Paperwork Reduction Act Officer, Office
of Information Technology.
[FR Doc. 2018–05091 Filed 3–13–18; 8:45 am]
BILLING CODE 9110–05–P
DEPARTMENT OF HOUSING AND
URBAN DEVELOPMENT
[Docket No. FR–7009–N–04]
A75–HUD Central Accounting and
Program System (HUDCAPS) Privacy
Act of 1974; System of Records
Department of Housing and
Urban Development.
ACTION: Notice of a modified system of
records.
AGENCY:
A75 HUDCAPS is an Office of
the Chief Financial Officer (OCFO)
system that serves as a sub-ledger
financial system for HUD. As of October
1, 2015, HUDCAPS is no longer HUD’s
core financial system/system of record
due to the implementation of New Core
Project Phase 1 Release 3. HUDCAPS is
now a sub-ledger financial system for
HUD and the Department of Treasury,
Administrative Resource Center (ARC)
Oracle Federal Financials serves as
HUD’s system of record and core
financial system.
DATES: April 13, 2018.
ADDRESSES: You may submit comments,
identified by docket number and title,
by one of the following methods:
Email: privacy@hud.gov.
Mail: John Bravacos, Senior Agency
Official for Privacy, Privacy Office,
Department of Housing and Urban
Development, Washington, DC 20410.
FOR FURTHER INFORMATION CONTACT: For
general questions please contact: The
Privacy Office, 451 Seventh Street SW,
Room 10139, Washington, DC 20410,
telephone number 202–708–3054.
Individuals who are hearing- or speechimpaired may access this number via
TTY by calling the Federal Relay
Service at 800–877–8339 (this is a tollfree number).
SUPPLEMENTARY INFORMATION: This
notice of revision of the System of
Records Notice for A75 HUDCAPS
reflects the change of HUDCAPS from a
core financial system to a sub-ledger
financial system for HUD. The
Department of Treasury, Administrative
Resource Center (ARC) Oracle Federal
Financials now serves as HUD’s system
of record and core financial system.
The following transactions remain in
HUDCAPS:
• Public and Indian Housing (PIH)
Section 8 programmatic transaction,
SUMMARY:
E:\FR\FM\14MRN1.SGM
14MRN1
Federal Register / Vol. 83, No. 50 / Wednesday, March 14, 2018 / Notices
including payments of PIH Section 8
programmatic invoices.
• Program Accounting System (PAS)
will continue to transmit current
transactional activity to HUDCAPS for
posting to the HUDCAPS sub ledger,
which is transmitted through NCIS to
the Oracle Federal Financials G/L.
• HUD legacy subsidiary systems
such as Line of Credit Control System
(LOCCS), Northridge Loan System
(NLS), Program Accounting System
(PAS), and others continue to support
program fund transactions related to
grant and loan activities and continue to
interface nightly with HUDCAPS.
The following routine uses have been
removed from the HUDCAPS SORN
completed in 2014 because HUDCAPS
is no longer HUD’s core financial
system/system of record. HUDCAPS is
now a sub-ledger financial system for
HUD, and the Department of Treasury,
Administrative Resource Center (ARC)
Oracle Federal Financials serves as
HUD’s system of record and core
financial system.
• The Internal Revenue Service
(IRS)—for reporting payments for goods
and services and for reporting of
discharge indebtedness;
• The General Service
Administration’s Federal Procurement
Data System, a central repository for
statistical information on Government
contracting, for purposes of providing
public access to Government-wide data
about agency contract actions;
• The consumer reporting agencies:
Disclosure pursuant to 5 U.S.C.
552a(b)(12). Disclosures may be made
from the system to consumer reporting
agencies as defined in the Fair Credit
Reporting Act (15 U.S.C. 1681a(f) or the
Federal Claims Collection Act of 1966,
31 U.S.C. 3701(a)(3)). The disclosure is
limited to information necessary to
establish the identity of the individual,
including name, social security number,
and address; the amount, status, and
history of the claim, and the agency or
program under which the claim arose
for the sole purpose of allowing the
consumer reporting agency to prepare a
credit report.
SYSTEM NAME AND NUMBER
HUD Central Accounting and Program
System (HUDCAPS, A75).
SECURITY CLASSIFICATION:
daltland on DSKBBV9HB2PROD with NOTICES
Unclassified.
SYSTEM MANAGER(S):
Assistant Chief Financial Officer for
Systems, Office of the Chief Financial
Officer, Department of Housing and
Urban Development, 451 Seventh Street
SW, Room 3100, Washington, DC 20410.
AUTHORITY FOR MAINTENANCE OF THE SYSTEM:
Sec. 113 of the Budget and
Accounting Act of 1950, 31 U.S.C. 66a.
(Pub. L. 81–784); The Chief Financial
Officers Act of 1990; Executive Order
9397, as amended by Executive Order
13478; The Housing and Community
Development Act of 1987, 42 U.S.C.
3543.
PURPOSE(S) OF THE SYSTEM:
A75 HUDCAPS is an Office of the
Chief Financial Officer (OCFO) system
that serves as a sub-ledger financial
system for HUD. The sub-ledger
contains Public and Indian Housing
(PIH) Section 8 programmatic
transaction, including payments of PIH
Section 8 programmatic invoices, and
HUD legacy subsidiary systems such as
LOCCS, NLS, PAS, and others, which
will continue to support program fund
transactions related to grant and loan
activities and continue to interface
nightly with HUDCAPS.
POLICIES AND PRACTICES FOR STORAGE OF
RECORDS:
Electronic files are stored on
electronic media. There are no paper
records that are maintained for this
system.
Grant, subsidy, project, and loan
recipients; HUD personnel; vendors;
brokers; bidders; managers; individuals
within Disaster Assistance Programs:
builders, developers, contractors, and
appraisers.
Records are retrieved by name, social
security number, schedule number,
receipt number, voucher number, and
contract number.
CATEGORIES OF RECORDS IN THE SYSTEM:
Retention and disposal is in
accordance with Records Disposition
Schedule 21, HUD Handbook 2225.6.
Records are destroyed or deleted when
no longer necessary for agency business
in accord with applicable federal
standards or in no less than seven years
after last action in accord with
limitations on civil actions by or against
the U.S. Government (28 U.S.C. 2401
and 2415). Data records are purged or
deleted from the system when eligible to
be destroyed using one of the methods
described by the NIST SP 800–88 Rev 1
‘‘Guidelines for Media Sanitization’’
(December 17, 2014).
The system contains the following
employee/vendor information: Vendor/
employee name, Vendor Number (EIN—
Employer Identification Number, SSN—
Social Security Number, and/or TIN—
Tax Identification Number), address,
Data Universal Numbering System
(DUNS), Banking Account/Routing
numbers, and financial data.
Note: Vendor and social security
numbers are no longer being entered in
HUDCAPS, with the exception of
programs handled by the PIH Financial
Management Center (FMC).
For historical purposes, HUDCAPS
stores vendor records for previous travel
records, which includes social security
numbers, bank account numbers, and
routing numbers.
RECORD SOURCE CATEGORIES:
These records contain information
obtained from the individual who is the
subject of the records, HUD personnel,
financial institutions, private
corporations or business partners, and
Federal agencies.
Jkt 244001
1. To the U.S. Treasury—for
transactions such as disbursements of
funds and related adjustments;
2. To other Federal Agencies—for the
purpose of debt collection to comply
with statutory reporting requirements;
3. To HUD contractors when
necessary to perform a function or
service related to this system of records.
Such recipients are required to comply
with the Privacy Act of 1974, as
amended U.S.C. 552a.
In addition to the routine uses
described above and the disclosures
generally permitted under 5 U.S.C.
§ 552a(b) of the Privacy Act, additional
discretionary disclosures that may be
applicable to this system of records
notice can be found in the Department’s
Privacy website under Appendix 1:
HUD’s Routine use Inventory Notice, 80
FR 81837 (December 31, 2015).
POLICIES AND PRACTICES FOR RETRIEVAL OF
RECORDS:
HUD Headquarters, 451 7th Street
SW, Washington, DC 20410 and
NCCIPS, Stennis Space Center, MS
29529. The backup data center is at
Mid-Atlantic Data Center in Clarksville,
VA 23927.
18:17 Mar 13, 2018
ROUTINE USES OF RECORDS MAINTAINED IN THE
SYSTEM, INCLUDING CATEGORIES OF USERS AND
PURPOSES OF SUCH USES:
CATEGORIES OF INDIVIDUALS COVERED BY THE
SYSTEM:
SYSTEM LOCATION:
VerDate Sep<11>2014
11241
PO 00000
Frm 00074
Fmt 4703
Sfmt 4703
POLICIES AND PRACTICES FOR RETENTION AND
DISPOSAL OF RECORDS:
ADMINISTRATIVE, TECHNICAL, AND PHYSICAL
SAFEGUARDS:
All HUD employees have undergone
background investigations. HUD
buildings are guarded and monitored by
security personnel, cameras, ID checks,
and other physical security measures.
Access is restricted to authorized
personnel or contractors whose
responsibilities require access. System
users must take the mandatory security
E:\FR\FM\14MRN1.SGM
14MRN1
11242
Federal Register / Vol. 83, No. 50 / Wednesday, March 14, 2018 / Notices
awareness training annually as
mandated by the Federal Information
Security Management Act (FISMA).
Users must also sign a Rules of Behavior
form certifying that they agree to
comply with the requirements before
they are granted access to the system.
RECORD ACCESS PROCEDURES:
For information, assistance, or inquiry
about records, contact John Bravacos,
Senior Agency Official for Privacy, 451
Seventh Street SW, Room 10139,
Washington, DC 20410, telephone
number (202) 708–3054. When seeking
records about yourself from this system
of records or any other Housing and
Urban Development (HUD) system of
records, your request must conform
with the Privacy Act regulations set
forth in 24 CFR part 16. You must first
verify your identity, meaning that you
must provide your full name, address,
and date and place of birth.
You must sign your request, and your
signature must either be notarized or
submitted under 28 U.S.C. 1746, a law
that permits statements to be made
under penalty of perjury as a substitute
for notarization. In addition, your
request should:
a. Explain why you believe HUD
would have information on you.
b. Identify which Office of HUD you
believe has the records about you.
c. Specify when you believe the
records would have been created.
d. Provide any other information that
will help the Freedom of Information
Act (FOIA), staff determine which HUD
office may have responsive records.
If your request is seeking records
pertaining to another living individual,
you must include a statement from that
individual certifying their agreement for
you to access their records. Without the
above information, the HUD FOIA
Office may not conduct an effective
search, and your request may be denied
due to lack of specificity or lack of
compliance with regulations.
daltland on DSKBBV9HB2PROD with NOTICES
CONTESTING RECORD PROCEDURES:
The Department’s rules for contesting
contents of records and appealing initial
denials appear in 24 CFR part 16,
Procedures for Inquiries. Additional
assistance may be obtained by
contacting John Bravacos, Senior
Agency Official for Privacy, 451 Seventh
Street SW, Room 10139, Washington,
DC 20410, or the HUD Departmental
Privacy Appeals Officers, Office of
General Counsel, Department of
Housing and Urban Development, 451
Seventh Street SW, Washington, DC
20410.
VerDate Sep<11>2014
18:17 Mar 13, 2018
Jkt 244001
NOTIFICATION PROCEDURES:
Individuals seeking notification of
and access to any record contained in
this system of records, or seeking to
contest its content, may submit a
request in writing to HUD’s Privacy
Office at the addresses provided above
or the component’s FOIA Officer, whose
contact information can be found at
https://www.hud.gov/foia.
EXEMPTIONS PROMULGATED FOR THE SYSTEM:
None.
HISTORY:
Docket No. FR–5763–N–03.
Dated: February 16, 2018.
John Bravacos,
Senior Agency Official for Privacy.
[FR Doc. 2018–05070 Filed 3–13–18; 8:45 am]
BILLING CODE 4210–67–P
DEPARTMENT OF THE INTERIOR
Fish and Wildlife Service
[FWS–HQ–FAC–2018–N024; FF09F42300–
FVWF97920900000–XXX]
Sport Fishing and Boating Partnership
Council Meeting
Fish and Wildlife Service,
Interior.
ACTION: Notice of meeting.
AGENCY:
We, the U.S. Fish and
Wildlife Service (Service), announce a
public meeting of the Sport Fishing and
Boating Partnership Council (Council).
A Federal advisory committee, the
Council was created in part to foster
partnerships to enhance public
awareness of the importance of aquatic
resources and the social and economic
benefits of recreational fishing and
boating in the United States. This
meeting is open to the public, and
anyone interested may make oral
statements to the Council or file written
statements for consideration.
DATES: The meeting will take place
April 4, 2018, from 9 a.m. to 4:30 p.m.
(Eastern Time) and April 5, 2018, from
9 a.m. to 4 p.m. For deadlines and
directions on registering to attend the
meeting, submitting written material,
and/or giving an oral presentation,
please see Public Input under
SUPPLEMENTARY INFORMATION.
ADDRESSES: The meeting will be held at
the Department of the Interior, 1849 C
Street NW, Room 5160, Washington, DC
20240.
FOR FURTHER INFORMATION CONTACT:
Linda Friar, Designated Federal Officer,
Sport Fishing and Boating Partnership
Council, 5275 Leesburg Pike, Mailstop
SUMMARY:
PO 00000
Frm 00075
Fmt 4703
Sfmt 4703
FAC, Falls Church, VA 22041;
telephone (703) 358–2056; fax (703)
358–2487; or email linda_friar@fws.gov.
SUPPLEMENTARY INFORMATION: In
accordance with the requirements of the
Federal Advisory Committee Act, 5
U.S.C. App., we announce that the Sport
Fishing and Boating Partnership
Council will hold a meeting April 4 and
5, 2018.
Background
The Council was formed in January
1993 under the provisions of 41 CFR
101–6.1007 to advise the Secretary of
the Interior, through the Director of the
U.S. Fish and Wildlife Service, on
aquatic conservation endeavors that
benefit recreational fishery resources
and recreational boating and that
encourage partnerships among industry,
the public, and government. The
Council represents the interests of the
public and private sectors of the
recreational fishing, boating, and
conservation communities and is
organized to enhance partnerships
among industry, constituency groups,
and government. The 18-member
Council, appointed by the Secretary of
the Interior, includes, as ex officio
members, the Service Director and the
president of the Association of Fish and
Wildlife Agencies. Other Council
members are directors from State
agencies responsible for managing
recreational fish and wildlife resources
and individuals who represent the
interests of saltwater and freshwater
recreational fishing, recreational
boating, the recreational fishing and
boating industries, recreational fisheries
resource conservation, Native American
tribes, aquatic resource outreach and
education organizations, and tourism.
Additional background information on
the Council is available at https://
www.fws.gov/sfbpc.
Meeting Agenda
An abbreviated list of planned agenda
items for the meeting includes:
• Review the Report to the Assistant
Secretary for Fish and Wildlife and
Parks, Subject: Response to Secretary’s
Order 3347—Conservation Stewardship
and Outdoor Recreation which was
prepared by the Assistant Secretaries for
Fish and Wildlife and Parks and Land
and Minerals Management; this report
provides recommendations to enhance
and expand recreational fishing access;
• Based on the report, develop
consensus-based Council
recommendations to enhance and
expand recreational fishing access;
• Hear and discuss updates on several
U.S. Fish and Wildlife Service programs
and other Council business.
E:\FR\FM\14MRN1.SGM
14MRN1
]]>Agencies
[Federal Register Volume 83, Number 50 (Wednesday, March 14, 2018)]
[Notices]
[Pages 11240-11242]
From the Federal Register Online via the Government Publishing Office [www.gpo.gov]
[FR Doc No: 2018-05070]
=======================================================================
-----------------------------------------------------------------------
DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT
[Docket No. FR-7009-N-04]
A75-HUD Central Accounting and Program System (HUDCAPS) Privacy
Act of 1974; System of Records
AGENCY: Department of Housing and Urban Development.
ACTION: Notice of a modified system of records.
-----------------------------------------------------------------------
SUMMARY: A75 HUDCAPS is an Office of the Chief Financial Officer (OCFO)
system that serves as a sub-ledger financial system for HUD. As of
October 1, 2015, HUDCAPS is no longer HUD's core financial system/
system of record due to the implementation of New Core Project Phase 1
Release 3. HUDCAPS is now a sub-ledger financial system for HUD and the
Department of Treasury, Administrative Resource Center (ARC) Oracle
Federal Financials serves as HUD's system of record and core financial
system.
DATES: April 13, 2018.
ADDRESSES: You may submit comments, identified by docket number and
title, by one of the following methods:
Email: [email protected].
Mail: John Bravacos, Senior Agency Official for Privacy, Privacy
Office, Department of Housing and Urban Development, Washington, DC
20410.
FOR FURTHER INFORMATION CONTACT: For general questions please contact:
The Privacy Office, 451 Seventh Street SW, Room 10139, Washington, DC
20410, telephone number 202-708-3054. Individuals who are hearing- or
speech-impaired may access this number via TTY by calling the Federal
Relay Service at 800-877-8339 (this is a toll-free number).
SUPPLEMENTARY INFORMATION: This notice of revision of the System of
Records Notice for A75 HUDCAPS reflects the change of HUDCAPS from a
core financial system to a sub-ledger financial system for HUD. The
Department of Treasury, Administrative Resource Center (ARC) Oracle
Federal Financials now serves as HUD's system of record and core
financial system.
The following transactions remain in HUDCAPS:
Public and Indian Housing (PIH) Section 8 programmatic
transaction,
[[Page 11241]]
including payments of PIH Section 8 programmatic invoices.
Program Accounting System (PAS) will continue to transmit
current transactional activity to HUDCAPS for posting to the HUDCAPS
sub ledger, which is transmitted through NCIS to the Oracle Federal
Financials G/L.
HUD legacy subsidiary systems such as Line of Credit
Control System (LOCCS), Northridge Loan System (NLS), Program
Accounting System (PAS), and others continue to support program fund
transactions related to grant and loan activities and continue to
interface nightly with HUDCAPS.
The following routine uses have been removed from the HUDCAPS SORN
completed in 2014 because HUDCAPS is no longer HUD's core financial
system/system of record. HUDCAPS is now a sub-ledger financial system
for HUD, and the Department of Treasury, Administrative Resource Center
(ARC) Oracle Federal Financials serves as HUD's system of record and
core financial system.
The Internal Revenue Service (IRS)--for reporting payments
for goods and services and for reporting of discharge indebtedness;
The General Service Administration's Federal Procurement
Data System, a central repository for statistical information on
Government contracting, for purposes of providing public access to
Government-wide data about agency contract actions;
The consumer reporting agencies: Disclosure pursuant to 5
U.S.C. 552a(b)(12). Disclosures may be made from the system to consumer
reporting agencies as defined in the Fair Credit Reporting Act (15
U.S.C. 1681a(f) or the Federal Claims Collection Act of 1966, 31 U.S.C.
3701(a)(3)). The disclosure is limited to information necessary to
establish the identity of the individual, including name, social
security number, and address; the amount, status, and history of the
claim, and the agency or program under which the claim arose for the
sole purpose of allowing the consumer reporting agency to prepare a
credit report.
SYSTEM NAME AND NUMBER
HUD Central Accounting and Program System (HUDCAPS, A75).
SECURITY CLASSIFICATION:
Unclassified.
SYSTEM LOCATION:
HUD Headquarters, 451 7th Street SW, Washington, DC 20410 and
NCCIPS, Stennis Space Center, MS 29529. The backup data center is at
Mid-Atlantic Data Center in Clarksville, VA 23927.
SYSTEM MANAGER(S):
Assistant Chief Financial Officer for Systems, Office of the Chief
Financial Officer, Department of Housing and Urban Development, 451
Seventh Street SW, Room 3100, Washington, DC 20410.
AUTHORITY FOR MAINTENANCE OF THE SYSTEM:
Sec. 113 of the Budget and Accounting Act of 1950, 31 U.S.C. 66a.
(Pub. L. 81-784); The Chief Financial Officers Act of 1990; Executive
Order 9397, as amended by Executive Order 13478; The Housing and
Community Development Act of 1987, 42 U.S.C. 3543.
PURPOSE(S) OF THE SYSTEM:
A75 HUDCAPS is an Office of the Chief Financial Officer (OCFO)
system that serves as a sub-ledger financial system for HUD. The sub-
ledger contains Public and Indian Housing (PIH) Section 8 programmatic
transaction, including payments of PIH Section 8 programmatic invoices,
and HUD legacy subsidiary systems such as LOCCS, NLS, PAS, and others,
which will continue to support program fund transactions related to
grant and loan activities and continue to interface nightly with
HUDCAPS.
CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM:
Grant, subsidy, project, and loan recipients; HUD personnel;
vendors; brokers; bidders; managers; individuals within Disaster
Assistance Programs: builders, developers, contractors, and appraisers.
CATEGORIES OF RECORDS IN THE SYSTEM:
The system contains the following employee/vendor information:
Vendor/employee name, Vendor Number (EIN--Employer Identification
Number, SSN--Social Security Number, and/or TIN--Tax Identification
Number), address, Data Universal Numbering System (DUNS), Banking
Account/Routing numbers, and financial data.
Note: Vendor and social security numbers are no longer being
entered in HUDCAPS, with the exception of programs handled by the PIH
Financial Management Center (FMC).
For historical purposes, HUDCAPS stores vendor records for previous
travel records, which includes social security numbers, bank account
numbers, and routing numbers.
RECORD SOURCE CATEGORIES:
These records contain information obtained from the individual who
is the subject of the records, HUD personnel, financial institutions,
private corporations or business partners, and Federal agencies.
ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES
OF USERS AND PURPOSES OF SUCH USES:
1. To the U.S. Treasury--for transactions such as disbursements of
funds and related adjustments;
2. To other Federal Agencies--for the purpose of debt collection to
comply with statutory reporting requirements;
3. To HUD contractors when necessary to perform a function or
service related to this system of records. Such recipients are required
to comply with the Privacy Act of 1974, as amended U.S.C. 552a.
In addition to the routine uses described above and the disclosures
generally permitted under 5 U.S.C. Sec. 552a(b) of the Privacy Act,
additional discretionary disclosures that may be applicable to this
system of records notice can be found in the Department's Privacy
website under Appendix 1: HUD's Routine use Inventory Notice, 80 FR
81837 (December 31, 2015).
POLICIES AND PRACTICES FOR STORAGE OF RECORDS:
Electronic files are stored on electronic media. There are no paper
records that are maintained for this system.
POLICIES AND PRACTICES FOR RETRIEVAL OF RECORDS:
Records are retrieved by name, social security number, schedule
number, receipt number, voucher number, and contract number.
POLICIES AND PRACTICES FOR RETENTION AND DISPOSAL OF RECORDS:
Retention and disposal is in accordance with Records Disposition
Schedule 21, HUD Handbook 2225.6. Records are destroyed or deleted when
no longer necessary for agency business in accord with applicable
federal standards or in no less than seven years after last action in
accord with limitations on civil actions by or against the U.S.
Government (28 U.S.C. 2401 and 2415). Data records are purged or
deleted from the system when eligible to be destroyed using one of the
methods described by the NIST SP 800-88 Rev 1 ``Guidelines for Media
Sanitization'' (December 17, 2014).
ADMINISTRATIVE, TECHNICAL, AND PHYSICAL SAFEGUARDS:
All HUD employees have undergone background investigations. HUD
buildings are guarded and monitored by security personnel, cameras, ID
checks, and other physical security measures. Access is restricted to
authorized personnel or contractors whose responsibilities require
access. System users must take the mandatory security
[[Page 11242]]
awareness training annually as mandated by the Federal Information
Security Management Act (FISMA). Users must also sign a Rules of
Behavior form certifying that they agree to comply with the
requirements before they are granted access to the system.
RECORD ACCESS PROCEDURES:
For information, assistance, or inquiry about records, contact John
Bravacos, Senior Agency Official for Privacy, 451 Seventh Street SW,
Room 10139, Washington, DC 20410, telephone number (202) 708-3054. When
seeking records about yourself from this system of records or any other
Housing and Urban Development (HUD) system of records, your request
must conform with the Privacy Act regulations set forth in 24 CFR part
16. You must first verify your identity, meaning that you must provide
your full name, address, and date and place of birth.
You must sign your request, and your signature must either be
notarized or submitted under 28 U.S.C. 1746, a law that permits
statements to be made under penalty of perjury as a substitute for
notarization. In addition, your request should:
a. Explain why you believe HUD would have information on you.
b. Identify which Office of HUD you believe has the records about
you.
c. Specify when you believe the records would have been created.
d. Provide any other information that will help the Freedom of
Information Act (FOIA), staff determine which HUD office may have
responsive records.
If your request is seeking records pertaining to another living
individual, you must include a statement from that individual
certifying their agreement for you to access their records. Without the
above information, the HUD FOIA Office may not conduct an effective
search, and your request may be denied due to lack of specificity or
lack of compliance with regulations.
CONTESTING RECORD PROCEDURES:
The Department's rules for contesting contents of records and
appealing initial denials appear in 24 CFR part 16, Procedures for
Inquiries. Additional assistance may be obtained by contacting John
Bravacos, Senior Agency Official for Privacy, 451 Seventh Street SW,
Room 10139, Washington, DC 20410, or the HUD Departmental Privacy
Appeals Officers, Office of General Counsel, Department of Housing and
Urban Development, 451 Seventh Street SW, Washington, DC 20410.
NOTIFICATION PROCEDURES:
Individuals seeking notification of and access to any record
contained in this system of records, or seeking to contest its content,
may submit a request in writing to HUD's Privacy Office at the
addresses provided above or the component's FOIA Officer, whose contact
information can be found at https://www.hud.gov/foia.
EXEMPTIONS PROMULGATED FOR THE SYSTEM:
None.
HISTORY:
Docket No. FR-5763-N-03.
Dated: February 16, 2018.
John Bravacos,
Senior Agency Official for Privacy.
[FR Doc. 2018-05070 Filed 3-13-18; 8:45 am]
BILLING CODE 4210-67-P
