AMSS PWS - DRAFT (050124).pdf

Performance Work Statement (PWS)

HUD Office of Chief Information Officer

Acquisition Modernizations Support

Services (AMSS)

Table of Contents

1.0 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.0 Definitions and Acronyms

2.1 Definitions

2.2 Acronyms [Revise with acronyms only germane to your requirement]

3.0 Government-Furnished Information

3.1 Government Services

3.3 Equipment

3.4 Materials

3.5 Quality Assurance (QA)

4.0 Contractor-Furnished Items and Services

4.1 Facilities

4.2 Equipment

4.3 Material

4.4 Contractor Responsibilities

4.5 Contractor Personnel

4.6 Identification of Contractor Employees

4.7 Quality Control

4.7.1 Quality Control Plan

5.0 Specific Tasks

5.1 Operation Support – Requirements Development Module

5.2 Requirements Development Module Setup

5.2.1 The Contractor shall correct application software errors

5.3 Source Selection Module Setup

5.3.1 The Contractor shall provide Application Quality management

5.3.2 The Contractor shall correct application software errors

5.4 Contract Management Module Setup

5.4.1 The Contractor shall provide Application Quality management

5.4.2 The Contractor shall correct application software errors

5.5 Training & User Resources

Following HUD approval of the module setup, the contractor will develop a training plan in collaboration with the COR to include date(s), frequency, content overview and type (virtual, on-demand, ILT). Upon approval of the training plan, the contractor will conduct training for

HUD acquisition workforce in the most efficient manner possible to include virtual ILT, recordings and Quick Reference Guides

6.0 Deliverables and Milestones

6.1 Quality Control Plan

6.2 Acceptance Criteria

7.0 Performance Requirements Summary

8.0 Related Documents

1.0 General Information

The HUD Office of the Chief Procurement Officer (OCPO) has a requirement for three commercial-off-the-shelf (COTS) modules to be used by members of the acquisition workforce to draft requirements based on a selection of multiple structured, templated formats determined by type of requirement, a module to facilitate source selection and a module to facilitate contract management.

1.1 Scope of Work

The contractor shall set up three separate COTS modules. The first module will serve as a requirements development module which will enable HUD users to choose from four (4) different type of requirements documents to include 1) Performance Work Statement; 2) Statement of Objectives; 3) Statement of Work; and 4) Product Descriptions/Specifications. The four (4) templates within the module will include standard language to be provided by HUD based on Department mandatory templates and policies. The module will guide users to input information specific to each section of the templates for their requirements. The module will guide users to ensure certain acquisition considerations are made and direct the users to populate each template section with the appropriate narrative or N/A designation.

In addition, the contractor shall set up a COTS source selection module to facilitate technical evaluations based on HUD usage and access requirements.

Lastly, the contractor will set up the contract management module to facilitate post-award contract management activities based on HUD usage and access requirements.

For alignment, consistency and accuracy, all modules must link information in relative sections for automated input when possible.

This requirement includes the contractor’s discussion with OCPO staff to fully understand setup requirements, full setup, quality assurance and testing of the setup in the tool by contractor staff prior to training and testing by OCPO staff. Lastly, training and Quick Reference Guides will be developed and provided to all HUD acquisition workforce members who will be using the tool following implementation to include program/project managers (P/PM), contracting officer representatives (COR), subject matter experts (SME), acquisition liaison specialists and buyers (CO). The number of users at the time of award will determine the number of licenses that will be purchased for post-implementation use of the tool.

1.2 Background

Current System Environment

Most of the automation that supports the HUD acquisition workforce is now achieved through the Purchase Request Information System Management (PRISM), which is delivered by a shared services provider - Treasury’s Administrative Resource Center (ARC). This PRISM solution has limited functionality available to users. Although HUD is in the process of working with ARC to enhance data visibility, collaboration space and dashboard capability, the resulting solution cannot be further modernized to fill the gaps in its capabilities.

The following gaps exist in HUD’s current system for which the agency is seeking solutions:

In the past, HUD Acquisition Workforce (AWF) users were able to develop requirements us the Acquisition Requirements Roadmap Tool (ARRT).

However, this tool is no longer being maintained and currently not compatible with current versions of Windows and MS Word.

Currently, AWF users make use of a secured SharePoint page to manage source selection activities. This process is not efficient or sustainable to support future procurement in HUD.

