Draft Performance Work Statement.pdf

Performance Work Statement (PWS)

NSPIRE Nextgen SYSTEM

Development, Modernization and Enhancements (DME)

5/15/2026

Version 2.0

(Draft)

Table of Contents

Vision Statement

1 General Information

1.1 Scope of Work

1.2 Background

1.3 Constraints

1.3.1 Project Planning and Management

1.4 Non-Personal Services

1.5 Period of Performance

1.6 Place of Performance

1.7 Hours of Operation

1.8 Special Qualifications

1.9 Post Award/Kickoff Conference

1.10 Status Meetings

1.11 Contractor Travel

1.12 Transition-In

1.13 Transition-Out

2 Definitions and Acronyms

2.1 Definitions

2.2 Acronyms

3 Government-Furnished Property and Services

3.1 Government Services

3.2 Facilities

3.3 Equipment

3.4 Materials and Information

3.5 Quality Assurance (QA)

4 Contractor-Furnished Items and Services

4.1 Facilities

4.2 Equipment

4.3 Materials

4.4 Contractor Responsibilities

4.5 Contractor Personnel

4.6 Identification of Contractor Employees

5 Specific Tasks

5.1 Transition In Plan

5.2 Program and Project Management

5.2.1 Project Management Plan (PMP)

5.2.2 Project Status Reports

Kick-off Meeting

5.3 Core Stability & Continuity

5.4 Field Inspection Application

5.5 Inventory & Profile Management

5.6 Ordering & Scheduling

5.7 Health & Safety Defects

5.8 Inspection Quality Control Review

5.9 Analytics & Reporting

5.10 Appeals & Technical Reviews

5.11 Vendor, Property, & Inspector Administration

5.12 Protocols, Standards & Technical Assistance Center (TAC) Integration

5.13 Training

5.14 System Security Compliance

5.15 Agile Sprint Planning

5.16 User Acceptance Testing (UAT)

5.17 CI/CD Release Software Package

5.18 Support Installation and Coordination

5.19 Change Management and Communications

5.20 Transition-Out

6 Deliverables

6.1 Quality Control Plan

6.2 Acceptance Criteria

7 Related Documents

8 Performance Requirements Summary

Performance Work Statement (PWS)

Vision Statement

The vision for the NSPIRE system is to deliver a modern, reliable, and user-centered platform that standardizes inspections, improves data accuracy, and streamlines workflows. The solution will replace a fragmented, manual processes with a scalable and secure digital ecosystem that supports real-time data access, automation, and consistent outcomes.

1 General Information

1.1 Scope of Work

The U.S. Department of Housing and Urban Development (HUD), Office of the Chief

Information Officer (OCIO) requires contractor support services to perform Development

Modernization Enhancement (DME) work to stabilize, modernize, and operationally sustain the

National Standards for the Physical Inspection of Real Estate (NSPIRE) inspection program

(NSPIRE NextGen Services). NSPIRE NextGen Services include reviewing business and technical needs, developing reports in an application that supports not only Public Indian

Housing (PIH)requirements but also those of HUD internal customers such as the Federal

Housing Administration (FHA) Office of Multifamily Housing (MFH), the Office of the HUD Chief

Financial Officer (OCFO), and external customers such as Public Housing Authorities (PHAs), owners, and agents.

Additionally, the Contractor must have deep product management, data query development, and experience in implementing reporting solutions using an approved, highly customizable business intelligence platform. As part of the Contractor’s solution, HUD requires a highly customizable, COTS inspection software or XaaS platform (NSPIRE NextGen System) that can accommodate the NSPIRE inspection process and life cycle to properly support our mission of ensuring safe, decent, and sanitary housing for our HUD-assisted tenants.

NSPIRE NextGen Services must meet modernization objectives capabilities for HUD’s stakeholder needs and services including:

• Stabilize inspection operations and prevent data loss.

• Support scalable, concurrent field inspections with offline capability.

• Replace manual and fragmented workflows with automated, auditable processes.

• Improve transparency and usability for internal and external stakeholders.

• Establish a modular architecture capable of supporting future NSPIRE phases without re-platforming.

The NSPIRE NextGen System must deliver targeted enhancements across the following system modules areas:

• Inspector Mobile Application

• Field Office Application

• Scheduling Application

• Vendor Management Application

• Quality Control Application

Internal HUD reporting provided in Section 5 of the PWS will detail specific requirements and tasks for each of the system modules listed above.

Successful NSPIRE NextGen System adoption requires a robust change management program embedded in the Contractor’s NSPIRE NextGen Services solution. This includes training development and delivery, updated materials, stakeholder communications, and operational readiness support for Assessment and Recovery Center (ARC), HUD field offices, Property Owners/Agents (POAs), HUD contractors, and inspectors.

Detailed descriptions of specific tasks are provided in Section 5 – Specific Tasks.

As part of the NSPIRE NextGen Services, the Contractor must provide support to OCIO to strengthen its Information Technology (IT) planning and operations function. NSPIRE NextGen

Services shall include analyzing current OCIO policies and procedures and providing recommendations to assist with the modernization of those policies and procedures. In addition, the Contractor must provide support to train HUD staff on all new processes.

The Contractor shall provide support services to monitor and validate the quality and effectiveness of out-sourced infrastructure managed services through program oversight and analysis, and provide resultant recommendations to the Government. The NSPIRE NextGen

System support services include:

• Program and Project Management

• Core Stability & Continuity

• Field Inspection Application