Lastly, HUD does not currently have an effective, efficient means of managing contract management to include tracking deliverables, performance, quality and expenditures as a part of post-award activities. This must be remedied in order to provide the level of visibility needed to reduce risk and document contract compliance and oversight.

1.3 Constraints

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

Constraints include the following:

The modules resulting from this award will NOT interface with PRISM.

Set up of the modules must be in accordance with the FAR, HUDAR and HUD procurement policies, procedures and mandatory requirements.

Set up of the modules shall be accomplished within 180 calendar days of award to include setup, testing, training, communication and final implementation.

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

Document Number Title & URL Released Mandatory/

Advisory

Executive Order (E.O.) 14028 and OMB Circular M-22-

Improving Nation’s Cybersecurity Executive Order on Improving the Nation's Cybersecurity | The White House Moving the U.S. Government Toward Zero Trust Cybersecurity Principles M-22-09 Federal Zero Trust Strategy (whitehouse.gov)

2021, M

44 USC §3541 et seq., OMB Circular M-19-2

Federal Information Security Management Act of 2014 (FISMA, supersedes the Computer Security Act of 1987) USCODE-2016-title44-chap35.pdf (govinfo.gov) M-19-02.pdf (whitehouse.gov)

2002 M

Pub. L. No. 113- 291, OMB Circular M-15-14

Federal Information Technology Acquisition Reform Act (FITARA), of December 2014 Management and Oversight of Federal Information Technology (archives.gov)

2014 M

44 USC §3601 et seq.

E-Government Act of 2002 (Pub. L. No. 107-347) https://www.govinfo.gov/content/pkg/USCODE-2019-title44/pdf/USCODE-2019-title44-chap36-sec3601.pdf

2002 M

31 USC §1101

Good Accounting Obligations in Government Act (AGO-IC Act), 2019 (formally known as Government Performance and Results Act or GPRA), Pub. L. No. 115-414.

https://www.govinfo.gov/content/pkg/USCODE-2019-title31/pdf/USCODE-2019-title31-subtitleII-chap11-sec1101.pdf

2019 M

Pub. L. No. 104-106, 40 USC §1401 et seq.

Information Technology Management Reform Act of 1996 (Clinger-Cohen Act) https://dodcio.defense.gov/Portals/0/Documents/ciodesrefvo lone.pdf

1996 M

Pub. L. No. 105-

220, 29 USC 701

et seq.

Section 508 of the Rehabilitation Act of 1998 https://www.section508.gov/manage/laws-and-policies/#508-policy

1998 M

Pub. L. No. 113- 101, 31 USC §3716(c)(6)

Digital and Transparency Act of 2014 (DATA Act) https://www.govinfo.gov/content/pkg/PLAW- 113publ101/pdf/PLAW-113publ101.pdf

2014 M

5 CFR Part 1315 Prompt Payment; Final Rule https://www.fiscal.treasury.gov/files/prompt-payment/5cfr1315.pdf

M

OMB Circular A-16 Coordination of Geographic Information and Related Spatial Data Activities https://www.whitehouse.gov/omb/circulars

2002 M

OMB Circular A-123, Appendix D

Compliance with the Federal Financial Management Improvement Act https://www.whitehouse.gov/omb/circulars

Latest version

M

OMB Circular A-130 Managing Information as a Strategic Resource https://www.whitehouse.gov/omb/circulars

Latest version

M https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/ https://www.whitehouse.gov/briefing-room/presidential-actions/2021/05/12/executive-order-on-improving-the-nations-cybersecurity/ https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf https://www.whitehouse.gov/wp-content/uploads/2022/01/M-22-09.pdf https://www.whitehouse.gov/wp-content/uploads/2018/10/M-19-02.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2015/m-15-14.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2015/m-15-14.pdf https://www.govinfo.gov/content/pkg/USCODE-2019-title44/pdf/USCODE-2019-title44-chap36-sec3601.pdf https://www.govinfo.gov/content/pkg/USCODE-2019-title44/pdf/USCODE-2019-title44-chap36-sec3601.pdf https://www.govinfo.gov/content/pkg/USCODE-2019-title31/pdf/USCODE-2019-title31-subtitleII-chap11-sec1101.pdf https://www.govinfo.gov/content/pkg/USCODE-2019-title31/pdf/USCODE-2019-title31-subtitleII-chap11-sec1101.pdf https://www.govinfo.gov/content/pkg/USCODE-2019-title31/pdf/USCODE-2019-title31-subtitleII-chap11-sec1101.pdf https://dodcio.defense.gov/Portals/0/Documents/ciodesrefvolone.pdf https://dodcio.defense.gov/Portals/0/Documents/ciodesrefvolone.pdf https://www.govinfo.gov/content/pkg/PLAW-113publ101/pdf/PLAW-113publ101.pdf https://www.govinfo.gov/content/pkg/PLAW-113publ101/pdf/PLAW-113publ101.pdf https://www.fiscal.treasury.gov/files/prompt-payment/5cfr1315.pdf https://www.fiscal.treasury.gov/files/prompt-payment/5cfr1315.pdf https://www.whitehouse.gov/omb/circulars https://www.whitehouse.gov/omb/circulars https://www.whitehouse.gov/omb/circulars

Advisory

OMB Memorandum 96-20

Implementation of the Information Technology Management Reform Act of 1996 https://www.whitehouse.gov/wp-content/uploads/2017/11/1996-M-96-20-Implementation-of-the-Information-Technology-Management-Reform-Act-of- 1996.pdf

Latest version

M

OMB Memorandum 99-20

Security of Federal Automated Information Resources https://obamawhitehouse.archives.gov/omb/memoranda_m 99-20/

1999 M

OMB Memorandum 06-15

Safeguarding Personally identifiable Information https://obamawhitehouse.archives.gov/sites/default/files/om b/assets/omb/memoranda/fy2006/m-06-15.pdf

2006 M

OMB Memorandum 06-16

Protection of Sensitive Agency Information https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2006/ m06-16.pdf

2006 M

OMB Memorandum 06-19

Reporting Incidents Involving PII https://georgewbush-whitehouse.archives.gov/omb/memoranda/fy2006/m06- 19.pdf

2006 M

OMB Memorandum 06-20

Reporting Instructions for the Federal Information Security Act and Agency Privacy Management https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2006/ m06-20.pdf

2006 M

OMB Memorandum 12-11

Reducing Improper Payments through the "Do Not Pay List" https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2012/ m-12-11_1.pdf

2012 M

PDD-63

Critical Infrastructure Protection, Presidential Decision Directive-63 https://irp.fas.org/offdocs/pdd/pdd-63.htm

1998 M

HSPD-12

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

2004 M

NIST Special Publication 800-12, Series

An Introduction to Computer Security: The NIST Handbook https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

M

NIST Special Publication 800-14, Series

Generally Accepted Principles and Practices for Securing Information Technology Systems https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

M

NIST Special Publication 800-18, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A https://www.whitehouse.gov/wp-content/uploads/2017/11/1996-M-96-20-Implementation-of-the-Information-Technology-Management-Reform-Act-of-1996.pdf https://www.whitehouse.gov/wp-content/uploads/2017/11/1996-M-96-20-Implementation-of-the-Information-Technology-Management-Reform-Act-of-1996.pdf https://www.whitehouse.gov/wp-content/uploads/2017/11/1996-M-96-20-Implementation-of-the-Information-Technology-Management-Reform-Act-of-1996.pdf https://www.whitehouse.gov/wp-content/uploads/2017/11/1996-M-96-20-Implementation-of-the-Information-Technology-Management-Reform-Act-of-1996.pdf https://obamawhitehouse.archives.gov/omb/memoranda_m99-20/ https://obamawhitehouse.archives.gov/omb/memoranda_m99-20/ https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2006/m-06-15.pdf https://obamawhitehouse.archives.gov/sites/default/files/omb/assets/omb/memoranda/fy2006/m-06-15.pdf https://irp.fas.org/offdocs/pdd/pdd-63.htm http://www.dhs.gov/homeland-security-presidential-directive-12 http://www.dhs.gov/homeland-security-presidential-directive-12 https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html

Advisory

NIST Special Publication 800-30, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

M

NIST Special Publication 800-34, Series

Contingency Planning Guide for Information Technology Systems https://csrc.nist.gov/publications/PubsSPs.html SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

M

NIST Special Publication 800-35, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

M

NIST Special Publication 800-37, Series

Guide for the Security Certification and Accreditation of Federal Information Systems https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

M