• Inventory & Profile Management

• Ordering & Scheduling

• Health & Safety Defects

• Inspection Quality Control Review

• Analytics & Reporting

• Appeals & Technical Reviews

• Vendor, Property, & Inspector Administration

• Protocols, Standards & Technical Assistance Center (TAC) Integration

• Training

• System Security Compliance

• Agile Sprint Planning

• User Acceptance Testing (UAT)

• Continuous Integration and Continuous Deployment (CI/CD pipeline Release Software

Package

• Support Installation and Coordination

• Change Management and Communications

Detailed descriptions of specific tasks are provided in Section 5 – Specific Tasks and Deliverables.

1.2 Background

All application data, artificial intelligence (AI) model outputs, configurations, and customizations are HUD property. HUD holds all rights, title, and interest in AI inputs, outputs, and queries, ensuring complete control over their use, access, modification, and disposition. Any data generated or utilized within the platform remains under HUD's sole authority. All deliverables—including source code, configuration files, documentation, and data—must be stored in a Government-approved repository.

HUD possesses unrestricted rights to utilize any AI models and their outputs for future training, retraining, development, and enhancement of its AI capabilities and the platform itself. This ensures HUD's complete ability to evolve and adapt its systems without impediment. Any AI models used on HUD data must comply with HUD and Federal AI usage policies, and the terms of this Task Order.

The ARC performs physical and financial assessments of affordable housing properties in

HUD’s portfolio in support of HUD’s oversight responsibilities - ensuring HUD-assisted housing meets minimal compliance thresholds. These assessments include routine, annual compliance requirements as well as more sophisticated analyses of collected data. ARC has determined that continued reengineering of its processes and reorienting its business model would enable it to streamline and integrate data collected and analyses produced in support of the Secretary’s priorities to build a stronger HUD and help families secure safe, quality housing.

ARC is developing and will be implementing a new NSPIRE model to further manage the physical inspection line of business. The NSPIRE NextGen Contractor must provide support service that includes the deployment of revised inspection standards and protocols; business processes; and Information Technology (IT) and support systems. This effort will improve transparency and alignment through enhanced standardized, repeatable processes and electronic submission of data to HUD. As a result, HUD will realize a more reliable, consistent, objective inspection standard across the department to ensure that families reside in decent, safe, and healthy housing. ARC has started, and will continue, to develop, document, and propose standards and protocols for a revised NSPIRE inspection model. During the performance of this contract, the Contractor shall migrate current NSPIRE functionality from the existing NSPIRE model to the enhanced NSPIRE Next Gen solution. More specifically, the enhanced NSPIRE NextGen implementation, as part of the NSPIRE NextGen System, must include, but is not limited to, advancing the following functionality:

• Ideal Future Date (IFD) management – the current NSPIRE model does not include a proper inventory management system. The enhanced NSPIRE module, using IFD, defines when a property needs to be inspected based on the various program business rules.

• Profile workflow – Enable workflow with HUD field office and POAs to validate and update property and user profiles. This functionality was not implemented in the current NSPIRE model.

• Procurement Module – Including the reverse auction process (RAP) and legacy financial tool capability (PASSFACS) – Physical Assessment Subsystem

Financial Accounting Control System and NIC and Backlog integration.

• Protocols & Standards – Standards and Protocol management capabilities in the

NSPIRE NextGen System must provide:

o Future AI capability to support local and state code impacts to standards.

o Impacts Appeals module.

o Portal –a standards portal or module to facilitate easy changes/updates to impacts items such as standards textual changes;

deficiencies lists; Health and Safety (H&S) criteria; scoring weights, etc.

o TAC Integration – the NSPIRE System must integrate with the

TAC.

1.3 Constraints

The services identified in this PWS must adhere to the rules, regulations, laws, standards, and conventions identified by HUD as well as within the Federal Government. Constraints include the following:

• The Contractor shall prepare Project Planning and Management PPM documentation in accordance with the format and content specified in the PPM templates at http://hudatwork.hud.gov/po/i/itm/ppm/ppm.cfm. The HUD PPM guide takes precedence in the event of inconsistencies between the PPM

Guide and its corresponding PPM templates and PPM Checklists.

Document Number

Title & URL Released Mandatory

Advisory

N/A HUD Web Policies and Standards http://www.hud.gov/library/bookshelf11

Current version

M

N/A World Wide Web Consortium (W3C) standards (http://www.w3.org) Current version

M

N/A Government web management policies and best practices (http://digital.gov) Current version

M

FIPS 199

FIPS 199 Standards for Security Categorization of Federal Information and Information Systems https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.199.pdf

2004 M

Public Law No: 113-283

The Federal Information Security Modernization Act of 2014

PUBL283.PS

2014 M http://hudatwork.hud.gov/po/i/itm/ppm/ppm.cfm http://www.hud.gov/library/bookshelf11 http://www.w3.org/ http://digital.gov/ https://nvlpubs.nist.gov/nistpubs/fips/nist.fips.199.pdf https://www.govinfo.gov/content/pkg/PLAW-113publ283/pdf/PLAW-113publ283.pdf

44 USC

§3601 et seq.

E-Government Act of 2002 http://www.gpo.gov/fdsys/pkg/USCODE-2010-title44/pdf/USCODE-2010-title44-chap36.pdf

2002 M

Pub. L. 103-

62, 31 USC

§1101

Government Performance and Results Act (GPRA) https://www.govinfo.gov/content/pkg/USCODE-2015-title31/pdf/USCODE- 2015-title31-subtitleVI-chap97-sec9705.pdf

1993 M

Pub. L. 104-

106, 40 USC

§1401 et seq.

Information Technology Management Reform Act of 1996 (Clinger-Cohen Act) http://www.gpo.gov/fdsys/pkg/USCODE-1998-title40/pdf/USCODE-1998-title40-chap25.pdf

1996 M

31 USC §

9101 et seq

Government Corporation Control Act http://www.gpo.gov/fdsys/pkg/USCODE-2008-title31/pdf/USCODE-2008-title31-subtitleVI-chap91.pdf

1948 M

Pub. L. 101-

235, 12 USC

1709(f-16)

HUD Reform Act, amending the National Housing Act http://www.gpo.gov/fdsys/pkg/USCODE-2011-title12/pdf/USCODE-2011-title12-chap13-subchapII-sec1709.pdf

1989 M

Pub. L. 105- 277 (112

STAT. 2681-

749-751), 44

USC §3504

Government Paperwork Elimination Act http://www.gpo.gov/fdsys/pkg/PLAW-105publ277/pdf/PLAW-105publ277.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2008-title44/pdf/USCODE-2008-title44-chap35-subchapI-sec3504.pdf

1998 M

29 USC 749d Section 508 of the Rehabilitation Act of 1998 https://www.law.cornell.edu/uscode/text/29/794d

1998 M

Pub. L. 104-

134, 31 USC

§3701 et seq.

Debt Collection Improvement Act of 1996 http://www.gpo.gov/fdsys/pkg/USCODE-2010-title31/pdf/USCODE-2010-title31-subtitleIII-chap37.pdf

1996 M

Pub. L. 113-

101, 31 USC

§3716(c)(6)

Digital and Transparency Act of 2014 http://www.gpo.gov/fdsys/pkg/PLAW-113publ101/pdf/PLAW-113publ101.pdf

2014 M

Pub. L. 97-

177, 31 USC

§3901 et seq.

Prompt Payment Act https://uscode.house.gov/view.xhtml?path=/prelim@title31/subtitle3/chapter3

9&edition=prelim 1982 M

Pub. L. 107-

300, 31 USC

§3321

Improper Payments Information Act of 2002 http://www.gpo.gov/fdsys/pkg/USCODE-2011-title31/pdf/USCODE-2011-title31-subtitleIII-chap33-subchapII-sec3321.pdf

2002 M

Pub. L. 112-

248 , 31 USC

§3321

Improper Payments Elimination and Recovery Improvement Act of 2012 http://www.gpo.gov/fdsys/pkg/PLAW-112publ248/pdf/PLAW-112publ248.pdf

2012 M

5 CFR Part

Prompt Payment https://www.fiscal.treasury.gov/files/prompt-payment/5cfr1315.pdf

Latest version

M

OMB Circular A- 123 Appendix D -

Policies and Standards for Financial Management Systems https://www.whitehouse.gov/wp- https://www.whitehouse.gov/wp-content/uploads/2022/12/M_23-06-Appendix-D_final.pdf

Latest version

M

OMB Circular A-130

Security of Federal Automated Information Resources (Appendix III) https://obamawhitehouse.archives.gov/omb/circulars_a130_a130appendix_iii

Latest version

M

OMB Circular A-130

Management of Federal Information Resources https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/OMB/cir culars/a130/a130revised.pdf

Latest version

M http://www.gpo.gov/fdsys/pkg/USCODE-2010-title44/pdf/USCODE-2010-title44-chap36.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2010-title44/pdf/USCODE-2010-title44-chap36.pdf https://www.govinfo.gov/content/pkg/USCODE-2015-title31/pdf/USCODE-2015-title31-subtitleVI-chap97-sec9705.pdf https://www.govinfo.gov/content/pkg/USCODE-2015-title31/pdf/USCODE-2015-title31-subtitleVI-chap97-sec9705.pdf http://www.gpo.gov/fdsys/pkg/USCODE-1998-title40/pdf/USCODE-1998-title40-chap25.pdf http://www.gpo.gov/fdsys/pkg/USCODE-1998-title40/pdf/USCODE-1998-title40-chap25.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2008-title31/pdf/USCODE-2008-title31-subtitleVI-chap91.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2008-title31/pdf/USCODE-2008-title31-subtitleVI-chap91.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2011-title12/pdf/USCODE-2011-title12-chap13-subchapII-sec1709.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2011-title12/pdf/USCODE-2011-title12-chap13-subchapII-sec1709.pdf http://www.gpo.gov/fdsys/pkg/PLAW-105publ277/pdf/PLAW-105publ277.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2008-title44/pdf/USCODE-2008-title44-chap35-subchapI-sec3504.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2008-title44/pdf/USCODE-2008-title44-chap35-subchapI-sec3504.pdf https://www.law.cornell.edu/uscode/text/29/794d http://www.gpo.gov/fdsys/pkg/USCODE-2010-title31/pdf/USCODE-2010-title31-subtitleIII-chap37.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2010-title31/pdf/USCODE-2010-title31-subtitleIII-chap37.pdf http://www.gpo.gov/fdsys/pkg/PLAW-113publ101/pdf/PLAW-113publ101.pdf https://uscode.house.gov/view.xhtml?path=/prelim@title31/subtitle3/chapter39&edition=prelim https://uscode.house.gov/view.xhtml?path=/prelim@title31/subtitle3/chapter39&edition=prelim http://www.gpo.gov/fdsys/pkg/USCODE-2011-title31/pdf/USCODE-2011-title31-subtitleIII-chap33-subchapII-sec3321.pdf http://www.gpo.gov/fdsys/pkg/USCODE-2011-title31/pdf/USCODE-2011-title31-subtitleIII-chap33-subchapII-sec3321.pdf http://www.gpo.gov/fdsys/pkg/PLAW-112publ248/pdf/PLAW-112publ248.pdf https://www.fiscal.treasury.gov/files/prompt-payment/5cfr1315.pdf https://www.whitehouse.gov/wp-https://www.whitehouse.gov/wp-content/uploads/2022/12/M_23-06-Appendix-D_final.pdf https://www.whitehouse.gov/wp-content/uploads/2022/12/M_23-06-Appendix-D_final.pdf https://obamawhitehouse.archives.gov/omb/circulars_a130_a130appendix_iii https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/OMB/circulars/a130/a130revised.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/OMB/circulars/a130/a130revised.pdf

OMB Circular A-130

Security of Federal Automated Information Resources (Appendix III) (see also 34 FR 6428) https://www.govinfo.gov/content/pkg/GPO-UA-1996-05-13/pdf/GPO-UA- 1996-05-13-34.pdf

Latest version

M

OMB

Memorandum M-17-12

Preparing for and Responding to a Breach of Personally Identifiable Information https://bidenwhitehouse.archives.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/m-17-12_0.pdf

January 3, M

GAO-08-343

Information Security: Protecting Personally Identifiable Information https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-08- 343/html/GAOREPORTS-GAO-08-343.htm

2008 M

OMB

Memorandum M-17-26

Reducing Burden for Federal Agencies by Rescinding and Modifying OMB Memoranda https://bidenwhitehouse.archives.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/M-17-26.pdf

2017 M

OMB

Memorandum M-18-20

Appendix C to OMB Circular A-123, Requirements for Payment Integrity Improvement https://bidenwhitehouse.archives.gov/wp-content/uploads/2018/06/M-18- 20.pdf

2018 M

PDD-63

Presidential Decision Directive-63 on Critical Infrastructure Protection: Sector Coordinators https://www.govinfo.gov/content/pkg/FR-1998-08-05/pdf/98-20865.pdf

1998 M

HSPD-12

Homeland Security Presidential Directive 12:Policy for a Common Identification Standard for Federal Employees and Contractors, Homeland Security Presidential Directive-12 http://www.dhs.gov/homeland-security-presidential-directive-12

2004 M

NIST Special Publication 800-12 Rev. 1

An Introduction to Computer Security http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

M

NIST Special Publication 800-18, Rev.

Guide for Developing Security Plans for Federal Information Systems http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

NIST Special Publication 800-30, Rev

Guide for Conducting Risk Assessments http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

M

NIST Special Publication 800-34, Rev.

Contingency Planning Guide for Information Technology Systems http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

M

NIST Special Publication 800-35

Guide to Information Technology Security Services http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

M

NIST Special Publication 800-37 Rev 2

Risk Management Framework for Information Systems and Organizations: A System Life Cycle Approach for Security and Privacy http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

M

NIST Special Publication 800-47 Rev.

Managing the Security of Information Exchanges http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A https://www.govinfo.gov/content/pkg/GPO-UA-1996-05-13/pdf/GPO-UA-1996-05-13-34.pdf https://www.govinfo.gov/content/pkg/GPO-UA-1996-05-13/pdf/GPO-UA-1996-05-13-34.pdf https://bidenwhitehouse.archives.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/m-17-12_0.pdf https://bidenwhitehouse.archives.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2017/m-17-12_0.pdf https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-08-343/html/GAOREPORTS-GAO-08-343.htm https://www.govinfo.gov/content/pkg/GAOREPORTS-GAO-08-343/html/GAOREPORTS-GAO-08-343.htm https://bidenwhitehouse.archives.gov/wp-content/uploads/2018/06/M-18-20.pdf https://bidenwhitehouse.archives.gov/wp-content/uploads/2018/06/M-18-20.pdf http://www.dhs.gov/homeland-security-presidential-directive-12 http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html

NIST Special Publication 800-53 Rev 5

Security and Privacy Controls for Information Systems and Organizations http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

NIST Special Publication 800-53A Rev

Assessing the Security Controls in Federal Information Systems and Organizations http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

NIST Special Publication 800-55 Vol. 1

Measurement Guide for Information Security: Volume 1 – Identifying and Selecting Measures http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

NIST

Special Publication

800-55 Vol 2

Measurement Guide for Information Security: Volume 2 – Developing an Information Security Measurement Program

Latest Version

A

NIST Special Publication 800-60 Rev 2

Guide for Mapping Types of Information and Information Systems to Security Categories (Appendices) http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

NIST Special Publication 800-60, Vol 1, Rev 1

Guide for Mapping Types of Information and Information Systems to Security Categories

Latest Version

A

NIST Special Publication 800-60, Vol 2, Rev 1

Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices

Latest Version

A

NIST Special Publication 800-82 Rev. 4

Pre-Draft Call for Comments: Guide to Operational Technology (OT) Security http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

NIST Special Publication 800-100

Information Security Handbook: A Guide for Managers http://csrc.nist.gov/publications/PubsSPs.html

Latest Version

A

US SGL

United States Standard General Ledger https://www.fiscal.treasury.gov/fsreports/ref/ussgl/ussgl_home.htm

M

SF-224

Monthly Statement of Transactions (FMS Form 224) https://fiscal.treasury.gov/reports-statements/fbwt/about.html

M

General Accounting Office, GAO- 02-45

HUD MANAGEMENT: Progress Made on Management Reforms, but Challenges Remain http://www.gao.gov/assets/240/232993.pdf

October

A

GAO/AIMD-

00-33

GAO Redbook Information Security Risk Assessment Practices of Leading Organizations http://www.gao.gov/assets/200/199976.pdf

Nov 1999 A

IEEE 730-

Approved Draft Standard for Software Quality Assurance Process

IEEE SA - IEEE 730-2026

Latest Version

M

IEEE

29148:2011

ISO/IEC/IEEE International Standard - Systems and software engineering -- Life cycle processes --Requirements engineering https://standards.ieee.org/ieee/29148/5289/

Latest Version

M

IEEE 1012-

IEEE Standard for System, Software, and Hardware Verification and Validation https://standards.ieee.org/ieee/1012/7324/

Latest Version http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html http://csrc.nist.gov/publications/PubsSPs.html https://www.fiscal.treasury.gov/fsreports/ref/ussgl/ussgl_home.htm https://fiscal.treasury.gov/reports-statements/fbwt/about.html http://www.gao.gov/assets/240/232993.pdf http://www.gao.gov/assets/200/199976.pdf https://standards.ieee.org/ieee/730/10854/ https://standards.ieee.org/ieee/29148/5289/ https://standards.ieee.org/ieee/1012/7324/

IEEE/ISO/IEC

12207-26

ISO/IEC/IEEE International Standard-Systems and software engineering – Software life cycle processes https://standards.ieee.org/ieee/12207/11416/

Latest Version

M

IEE/ISO/IEC

15288-2023

ISO/IEC/IEEE International Standard - Systems and software engineering -- System life cycle processes https://standards.ieee.org/ieee/15288/10424/

Latest Version

M

IEE/ISO/IEC

16326-2019

ISO/IEC/IEEE International Standard - Systems and software engineering - Life cycle processes - Project Management https://standards.ieee.org/ieee/16326/6769/

Latest Version

M

IEE/ISO/IEC

23026-2023

ISO/IEC/IEEE International Standard - Systems and Software Engineering – Engineering and Management of Websites for Systems, Software, and Services Information https://standards.ieee.org/ieee/23026/10425/

Latest Version

M

IEEE/ISO/IEC

29148-2018

ISO/IEC/IEEE International Standard - Systems and software engineering – Life cycle processes – Requirements engineering https://standards.ieee.org/ieee/29148/6937/

Latest Version

M

ISO/IEC/IEEE

42010:2011

Systems and software engineering — Architecture description

Latest Version

M

HUD

Handbook 1325.01, REV-01

Privacy Act Handbook http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hud clips/handbooks/admh/1325.1 Sept 1995 M http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hud clips/handbooks/hsgh/2226.1

HUD

Handbook 2400.25

REV4

Information Technology Security Policy itsechand_43865.pdf

Latest Version

M

HUD

Handbook

3255.1 V2

Enterprise Architecture Policy 32551CIOH.pdf

Latest Version

M

Project Planning and Management V2.0

Project Planning and Management V2.0 Project Planning and Management V2.0 | HUD.gov / U.S. Department of Housing and Urban Development (HUD)

Latest Version

M

N/A

HUD Project Planning and Management (PPM) Site: Project Type Guides, Tools, and Artifact Templates http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ppm/PPMV20

HOME

Latest Versions

M

N/A HUD Enterprise Architecture Program http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ea/newea

Latest Version

M

N/A HUD Enterprise Test Center (HTC) Policy http://hudatwork.hud.gov/HUD/cio/po/i/it/sd/devlife/bld/testcenter/tcpolicy_toc

NIST Special Publication 800-34 Rev. 1

Contingency Planning Guide for Information Technology Systems https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final

11/11/2010

1.3.1 Project Planning and Management

All HUD IT projects, including all information systems acquired, developed, enhanced, or maintained must follow the policy, procedures, standards, and guidelines set forth within the https://standards.ieee.org/ieee/12207/11416/ https://standards.ieee.org/ieee/15288/10424/ https://standards.ieee.org/ieee/16326/6769/ https://standards.ieee.org/ieee/23026/10425/ https://standards.ieee.org/ieee/29148/6937/ http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/handbooks/admh/1325.1 http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/handbooks/admh/1325.1 http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/handbooks/hsgh/2226.1 http://portal.hud.gov/hudportal/HUD?src=/program_offices/administration/hudclips/handbooks/hsgh/2226.1 https://www.hud.gov/sites/dfiles/OCHCO/documents/32551CIOH.pdf https://www.hud.gov/stat/cio/ppmv20 https://www.hud.gov/stat/cio/ppmv20 http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ppm/PPMV20HOME http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ppm/PPMV20HOME http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ea/newea http://hudatwork.hud.gov/HUD/cio/po/i/it/sd/devlife/bld/testcenter/tcpolicy_toc https://csrc.nist.gov/pubs/sp/800/34/r1/upd1/final

IT Management Framework using the Project Planning and Management (PPM) Life Cycle located at HUD’s PPM Life Cycle Website:

https://www.hud.gov/program_offices/cio/ppm/PPMV20HOME

PPM was designed based on the best practices from Capability Maturity Model Integration

(CMMI) for systems development and PMBok for project management. At its foundation

PPM is designed as a Waterfall methodology, HUD encourages tailoring the PPM to use the many modern solution development methodologies available to enable the planning, development and delivery of useable functionality within 6–9-month increments.

Offerors are encouraged to propose a preferred methodology whether their solution(s) are for custom development, including prototypes or pilots, Government Off the Shelf

(GOTS) configuration, commercial off the shelf (COTS) products, or Software as a

Services. Working with the HUD Project Manager(s), the Contractor will tailor PPM to take advantage of Contractor proposed expertise in using other methodologies in a manner that will provide HUD the best value and address all of the work necessary for successful project completion, on time, within budget, and delivering intended functionality.

The decisions of PPM tailoring are captured in the Project Tailoring Agreement (PTA), which documents the specific agreement for creating, combining, referring, or omitting specific artifacts applicable to the project, as well as adjusting project control gate reviews to be consistent with the tailoring. All tailoring of PPM must be approved by HUD’s Deputy

Chief Information Officer (DCIO) for Business & IT Modernization. As a default, any project without an approved project tailoring agreement is required to follow all PPM phases and artifacts as presented.

1.4 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the

Government assign tasks to, or prepare work schedules for, individual Contractor employees. It shall be the responsibility of the Contractor to manage its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services.

If the Contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor's responsibility to notify the Contracting

Officer (CO) immediately. These services shall not be used to perform the work of a policy, decision making or management nature, i.e., inherently Government functions. All decisions relative to programs supported by the Contactor shall be the sole responsibility of the Government.

1.5 Period of Performance

The period of performance shall be for one (1) twelve (12) month base period of performance and four (4) twelve (12) month option periods of performance.

https://www.hud.gov/program_offices/cio/ppm/PPMV20HOME https://www.hud.gov/program_offices/cio/ppm/PPMV20HOME

1.6 Place of Performance

The NSPIRE NextGen Services to be performed under this contract shall be performed at the Contractor facilities or remotely.

1.7 Hours of Operation

Key Personnel are responsible for providing services between the hours of 8:00 AM to

4:30 PM Monday through Friday except for Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closing, or similar

Government directed facility closings. Weekly hours must not exceed a forty (40) hour work week and a typical workday will be 8 hours each day Monday through Friday. The

Government reserves the right to change hours of operation or restrict contractor access.

Government agencies will not be available during scheduled holidays, inclement weather, weekends, and after duty hours.

The Contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within the contract when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce is essential.

1.8 Special Qualifications

The Contractor shall have and maintain SOC 2 Type II certifications.

The Contractor shall ensure the following professional certifications are possessed and maintained during the entire contract performance period:

• Project Management Professional Certification (PMP)

• SAFe Scrum Master Certified

The Contractor shall meet these qualification requirements upon contract award.

1.9 Post Award/Kickoff Conference

The Contractor shall attend any post award/kickoff conference convened by the contracting activity or contract administration office in accordance with HUD Acquisition

Regulation (HUDAR) clause 2452.237-79 - Post Award Conference.

1.10 Status Meetings

The Contracting Officer, Contracting Officer’s Representative (COR), and other

Government personnel, as appropriate, will meet periodically with the Contractor to review

Contractor performance, requirement status, etc. At these meetings, the Contracting

Officer will appraise the Contractor of how the Government views the Contractor's performance or progress of the requirement. The Contractor will apprise the Government of problems, if any, being experienced. Appropriate action must be taken to resolve outstanding issues. These meetings must be at no additional cost to the Government. Post

Award Conference and subsequent meetings may be held via teleconference at the

Contracting Officer's discretion.

1.11 Contractor Travel

Prior to travel, the Contractor shall coordinate with and receive Government authorization from the COR for all travel. Reimbursement of travel costs will be in accordance with the

Federal Travel Regulation and in accordance with FAR Overhaul 31.205-46, Travel costs.

1.12 Transition-In

The Contractor shall, upon the Contracting Officer's written notice, furnish transition-in services as required. As a successor, the Contractor shall have sufficient personnel on board during the 30-day transition-in period to ensure a smooth transition with the incumbent contractor. The Contractor shall provide an orderly transition of work acceptance and accomplishment such that any impact to the program is minimized.

During the transition-in period, the Contractor shall become familiar with the requirements to commence full performance of services by the end of the transition-in period.

Transition-in is not required if the successor Contractor is the incumbent contractor.

1.13 Transition-Out

To minimize any decrease in productivity and to prevent possible negative impacts on additional services, the Contractor shall have sufficient personnel on board during the 30-day transition-out period. The Contractor shall ensure a smooth transition with the successor contractor during the transition-out period, prior to completion of contractual performance. The Contractor shall aid the successor in the development of plans, procedures, and methods for the assumption of all on going work. The Contractor shall provide an orderly transition of work acceptance and accomplishment, such that full control by the successor contractor is achieved by the end of the transition-in period.

2 Definitions and Acronyms

2.1 Definitions

Acceptance Testing - Acceptance tests are formal tests that verify if a system satisfies business requirements. They require the entire application to be running while testing and focus on replicating user behaviors. But they can also go further and measure the performance of the system and reject changes if certain goals are not met.

Backlog - The backlog is a list of the Government’s requirements, to include features, user stories, and tasks and is ordered from the highest priority to the lowest priority. A backlog includes both functional and non-functional work, including user stories, features, or epics. If new requirements or defects are discovered, they are added to the backlog. A backlog can occur at varying levels; for example, a product backlog is a high-level backlog that contains all the requirements for the entire program, and an iteration backlog includes a list of user stories intended for that iteration. There are different types of backlogs:

• Portfolio backlog: The Portfolio Backlog is the highest-level backlog and provide the requirements across the portfolio, which will span multiple projects / teams. This backlog includes the high-level goals as epics or features. The project teams then break these work items down into user stories for prioritization and development.

• Program / Release backlog: The backlog with the list of items that are slated to be completed in a release / program increment. These items are derived from the Portfolio Backlog.

Backlog refinement / Backlog grooming - The process for keeping the backlog updated by adding details and revisiting the order and estimates assigned to work.

This allows details to emerge as knowledge increases through feedback and learning cycles.

Business/Workdays – Every official day of the week which are days between and including Monday to Friday. This does not include federal holidays and weekends.

Calendar Day - Any day of the week.

Contractor - A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

Contracting Officer (CO) - A person with authority to enter into, administer, and/or terminate contracts and make related determinations and findings on behalf of the

Government. Note: the only individual who can legally bind the Government.

Contracting Officer’s Representative (COR) – An employee of the U.S. Government appointed by the Contracting Officer to perform contract administration activities regarding technical issues. This individual has authority to provide technical directions to the

Contractor if direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have the authority to change the terms and conditions of the contract.

Cross-functional team - A team that is made up of people who have a mix of skills and ability to define, build, and test ideas into a working product.

Defective Service - A service output that does not meet the standard of performance associated with the Performance Work Statement.

Definition of Done - A predefined set of criteria that must be met before a work item is considered to be complete. This set of criteria serves as a checklist that is used to check each work item for completeness and used as the work item’s artifact.

Definition of Ready – A pre-defined set of criteria that must be met before a user story is considered to be ready for development. This set of criteria serves as a checklist that is used to check each work item for completeness, accuracy, and common understanding between the customer and the development team.

Deliverable - Any artifact that can be physically or electronically delivered which may include working software, as well as non-manufactured things such as meeting minutes or reports.

Development, Modernization, and Enhancements (DME) – Projects and activities that lead to new IT assets/systems or change or modify existing IT assets to substantively improve capability or performance. DME may include, but is not limited to, adding features and new applications required by management needs and/or statutory, regulatory, or

Presidential directives and creating new case tracking modules and business workflows. The

Development hours will also include Requirement gathering and design, Documentation, Testing, Development and Unit Testing.

Development, Security, and Operations (DevSecOps) – The integration of security into every phase of the software development lifecycle.

Development Team – Team that consists of people who create the product. It may be comprised of government and contractor team of developers, including software and security engineers, data specialists, testers, quality assurance, and anyone else with a hands-on role in product development configuration management.

End-to-end testing (aka Regression testing) - End-to-end testing replicates a user behavior with the software in a complete application environment. It verifies that various user flows work as expected and can be as simple as loading a web page or logging in or much more complex scenarios verifying email notifications, online payments, etc.

ExAM4 Enterprise/ExAM4 Inspection- These terms are interchangeable. This is the

Salesforce mobile application the inspectors currently use to provide a configurable inspection framework.

Functional testing - Functional tests focus on the business requirements of an application. Functional testing verifies the output of an action and does not check the intermediate states of the system when performing that action. To avoid confusion between integration testing and functional testing the difference between the two is defined as follows: Integration testing may simply verify that you can query the database while a functional test would expect to get a specific value from the database as defined by the product requirements

Government Furnished Property (GFP) - Government-furnished property is property in the possession of, or directly acquired by, the Government and subsequently furnished to the Contractor for performance of a contract. Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes contractor-acquired property if the contractor-acquired property is a deliverable under a cost contract when accepted by the Government for continued use under the contract.

Integration testing - Integration tests verify that different modules or services used by an application work well together. For example, it can be testing the interaction with the database or making sure that microservices work together as expected

Minimum viable product - The simplest version of a product that can be released. A minimally viable product should have enough value that it is still usable, demonstrates future benefit early on to retain customer buy in, and provides a feedback loop to help guide future development.

Performance Requirements Summary (PRS) - A listing of the performance requirements under the contract that are to be evaluated by the Government on a regular basis, performance indicators for these requirements, performance standards for these requirements and surveillance methods to be used to determine if performance standards are met.

Performance Standard - The Contractor’s performance level required by the Government.

Performance Work Statement (PWS) - A statement of work for performance-based acquisitions that describe the required results in clear, specific, and objective terms with measurable outcomes.

Physical Security - Actions that prevent the loss or damage of Government property.

Project Manager or Technical Point of Contact - An individual who assists the COR in providing technical directions and monitoring performance under the contract. PM and

POC would be defined by the contractor and HUD.

Performance Testing - Performance tests evaluate how a system performs under a particular workload. These tests help to measure the reliability, speed, scalability, and responsiveness of an application. For instance, a performance test can observe response times when executing a high number of requests or determine how a system behaves with a significant amount of data. It can determine if an application meets performance requirements, locate bottlenecks, measure stability during peak traffic, and more.

Quality Assurance (QA) - Policies and procedures adopted by the Government to ensure that supplies and services acquired under Government contracts conform to the contracts’ quality requirements.

Quality Assurance Surveillance Plan (QASP) - A plan describing how the agency will survey, observe, test, sample, evaluate and document the Contractor's performance in meeting critical performance standards identified in the contract.

Quality Control (QC) - All necessary measures taken by the Contractor to assure that the quality of an end product of service meets the contract requirements.

Release / Program Increment — A predefined, time-boxed, and recurring period in which working software is delivered. For custom development, this means creating new software informed by customer feedback rather than extensive upfront planning. For COTS products, this includes configuration, module enablement, and integration work delivered incrementally. Releases / program increments are comprised of multiple sprints / iterations.

Sprint / Iteration – A standard, fixed-length timebox where the agile team delivers incremental value in the form of working, tested software. Iterations are typically 2 weeks in length. Multiple sprints will culminate in a release / program increment.

Subcontractor - Any person, other than the prime Contractor, who offers to furnish or furnishes any supplies, material, equipment, or services of any kind under a prime contract or a subcontract entered into in connection with such prime contract, and any person who offers to furnish or furnishes general supplies to the prime contractor or a higher tier subcontractor. The Government does not have privity of contract with a subcontractor.

Unit testing - Software testing in which individual units of source code, sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures are tested to determine whether they are fit for use. This is the smallest testable increment in software development.

Work Week - Monday through Friday, unless specified otherwise.

2.2 Acronyms

ACC - Annual Contribution Contract

API - Application Programming Interface

AQL - Acceptable Quality Level

ATO - Authority to Operate

CMMI - Capability Maturity Model Integration

CFR - Code of Federal Regulations

CIO or OCIO - Office of the Chief Information Officer of HUD

CFO or OCFO – Office of the Chief Financial Officer of HUD

CLIN – Contract Line-Item Number

CO - Contracting Officer

COR – Contracting Officer’s Representative

COTS – Commercial Off the Shelf

CSAM - Cyber Security Asset Management [System]

DCIO - Deputy Chief Information Officer

DevSecOps – Development, Security, and Operations

EAP - Enterprise Analytics Platform

EIV - Enterprise Income Verification

EST - Eastern Standard Time (U.S.)

ETL – Extraction, Transformation, and Loading of data

FAQ - Frequently Asked Questions

FAR - Federal Acquisition Regulation

FHA – Federal Housing Administration

GFP - Government Furnished Property

GOTS - Government Off-the-Shelf

GSA - U.S. General Services Administration

HHS – U.S. Department of Health and Human Services

HUD - U.S. Department of Housing and Urban Development

HUDAR - HUD Acquisition Regulation

ICAM - Identity, Credential, and Access Management

IG or OIG - Office of Inspector General

IMS/PIC - Inventory Management System / PIH Information Center iREMS - integrated Real Estate Management System

IT - Information Technology

IT PM - Information Technology Project Manager

MFH – FHA Office of Multifamily Housing

MOU – Memorandum of Understanding

NIST - National Institute of Standards and Technology

NSPIRE - National Standards for the Physical Inspection of Real Estate

O&M - Operations and Maintenance

OCIO - Office of the Chief Information Officer

PHA – Public Housing Agency

PHAS - Public Housing Assessment System

PIH - Office of Public and Indian Housing

PM - Project Manager

POA&M - Plan of Action & Milestones

POC - Point of Contact

PPM - Project Planning and Management

PTA - Project Tailoring Agreement

Q&As - Questions and Answers QA - Quality AssuranceQASP - Quality Assurance Surveillance Plan

QCP - Quality Control Plan

REAC - Real Estate Assessment Centers

SEMAP - Section Eight Management Assessment Program

SaaS – Software as a Service

TAC - Technical Assistance Center

TPOC - Technical Point of Contact

TRC - Technical Review Committee

VPN - Virtual Private Network

3 Government-Furnished Property and Services

The Contractor shall ensure accurate control and accountability of all Government-

Furnished Property in accordance with the terms and conditions of this contract. The

Government will furnish, at no cost to the Contractor, the GFP shown below.

3.1 Government Services

No government services will be provided

3.2 Facilities

No facilities will be provided by the Government.

3.3 Equipment

The Government will provide the Contractor with PIV cards for accessing HUD's software development, test, production environment via Virtual Private Network (VPN), and Government Issued laptops as required to perform the work identified in this PWS.

3.4 Materials and Information

The Government will provide IT Security process and templates, Technical Review

Committee (TRC) process and templates, existing information regarding the legacy

NSPIRE system, materials regarding legacy HUD NSPIRE data models, and additional

Standard Operating Procedures and Policies as agreed upon with the COR. Copies of the required materials may be provided to the Contractor in hard copy or soft copy. All materials will remain the property of the Government and will be returned to the COR upon request or at the end of the contract period.

3.5 Quality Assurance (QA)

The Government shall evaluate the Contractor's performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable quality level.

4 Contractor-Furnished Items and Services

The Contractor shall furnish, all facilities, equipment, and supplies required to perform the work under this contract that are not listed under Government-Furnished Property and

Services.

4.1 Facilities

The Contractor shall furnish their own facilities.

4.2 Equipment

The Contractor shall furnish all equipment required to perform the services identified within the PWS.

4.3 Materials

The Contractor shall furnish all materials required to perform the services identified within the PWS.

4.4 Contractor Responsibilities

The Contractor shall only conduct business with designated Government personnel listed as points of contact (POCs). Names of authorized personnel will be provided to the Contractor by the Contracting Officer, in writing, and updated as necessary throughout the contract’s period of performance.

U.S. Government records, copies of original results and reports, verified original data, corrected data, and corrected supporting final reports which are maintained by the

Contractor remain the property of the U.S. Government. These files/results must be surrendered to the COR upon request and at the end…