NIST Special Publication 800-47 Series

Security Guide for Interconnecting Information Technology Systems https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800-53, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800- 53A, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800-55, Series

Performance Measurement Guide for Information Security https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800-60, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800-64, Series

Security Considerations in the Information System Development Life Cycle https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html

Advisory

NIST Draft Special Publication 800-82, Series

Guide to Industrial Control Systems (ICS) Security https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800-84, Series

Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800- 100, Series

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

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

NIST Special Publication 800- 119, Series

Guidelines for the Secure Deployment of IPv6 https://csrc.nist.gov/publications/PubsSPs.html

SP 800 Series is available at:

https://csrc.nist.gov/publications/sp800

Latest Version

A

HUD Handbook 1325.1

Privacy Act Handbook https://www.hud.gov/program_offices/administration/hudclip s/handbooks/admh

Latest Version

M

HUD Handbook 2400.25

Information Technology Security Policy https://www.hud.gov/program_offices/administrati on/hudclips/handbooks/cio

Latest Version

M

HUD Handbook 3255.1

Enterprise Architecture Policy https://www.hud.gov/program_offices/administrati on/hudclips/handbooks/cio

Latest Version

M

HUD Handbook 3410.1

HUD Policy for IT Project Planning and Management (PPM 2.0) https://www.hud.gov/program_offices/administrati on/hudclips/handbooks/cio

Latest Version

M

HUD PPM 2.0 HUD Project Planning and Management (PPM) Site:

Project Type Guides, Tools and Artifact Templates Project Planning and Management V2.0 Home Page | HUD.gov / U.S. Department of Housing and Urban Development (HUD)

Latest Versions

M

HUD Handbook 3430.1

HUD Policy for Agile Methodology https://www.hud.gov/program_offices/administration/hudcli ps/handbooks/cio

Latest Version

M

NDIA IPMD EIA-748 National Defense Industrial Association (NDIA) American National Standards Institute Electronic Industries Alliance (ANSI/EIA) - 748 standards for Earned Value Management Systems (EVMS) NDIA IPMD EIA-748 EVMS Intent GuideNDIA IPMD EIA- 748 EVMS Intent Guide

2018 A https://csrc.nist.gov/publications/PubsSPs.html https://csrc.nist.gov/publications/PubsSPs.html https://www.hud.gov/program_offices/administration/hudclips/handbooks/admh https://www.hud.gov/program_offices/administration/hudclips/handbooks/admh https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/cio/ppm/PPMV20HOME https://www.hud.gov/program_offices/cio/ppm/PPMV20HOME https://www.hud.gov/program_offices/cio/ppm/PPMV20HOME https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.hud.gov/program_offices/administration/hudclips/handbooks/cio https://www.ndia.org/-/media/sites/ndia/divisions/ipmd/division-guides-and-resources/ndia_ipmd_intent_guide_ver_d_aug282018.ashx https://www.ndia.org/-/media/sites/ndia/divisions/ipmd/division-guides-and-resources/ndia_ipmd_intent_guide_ver_d_aug282018.ashx https://www.ndia.org/-/media/sites/ndia/divisions/ipmd/division-guides-and-resources/ndia_ipmd_intent_guide_ver_d_aug282018.ashx

1.3.1 Project Planning and Management

All HUD IT projects, including all information systems acquired, developed, enhanced, or maintained shall follow the policy, procedures, standards, and guidelines set forth within the IT Management Framework using the Project Planning and Management (PPM) Life Cycle located at HUD’s PPM Life Cycle Website:

http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ppm/PPMV20HOME

PPM was designed based on the best practices from Capability Maturity Model Integration (CMMI) for systems development and Project Management Body of Knowledge (PMBok) for project management. While at the 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 six (6) months.

Contractors are encouraged to propose a preferred methodology whether their solution(s) are Commercial Off the Shelf (COTS)/ Government Off the Shelf (GOTS) configuration, or Software as a Service (SaaS). 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 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 adjust 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 work of a policy, http://portal.hud.gov/hudportal/HUD?src=/program_offices/cio/ppm/PPMV20HOME 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 base period of twelve (12) months and four

(4) twelve (12)month option periods. (See Clause 52.212-8.)

1.6 Place of Performance

The services associated with setup, quality assurance, testing and training to be performed under this contract shall be performed at the Contractor’s facilities. OCPO representatives are in the Eastern time zone and will coordinate virtually with contractor staff throughout the period of the project. Training of HUD testers and users will be provided virtually. See Section 1.7 Hours of Operation.

1.7 Hours of Operation

The Contractor shall ensure that personnel are available to interface with acquisition workforce users located in HUD offices covering six time zones from the East Coast to Hawaii. This may require a limited number of contractor personnel to work outside of the Contractor’s core hours in the time zone of the Contractor’s location.

1.8 Special Qualifications

In executing the required tasks, the Contractor shall adopt the industry-standard project management principles outlined by the Project Management Institute’ PMBOK (Project

Management Body of Knowledge). The Contractor must be able to create data visualization reports, data collection forms, and other deliverables using the HUD-approved technologies during the period of performance of this contract.

1.9 Post Award/Kickoff Conference

The Contractor shall attend any post award conference convened by the contracting activity or contract administration office in accordance with FAR Subpart 42.5 and HUD

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

Government intends to convene a Post Award Conference with the Contractor within ten (10) business days after contract award. The Contracting Officer will notify the

Contractor of the specific date, location, and agenda within five days after contract award.

1.10 Status Meetings

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

Government personnel, as appropriate, may meet periodically with the Contractor to also review Contractor performance, requirement status, etc. At these meetings, the

Contracting Officer will apprise the Contractor of how the Government views the

Contractor's performance or progress of the requirement. The Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the Government. Post award conference and subsequent meetings may be held via teleconference.

1.11 Contractor Travel

No contractor travel is anticipated for performance of this requirement.

Communications between the Government and the contractor will be virtual using MS

Teams, email, or phone.

1.12 Transition In

N/A as these services to be procured have not been procured previously. The requirements are new to the program and there is no incumbent.

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 incumbent Contractor shall ensure a smooth transition with the successor Contractor during the Transition-Out period, prior to completion of contractual performance. The incumbent 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 new contract Transition-In period. The transition out period is optional.

2.0 Definitions and Acronyms

2.1 Definitions

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.

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

Deliverable - Anything that can be physically delivered but may include non-manufactured things such as meeting minutes or reports.

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.

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

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 shall meet contract requirements.

Statement of Objectives (SOO) - A Government-prepared document incorporated into the solicitation that states the overall performance objectives. It is used in solicitations when the Government intends to provide the maximum flexibility to each offeror to propose an innovative approach.

Statement of Work (SOW) – A statement of work shall include a description of work to be performed; location of work; period of performance; deliverable schedule; applicable performance standards; and any special requirements (e.g., security clearances, travel, special knowledge) in full detail.

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 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.

Workday - The number of hours per day the Contractor provides services in accordance with the contract.

Work Week - Monday through Friday, unless specified otherwise.

2.2 Acronyms [Revise with acronyms only germane to your requirement]

AQL - Acceptable Quality Level

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

CFR - Code of Federal Regulations

CO - Contracting Officer

COR - Contracting Officers Representative

EST - Eastern Standard Time (U.S.)

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

HUDAR - HUD Acquisition Regulation

IT – Information Technology

PM - Project Manager

POC - Point of Contact

POP - Period of Performance

QA - Quality Assurance

QASP - Quality Assurance Surveillance Plan

QCP - Quality Control Plan

U.S.C - United States Code

3.0 Government-Furnished Information

The Government will provide the contractor with all required HUD templates for an

SOW, PWS and SOO. Also, the Government will provide the contractor with copies of all relevant regulations, policies, procedures, templates and any additional information needed to inform the contractor’s setup of the tool for use by the HUD acquisition workforce.

3.1 Government Services

N/A

3.2 Facilities

Government facilities will not be provided during the contract period of performance.

3.3 Equipment

Government equipment will not be provided.

3.4 Materials

Copies of the required information referenced above in Section 3.0 will be provided to the Contractor in soft copy within 5 business days of contract award. 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.0 Contractor-Furnished Items and Services

The Contractor shall furnish all equipment and supplies required to perform the work under this contract.

4.1 Facilities

The Contractor shall furnish all facilities required to perform the duties of this contract.

4.2 Equipment

The Contractor shall furnish all equipment required to perform the duties of this contract.

4.3 Contractor Responsibilities

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

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.

4.5 Contractor Personnel

The Contractor shall provide a Contract Manager/Project Manager who shall be responsible for the performance of work. An alternate shall also be designated to act in the absence of the Contract Manager. These Contractor personnel (main point of contact and alternate point of contact) are considered Key Personnel by the

Government and shall be listed as such in accordance with HUDAR 2452.237-70, "Key

Personnel.

The Contract Manager/Project Manager or alternate shall have full authority to act on all contact matters relating to daily operations of this contract. Accordingly, at a minimum, the points of contact shall have the technical knowledge of the requirement and be in the position to actually receive assignment, guidance and direction from the COR and

CO per HUDAR 2452.237-73, Conduct of Work and Technical Guidance and shall be allocated enough hours to the requirement to ensure successful performance.

These points of contact shall each be an employee of the Contractor. An employee of a subcontractor is not acceptable for either of these positions. The Contract

Manager/Project Manager or alternate shall be available between the hours of 8:00am to 4:00pm, Monday through Friday EST, except Federal Holidays or when the

Government facility is closed for administrative reasons.

4.6 Identification of Contractor Employees

All Contractor/subcontractor personnel email addresses should include an identifier to distinguish themselves from Government employees. When conversing with

Government personnel during business meeting, over the telephone or via electronic mail, Contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between

Government employees.

Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, Contractor/subcontractors occupying collocated space with their Government program customer shall identify their workspace area with their name and company affiliation, or as a minimum, "CNTR” (for Contractor) after name.

4.7 Quality Control

The Contractor shall establish and maintain a complete Quality Control Program that shall ensure services are performed in accordance with this contract. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-reoccurrence of defective services. The Contractor's quality control program is the means which ensures that work complies with the requirements of the contract. The

Contractor shall provide the associated Quality Control Plan to the Government as directed.

4.7.1 Quality Control Plan

The Contractor shall develop, maintain, enforce, and document a Quality Control Plan

(QCP).

The QCP shall ensure the Government receives the level of quality that is consistent with the requirements specified in this contract. The QCP shall be sufficiently detailed to provide the Contractor's methodology for identifying and recruiting qualified personnel. The QCP shall also provide the Contractor's methodology for resolving problems identified by the Government during reviews conducted in accordance with its

Quality Assurance Surveillance Plan (QASP).

The QCP shall also provide the Contractor's methodology for establishing an internal feedback system for support personnel, and for resolving problems identified by that feedback system.

The QCP shall demonstrate and validate that the services or deliverables to be provided under the contract are completed with a level of quality that meets the minimum performance threshold established in the Government's QASP. The QCP shall address

Quality Management Approach, Quality Assurance, Quality Control and Quality

Standards.

5.0 Specific Tasks

5.1 Operation Support

The Contractor shall provide operational support for setup, testing, training and implementation of the three (3) stand-alone, commercial-off-the-shelf requirements development module.

Deliverables

A001 Project Work Plan

A002 Bi-weekly Project Status Report

A003 - Requirements Development Module Post Setup Demo A004 – Requirements Development Module – Initial Testing/Quality Assurance Results A005 – Requirements Development Module – Final Quality Assurance Results

A006 – Source Selection Module Post Setup Demo A007 – Source Selection Module – Initial Testing/Quality Assurance Results A008 – Source Selection Module – Final Quality Assurance Result

A009 - Requirements Development Module Post Setup Demo A010 – Requirements Development Module – Initial Testing/Quality Assurance Results A011 – Requirements Development Module – Final Quality Assurance Result

Training Plan A012 – Requirements Development Module A013 – Source Selection Module A014 – Contract Management Module

Training A015 – Requirements Development Module A016 – Source Selection Module A017– Contract Management Module

Resources – Videos and Quick Reference Guide(s) A018 – Requirements Development Module A019 – Source Selection Module A020 – Contract Management Module

A021 Draft Status Meeting Minutes

A022 Final Status Meeting Minutes

A023 Quality Control Plan

5.1.1 Project Management

The Contractor shall perform project management tasks for project planning, status reporting, production monitoring and task management, and deliverable tracking in support of the operational requirements given by the OCIO senior leadership and program offices.

Project Work Plan

The Contractor shall create and maintain a Project Work Plan outlining the approach to accomplish the tasks of this PWS. The Project Work Plan shall include a detailed description of all tasks, itemized deliverables, schedule, resource estimates, and identification of any risks and risk mitigation strategies for the completion of all tasks.

Initial Project Work Plans shall be submitted to the COR within ten (10) business days after contract award. The Contractor shall update the narrative and schedules as tasks are assigned by the COR, with updates occurring no less frequently than monthly at a minimum with submission to the COR within two (2) business days after the end of the reporting month (or as otherwise indicated by the COR and/or ITPM).

Bi-weekly Project Status Report

The Contractor shall submit to the COR a bi-weekly Project Status Report for the requirements development tool project providing the activities performed and actual progress of each task supported under the PWS. The bi-weekly Project Status Report shall be current as of 4:00pm (EST) on the last business day of every other week

(normally Friday). The report shall:

Provide a brief, factual summary description of technical progress made for each PWS task during the reporting period.

Manage program risks and issues - Identify significant problems and their impacts, causes, proposed corrective actions, and the effect that such corrective actions will have on the accomplishments of the contract objectives.

Provide schedule status and/or degree of completion of tasks/activities by time intervals.

Performance Standards

a) STD: Project Work Plan are submitted within ten (10) business days after contract award and monthly thereafter.

AQL: 2 business day deviation from standard.

b) STD: 100% of notification emails are submitted within one (1) day of problem detection.

AQL: 5% deviation from standard.

Deliverables A001 Project Work Plans A002 Bi-weekly Project Status Report A021 Draft Status Meeting Minutes A022 Final Status Meeting Minutes

5.2 Requirements Development Module Setup

The module will be accessed by HUD users throughout the agency for developing a

PWS, SOO and SOW when needed in a predetermined format according to HUD-approved templates, policies and guidelines. The contractor will facilitate discussions with HUD representatives to get specific information to inform the setup. Follow-up discussions may be necessary.

Following discussions with HUD, the contractor will set up the requirements development module based on HUD usage and access requirements. Setup will be followed with a demo of the module to HUD representatives to ensure that all requirements are met.

The Contractor shall fix all application problems caused by design, logic, or coding errors associated with the foundational COTS solution and specific setup required to implement the application into production.

Performance Standards

a) STD: 100% of application software and setup meets the Government’s requirements for timeliness, regulations, policy and operates properly.

AQL: 5% deviation from standard.

Deliverables A003 Post Setup Demo

5.2.1 The Contractor shall correct application software errors.

The Contractor shall perform the analysis, design, software modifications, testing and documentation activities required in implementing software corrections to application errors caused by design, logic, or coding errors.

At the request of the COR, the Contractor shall perform analysis and develop an

Analysis Report to identify impacts to system and interfaces due to software errors.

Quality Assurance/Testing – The contractor will ensure that all security, access and functionality is addressed by the proposed setup.

Performance Standards

a) STD: 95% of application software corrections require no further software releases.

AQL: 5% deviation from standard.

Deliverables A004 Initial Testing/Quality Assurance Results

5.2.2 The Contractor shall correct application software errors.

The Contractor shall perform the analysis, design, software modifications, testing and documentation activities required in implementing software corrections to application errors caused by design, logic, or coding errors.

At the request of the COR, the Contractor shall perform analysis and develop an

Analysis Report to identify impacts to system and interfaces due to software errors.

Quality Assurance/Testing – The contractor will ensure that all security, access and functionality is addressed by the proposed setup.

Performance Standards

a) STD: 95% of application software corrections require no further software releases.

AQL: 5% deviation from standard.

Deliverables A005 Final Testing/Quality Assurance Results

5.3 Source Selection Module Setup

The contractor will facilitate discussions with HUD representatives to get specific information to inform the setup. Follow-up discussions may be necessary.

Following discussions with HUD, the contractor will set up the source selection module to facilitate technical evaluations based on HUD usage and access requirements.

Setup will be followed with a demo of the module to HUD representatives to ensure that all requirements are met.

The Contractor shall fix all application problems caused by design, logic, or coding errors associated with the foundational COTS solution and specific setup required to implement the application into production.

Performance Standards

a) STD: 100% of application software and setup meets the Government’s requirements for timeliness, regulations, policy and operates properly.

AQL: 5% deviation from standard.

Deliverables A006 Post Setup Demo

5.3.1 The Contractor shall provide Application Quality management.

At the direction of the COR, the Contractor shall analyze application problems and recommend potential solutions via an Application Quality Analysis Report within two (2) business days of COR request.

The Contractor shall also attend Data Resolution Discussion Meetings and deliver draft meeting minutes to the COR within two (2) business days after each meeting. The meeting minutes shall include issues discussed, decisions, assignments, and pending matters. Upon receipt of Government comments, the Contractor shall incorporate the comments into final meeting minutes which shall be submitted within three (3) business days.

Upon approval of the COR, the Contractor shall develop and test reconciliation routines to perform data clean up and prepare a Data Services Request for COR approval to execute the reconciliation job. After completion of each reconciliation job, the

Contractor shall prepare and submit to the COR a Data Resolution Report that demonstrates the data quality issue has been resolved.

Performance Standards

a) STD: Testing and Quality Assurance is completed and completed within five (5) business days of application setup.

AQL: Testing and Quality Assurance Report is completed and submitted within five (5) business days of completion.

A007 Initial Testing/Quality Assurance Results

5.3.2 The Contractor shall correct application software errors.

The Contractor shall perform the analysis, design, software modifications, testing and documentation activities required in implementing software corrections to application errors caused by design, logic, or coding errors.

At the request of the COR, the Contractor shall perform analysis and develop an

Analysis Report to identify impacts to system and interfaces due to software errors.

Quality Assurance/Testing – The contractor will ensure that all security, access and functionality is addressed by the proposed setup.

Performance Standards

a) STD: 95% of application software corrections require no further software releases.

AQL: 5% deviation from standard.

Deliverables

A008 Final Testing/Quality Assurance Results

5.4 Contract Management Module Setup

The contractor will facilitate discussions with HUD representatives to get specific information to inform the setup. Follow-up discussions may be necessary.

Following discussions with HUD, the contractor will set up the contract management module to facilitate post-award contract management activities based on HUD usage and access requirements. Setup will be followed with a demo of the module to HUD representatives to ensure that all requirements are met.

The Contractor shall fix all application problems caused by design, logic, or coding errors associated with the foundational COTS solution and specific setup required to implement the application into production.

Performance Standards

a) STD: Testing and Quality Assurance is completed and completed within five (5) business days of application setup.

AQL: Testing and Quality Assurance Report is completed and submitted within five (5) business days of completion.

A009 Post Setup Demo

5.4.1 The Contractor shall provide Application Quality management.

At the direction of the COR, the Contractor shall analyze application problems and recommend potential solutions via an Application Quality Analysis Report within two (2) business days of COR request.

The Contractor shall also attend Data Resolution Discussion Meetings and deliver draft meeting minutes to the COR within two (2) business days after each meeting. The meeting minutes shall include issues discussed, decisions, assignments, and pending matters. Upon receipt of Government comments, the Contractor shall incorporate the comments into final meeting minutes which shall be submitted within three (3) business days.

Upon approval of the COR, the Contractor shall develop and test reconciliation routines to perform data clean up and prepare a Data Services Request for COR approval to execute the reconciliation job. After completion of each reconciliation job, the

Contractor shall prepare and submit to the COR a Data Resolution Report that demonstrates the data quality issue has been resolved.

Performance Standards

a) STD: Testing and Quality Assurance is completed and completed within five (5) business days of application setup.

AQL: Testing and Quality Assurance Report is completed and submitted within five (5) business days of completion.

A010 Initial Testing/Quality Assurance Results

5.4.2 The Contractor shall correct application software errors.

The Contractor shall perform the analysis, design, software modifications, testing and documentation activities required in implementing software corrections to application errors caused by design, logic, or coding errors.

At the request of the COR, the Contractor shall perform analysis and develop an

Analysis Report to identify impacts to system and interfaces due to software errors.

Quality Assurance/Testing – The contractor will ensure that all security, access and functionality is addressed by the proposed setup.

Performance Standards

a) STD: 95% of application software corrections require no further software releases.

AQL: 5% deviation from standard.

Deliverables A011 Final Testing/Quality Assurance Results

5.5 Training & User Resources

5.5.1 Training/Resources

Following HUD approval of the module setup, the contractor will develop a training plan in collaboration with the COR to include date(s), frequency, content overview and type

(virtual, on-demand, ILT). Upon approval of the training plan, the contractor will conduct training for HUD acquisition workforce in the most efficient manner possible to include virtual ILT, recordings and Quick Reference Guides.

P…