DRAFT PWS - ICS Technical Support.pdf

DRAFT

Payroll and HR IT Technical Support

Performance Work Statement

May 11, 2026

1. BACKGROUND 5

1.1 Business Line 5

2. OBJECTIVES 5

3. Overview of HR and Payroll IT Services 6

3.1 HR and Payroll IT Services Environment 6

3.2 Applications 7

4. SCOPE 9

4.1 Operations and Maintenance (O&M) Support 9

4.2 Development, Modernization, and Enhancement (DM&E) Support 9

5. TASK REQUIREMENTS 10

5.1 Project Management Support 10

5.1.1 Project Planning 10

5.1.2 Project Coordination 11

5.2 Analysis, Development, and Implementation Support 11

5.2.1 System Change Analysis 11

5.2.2 System Change Development 13

5.2.3 Documentation 14

5.3 Operational Support 14

5.3.1 Contractor Access Control Management (ACM) 14

5.3.2 Systems Operations and Monitoring 14

5.3.3 Audit Support 15

5.3.4 Testing 15

5.3.4.1 Test Strategy 16

5.3.4.2 Test Plans 17

5.3.4.3 Test Scripts 17

5.3.4.4 Testing Controls 18

5.3.4.5 Unit/Module Testing 18

5.3.4.6 System Testing 19

5.3.4.7 User Acceptance Testing 19

5.3.4.8 Integration (End-to-End) Testing 19

5.3.4.9 Regression Testing 19

5.4 Payroll, Corporate Application Data Warehouse (CADW), Enterprise Data Warehouse (EDS), and Quality Management System (QMS) Support 20

5.4.1 O&M Support 20

5.4.2 DM&E Support 21

5.4.3 Optional Surge Support 21

5.4.4 Optional Travel 21

6. PERSONNEL REQUIREMENTS 21

6.1 Key Personnel 21

6.1.1 Key Personnel Federal HR/Payroll IT SME Requirements 22

6.1.2 Non-Key personnel 23

6.2 Desired Skills and Knowledge 24

7. DELIVERABLES 25

7.1 Weekly Status Reports 32

7.2 Monthly Status Reports 33

7.3 Risk Management Plan 33

7.4. Quality Assurance and Quality Control Plan (QASP) 34

7.5 Delivery Instructions 34

7.5.1 Format 34

7.5.2 Deliverable Review and Acceptance 34

7.6 Inspection and Acceptance 35

7.7 Performance Measures 36

8. PLACE AND PERIOD OF PERFORMANCE 40

8.1 Place of Performance 40

8.2 Period of Performance 41

9. PHASE IN/PHASE OUT 41

9.1 Phase In/Phase Out 42

9.1.1 Phase In 42

9.2 Phase Out Transition Management Plan 43

10 TRAVEL 45

11 GOVERNMENT FURNISHED EQUIPMENT/INFORMATION 46

12 SECURITY 47

12.1 IT Security Procedural Guide: Security and Privacy Requirements for IT Acquisition Efforts CIO-IT Security-09-48 47

12.2 GSA Directive ADM 2181.1 Homeland Security Presidential Directive (HSPD-12) And Background Investigation Requirements 47

12.3 General Compliance Requirements 48

12.4 Sensitive Information Storage 48

12.5 Protection of Information 49

12.6 Confidentiality and Nondisclosure 49

12.7 Privacy Act 50

12.8 Section 508 Compliance 50

12.9 Comprehensive Security Requirements for Government Information Systems 50

13 CONTRACT ADMINISTRATION 51

13.1 Government Points of Contact 51

1. BACKGROUND

This Task Order (TO) pertains to the required development and technical support activities for applications maintained by the Payroll and Human Resources Information Technology (HR IT) Services Division.

1.1 Business Line

This Task Order is intended to procure Development, Modernization, and Enhancement (DM&E), and Operations and Maintenance (O&M) support services for ePayroll and HR IT applications.

2. OBJECTIVES

The Government anticipates achieving the following objectives through the services provided under this contract:

● Deliver continuous customer support to internal and external users.

● Furnish O&M technical support for software applications, backend processes, utilities, and both Commercial-Off-The-Shelf (COTS) and Government-Off-The-Shelf (GOTS) software maintained by HRIT.

● Enhance the usability standards of existing applications through DM&E efforts, ensuring compliance with federal information systems security and customer requirements.

● Maintain proactive and responsive communication with system users to guarantee timely resolution of complex inquiries and satisfactory solutions.

● Provide new application solutions to fulfill customer needs, adhering to GSA system development life cycle guidelines.

● Implement System Development Life Cycle (SDLC) and agile project management and development principles and best practices.

● Ensure rigorous compliance with GSA IT Security Policies and all pertinent GSA and NIST standards and guidelines, as well as other Government-wide laws and regulations governing the protection and security of information technology.

3. Overview of HR and Payroll IT Services

An overview of the systems and applications included in this PWS are delineated in the proceeding sub-sections.

3.1 HR and Payroll IT Services Environment

The software and tools currently employed for the Division's applications and systems are as follows:

● Visual Cron 12 - Visual Cron serves as the process job scheduling software, facilitating interactions with databases and SFTP servers.

● Pentaho 9.3 - Pentaho is utilized as the ETL (Extract, Transform, Load) software for data extraction from databases and the execution of database procedures.

● MySQL Work Bench 8.0 - MySQL Workbench functions as the user interface for engaging with the MySQL database.

● MySQL database 8.0 - The MySQL database is utilized for data storage and processing.

● Toad For Oracle 16.3 - The Toad for Oracle server operates as the user interface for interacting with the Oracle database.

● Oracle database 19c - The Oracle database is employed for data storage and processing.

● DBeaver 25.2.5.202511161745 - DBeaver serves as a unified user interface for MySQL and Oracle databases.

● Visual Studio 2022 - Visual Studio is a software application utilized for the development of .Net applications.

● Visual Studio Code 1.101.1 - Visual Studio Code functions as a professional-grade software application utilized for Python programming development.

● Python 3.14 - Python is requisite for the execution of Python code.

● Notepad++ 8.8.2 - Notepad++ is a code editor featuring reserved word highlighting, file comparison capabilities, and advanced file search functionality.

● Microsoft Visio 2019 - Microsoft Visio is utilized for the creation of workflow and Entity-Relationship (ER) diagrams.

● SQL Developer 24 - SQL Developer is software that provides developers with access to interact with the Oracle database.

3.2 Applications

The support services shall cover the following applications as well as any other applications managed by the Division.

Business Line

Application/System Description ePayroll Labor Distribution System (LDS)

Platform: Oracle

The Labor Distribution System (LDS) is used to apply salary data and time and attendance data, from PAR and HR Links respectively, to various projects to determine the cost for the projects for budgeting, cost control, performance measurement, determining fees and prices for services, assessing programs, and management decision making. LDS provides OCFO and clients a centralized historical source for obtaining information in support of Payroll, Labor Distribution, ABC/M, OPM Accounting, RRB Accounting, and limited HR information.

LDS also includes two backend jobs: 1.)

Labor Code Maintenance 2.) Labor Projection Module ePayroll PAR (Payroll Accounting and Reporting)

Platform: Oracle

PAR consists of an operational transaction database for payroll data and a reporting DataMart, and both of these provide reporting and accounting transactions to GSA and clients’ core financial system. PAR is supported by time and attendance and miscellaneous reimbursement information systems. A brief description of each of the application modules are included below.

PAR is a major application that provides complete payroll functionality for an employee’s entire service life, from initial hire through final payments at separation and submission of retirement records to the Office of Personnel Management. PAR is a fully automated, nationwide, civilian payroll system. GSA professionals developed, designed, programmed, implemented, and maintained PAR at GSA’s Heartland Finance Center, Kansas City, Missouri. It provides a full range of payroll services for 17700 employees, which includes GSA and 27 independent agencies or presidential commissions.

ePayroll Voluntary Leave Transfer Program

(VLTP)

Platform: Oracle with .Net front-end

Web-based module used to donate leave to an approved Shared Leave recipient.

HR IT HR Links

GSA’s HR system which provides personnel action, time management, and benefits processing for all of GSA’s 11800 employees

HR IT GSA Jobs

Platform: FedRAMP Saas

GSAJobs is a Software as a Service (SaaS) solution that is used for electronic automation of staffing and HR employment recruiting functions.

HR IT GSA OLU GSA Online University is a Software as a

Platform: FedRAMP Saas

Service (SaaS) solution that is utilized for the delivery of online learning for GSA.

HR IT Corporate Application Data Warehouse (CADW)

Platform: Database

- Percona MySQL

The CADW is the consolidated data store and transformation system built in-house by GSA for human resource information and analytics.

HR IT HR Quality Management System (QMS)

Platform: Database

- Percona MySQL, Web - Nginx/.net Core

The HR QMS application was built inhouse by GSA and provides GSA HR specialists the workflow tools to perform their day-to-day jobs. This includes the analysis for determining data errors, discrepancies and anomalies in the various HR systems and information for correcting the data issues.

HR IT GRB Assist

Platform: Database

- MS SQL Server, Web - IIS/.NET

4. SCOPE

The following services are required under this task order:

4.1 Operations and Maintenance (O&M) Support

This O&M activity supports all applications maintained by HRIT. O&M includes all projects, except those that expand an asset's capacity or significantly exceed the original intent's requirements.

4.2 Development, Modernization, and Enhancement (DM&E) Support The DME activities support all applications maintained by HRIT, and shall support and incorporate all projects that result in the creation of new information technology (IT) assets or those that modify or alter existing IT assets. These activities are undertaken for the purposes of improving capability or performance, implementing legislative or regulatory requirements, and/or satisfying agency-specific requirements.

5. TASK REQUIREMENTS

5.1 Project Management Support

The Contractor shall be responsible for oversight functions to accomplish the requirements of this task order and to achieve the required performance objectives.

The Contractor shall:

● Report the "burn rate"; providing the names of Contractor personnel, detailing the hourly labor rate and the number of hours expended against the respective labor category

● Report contract performance and identify any problems or issues as early as practicable.

● Review deliverables to ensure strict conformance to the Quality Assurance Surveillance Plan (QASP) and specifications.

● Resolve resource issues within the scope of their responsibility.

5.1.1 Project Planning

Within seven (7) business days of award, the Government shall contact the Contractor to request a kick-off meeting. The Contractor shall have 7 business days to agree on a date. The designated government personnel will be in attendance. The Contractor shall come prepared to the kick-off meeting to discuss the following:

● Any proposed changes to resource allocations and/or staffing plans;

● Proposed project timeline for key milestones; and

● Deliverables.

The Contractor shall deliver the following project planning deliverables per the schedule described in Section 8 Deliverables.

5.1.2 Project Coordination

This task order requires coordination with several different internal and external stakeholders, which may be government personnel or other contractors. The Contractor shall be responsible for this coordination. Duties will be performed through collaboration with all parties. Chain of command and roles and responsibilities shall be established and maintained to work effectively in this type of environment. Coordination shall take place in writing through formal processes such as status reports and participation in project meetings and informal processes while working side by side.

5.2 Analysis, Development, and Implementation Support

The Contractor shall support system configuration changes, database changes, upgrades, required data conversions, training on all phases of testing as described under the testing tasks, and user support for major software and system changes. Additionally, the Contractor shall manage and implement new applications and maintain existing applications within the division.

5.2.1 System Change Analysis

For all system changes, the Contractor shall provide the following services:

● The Contractor shall analyze the requirements.

● The Contractor shall develop Impact Analyses (IAs) that document the impact of proposed changes to the government’s applications. The IAs shall include:

o Rough estimates of life cycle costs for proposed new or changed systems, including operations and maintenance costs with the use of appropriate technology, tools, and methods.

o Time estimates for proposed new or changed systems, including operations and maintenance with the use of appropriate technology, tools, and methods.

● The Contractor shall prepare Requirements Analyses which include Hardware Requirements Analyses and Technical Environment Assessments.

o The Hardware Requirements Analysis shall include the need for application servers, database servers, and other devices required for government upgraded software.

o The Technical Environment Assessment shall include the need for Application Server software, database server software, and any middleware or other software required to operate the government software.

● The Contractor shall assist current or potential application users in identifying and describing problems or system performance improvements, through troubleshooting.

● The Contractor shall investigate the source and impact of identified issues and problems, determine the feasibility of a system solution, and identify the system solutions.

● The Contractor shall analyze users' business requirements and prepare user stories and/or functional specifications for a proposed new or changed system.

● The Contractor shall assist and guide prospective users of a proposed new or changed system in:

o Quantifying the benefits of having the system (or the penalties for not having it) o Assessing the impact of the system on their organization and on the operation of their business.

● The Contractor shall prepare all Systems Development Life Cycle documentation for the Planning, Requirements, Design, Development, Testing, Implementation, and Operation and Maintenance phases.

● The Contractor shall assist the Government Project Lead/Task Lead in:

o Analyzing the costs, benefits, and risks of the proposed system change.

o Conducting alternative analysis.

o Understanding the Business Line Executives Concept of Operations and subsequent requirements of the system.

o Providing input for Executive Business Cases.

o Providing recommendations for interim and long-term solutions.

o Drafting ‘As Is’ and ‘To Be’ diagrams.

o Analyzing existing business processes and recommending changes to streamline, enhance, or reengineer.

o Providing guidance on the implementation.

● The Contractor shall prepare, in conjunction with developers, users, implementers, and operations representatives, the acceptance (or parallel) test plan for the new or changed system.

● The Contractor shall prepare, in conjunction with developers and test team, reusable test scripts for the new or changed systems.

● The contractor shall perform system change analysis related to security scanning findings.

5.2.2 System Change Development

● The Contractor shall be responsible for planning, processing, and development and code changes.

● The Contractor shall be responsible for design and development of systems making specific determinations pertaining to maintaining existing application performance and efficiency.

● The Contractor shall review and repair legacy code.

● The Contractor shall conduct system analysis and development to keep government systems current with changing technologies.

● The Contractor shall analyze system specifications and translate system requirements into technical specifications.

● The Contractor shall develop System Design Documents (SDDs) that annotate and trace requirements for design features of government applications.

● The Contractor shall analyze system changes and unit test results of the applications.

● The Contractor shall develop Implementation Plans that annotate and trace requirements for deployment of government applications.

● The Contractor shall participate in GSA IT project discussions, prove-out and testing of platforms, and technical review and comment when directed.

● The Contractor shall assist in the standardization of various applications through engineering and deployment support.

● The Contractor shall support development tool-sets.

● The contractor shall perform system development related to security scanning findings.

5.2.3 Documentation

The Contractor shall design, develop, and maintain user manuals and corresponding training programs for the systems being developed and maintained.

5.3 Operational Support

5.3.1 Contractor Access Control Management (ACM)

The Contractor shall perform re-certification of all contract staff, as well as track the users on contract without system access. This includes managing background investigations, training certificates, access request forms, and other required government forms for all active contractors.

5.3.2 Systems Operations and Monitoring

The Contractor shall review a multitude of system event logs from government systems.

● The Contractor shall identify any operational errors and determine corrective actions needed.

● The Contractor shall identify any exceptions and determine if the exception(s) is a true security incident after analysis of the information collected.

● If a valid security incident has been detected, the Contractor shall notify the Information System Security Manager (ISSM) and work with system and application staff to mitigate the incident and take the appropriate measures to preserve evidence.

● The Contractor shall work with the ISSO and system owner to take any necessary action to correct or mitigate identified incidents.

5.3.3 Audit Support

● The Contractor shall re-certify database accounts for system applications.

● The Contractor shall verify the list of accounts and ensure that the proper paperwork is on file for each user to recertify for the fiscal year.

● The Contractor shall provide Statements on Standards for Attestation Engagements (SSAE) 18 and Financial System Audit (FSA) fiscal year audit support to independent auditors for government systems

● The Contractor shall send evidence of log reviews, raw logs, user reports to the Government and provide online demonstrations or review repositories and processes.

● The Contractor shall gather and provide other evidence and documentation as required for all required audits and self-assessments

● The Contractor shall maintain required application security documentation

● The Contractor shall draft and execute Plans of Actions and Milestones and Corrective Action Plans for audit findings

5.3.4 Testing

The Contractor shall conduct individual unit or module testing, system and regression testing for all applications maintained by the Division.

The Contractor shall provide support to the Government to perform user acceptance testing, end-to-end testing, load testing, regression testing, cycle testing, and patch testing as required.

All testing, excluding the unit testing, shall be performed in the government test environment as directed by the COR.

All Contractor testing shall be documented to the extent that tests can be retested based on the documentation. The Contractor shall provide a written description of any error or deficiency that the Government identifies or that is identified to the Contractor. The Contractor shall correct defects or deficiencies in the application(s) and related documentation.

The Contractor shall test all development work for new/existing applications and their supporting processes in the development and test environments prior to installation in the production system environment. Software shall not be passed to the Business Line for User Acceptance Testing (UAT) unless acceptance criteria have been met. Decisions to move software into production shall be approved by the Government.

5.3.4.1 Test Strategy

The Contractor shall follow and maintain or create a new Test Strategy document as directed by the Government PM or COR that implements industry best practices. The purpose of the Test Strategy document is to ensure that the Contractor and the Government have a mutual understanding of how the test process will operate. The Test Strategy shall address the following:

● Testing methodology, tools, and reporting

● Approach, definition, and coverage for all testing, including unit, system, acceptance, integration, and regression tests

● How configuration management and change management will be incorporated into the testing process;

● Criteria for completion and closure of testing

● Documentation that will be produced during testing, including the format of the Test Plan

5.3.4.2 Test Plans

The Contractor shall follow and maintain, or create, a new Test Plan as directed by the Government PgM/PjM or COR that addresses all software testing for new and existing applications and their supporting processes. The Test Plan shall document the following:

● The approach and methodology to conduct unit testing, system testing, acceptance testing; integration testing (including end-to-end testing), regression testing, performance testing, user load testing and batch performance testing

● The approach and methodology to conduct performance testing

● How the Contractor shall assist the Government in performing the acceptance and integration (end-to-end) testing

● Detailed Test Cases, including Test Case descriptions, setups, and expected results

● Detailed Performance Test Cases, including Test Case descriptions, setups, and expected results.

For tasks involving software development, the Test Plan shall include a requirements traceability matrix (RTM) to ensure appropriate tests are performed as changes are made. Test Cases shall be based upon the functional and technical analysis and shall be developed with a thorough knowledge of the government’s (GSA’s) data set and performance requirements. The Test Plan and Test Cases shall be reusable throughout the application/solutions life cycle.

5.3.4.3 Test Scripts

After the Test Plan has been approved by the Government, the Contractor shall develop test scripts that implement/validate the test cases identified in the Test Plan. The test scripts shall include the detailed testing steps, in addition to the data listed in the Test Plan. The Test Scripts shall be sufficiently robust to support user acceptance testing (UAT). The Test Plan and the test scripts, which will be used by the Government to perform UAT, must be agreed upon by the Government in advance and may be augmented with additional tests.

● The Contractor shall deliver a RTM for all test efforts

● The Contractor’s RTM template must be approved by the COR

5.3.4.4 Testing Controls

The Contractor shall conduct tests in accordance with the Test Plan. The Contractor shall perform or participate in testing activities in accordance with the following table1:

Testing Responsibilities

Test Type Government and/or

IV&V

Contractor

Unit/Module O

System O

User Acceptance O SH

Integration (End to End) O SR

Load Testing SR O

Contractor Regression O

Government Regression O SR

The Contractor shall document, analyze, correct, and re-test discrepancies.

Controls shall be in place to ensure that the testing is complete and accurate and that the results are acceptable to the Government before the system is put into use. Controls shall provide checks and balances and separation of duties.

Controls shall also serve to track testing progress against schedules and the accuracy of the system. Controls, at a minimum, shall be in accordance with GSA Configuration Management processes and separation of duties.

5.3.4.5 Unit/Module Testing

1 In the Testing Responsibilities table, O indicates testing type owner, as assigned;

SR indicates supporting role in testing and SH indicates shared participation in Independent Verification and Validation (IV&V).

The Contractor shall perform software unit/module testing and software quality assurance inspections and audits in the development environment. When the Contractor has completed this testing, it shall be turned over for placement under configuration control for promotion from the development environments to the controlled environments for system testing.

5.3.4.6 System Testing

The Contractor shall perform system testing that includes the testing of functional and technical requirements and system integration across modules both internal and external. Discrepancies shall be documented, analyzed, corrected, and re-tested. The system test must be completed, documented and accepted by the Government. It shall then be turned over for placement under configuration control for promotion to Government test environments.

5.3.4.7 User Acceptance Testing

The Contractor shall support the Government’s UAT with instructions, Subject Matter Expert (SME) support, software quality assurance inspections, and audits.

When acceptance testing is completed and the Government has approved the code, it shall be turned over for placement under configuration control for promotion to the UAT environment. Errors will be reported through the configuration process for correction and retesting.

5.3.4.8 Integration (End-to-End) Testing

The Contractor shall support the Government’s Integration (End to End) Testing.

The Integration Testing includes testing all newly added or upgraded functionality of the HRIT applications. The Contractor shall provide required assistance and work closely with all parties involved in Integration Testing.

Discrepancies shall be documented, analyzed, corrected, and re-tested through the configuration control process.

5.3.4.9 Regression Testing

The Contractor shall conduct regression testing on an ongoing basis to ensure changes to the system have not impacted the system functionality and performance. The Contractor shall plan, schedule, test, and provide regression testing results to the Government.

5.4 Payroll, Corporate Application Data Warehouse (CADW), Enterprise Data Warehouse (EDS), and Quality Management System (QMS) Support

5.4.1 O&M Support

The Contractor shall provide O&M support for the payroll, CADW, EDS, and HR

QMS.

● Support the CADW upgrade/patch process and ensure the prevention of unintended consequences associated with implementation of upgrades/patches in GSA’s production environment

● Maintain CADW to support the existing and new HR, Payroll, Training, Financial data, and data from other data sources

● Maintain Database Structures to support the CADW

● Maintain custom Business Objects (BO) Universes and reports

● Maintain Interface Processes

● Support performance optimization of processes accessing source system data when required

● Support a patch management evaluation process that includes quarterly patch analysis, testing, and certification that the functionality of CADW will be unaffected in the newly patched operating environment

● Provide Tiers 2 and 3 Help Desk Support for CADW using ServiceNow (or other Government provided tool) to track and resolve trouble tickets, user inquiries, and requests for enhancements

● Remediate audit, security, and privacy related findings

● Maintain HR QMS processes

5.4.2 DM&E Support

The Contractor shall provide development, modernization, and enhancement DM&E support for the Payroll, CADW, EDS, and QMS as follows:

● Enhance and expand Payroll, CADW, and HR QMS to improve OHRM reporting

● Add new business validations rules, identifying reconciliation issues, and routing to appropriate HR staff

● Build new interfaces

● Add HR Business Rules for error identification

● Data modeling and migration support

● Add new attributes to CADW

● Enhance, build, and maintain BO Universes to support CADW

● Support migration of existing data to the GSA Enterprise Dataware

System

5.4.3 Optional Surge Support

The Government may exercise an optional surge Labor Hours task support requirement, as needed, to request that additional Contractor personnel be assigned to perform a variety of tasks. The Contractor personnel shall perform duties as specified by the COR or the Government Project Lead for a defined period as agreed to by the Government and the Contractor.

5.4.4 Optional Travel

The Government may authorize travel in support of major initiatives where the contract staff cannot attend virtually. All travel must be approved in advance by the COR.

6. PERSONNEL REQUIREMENTS

6.1 Key Personnel

The Contractor shall assign to the Contract tasks qualified personnel to manage the project. Certain individuals shall be designated as Key

Personnel. Key Personnel shall be dedicated and full time. Key Personnel must be experts in their field.

The Payroll IT Services has a critical need to maintain highly qualified contractor resources to maintain day-to-day payroll operations and respond quickly to federally mandated projects. Unfortunately, quickly implementing emergency payroll changes to accommodate furloughs, and natural disasters seem to be the new normal for payroll operations. In addition, the Payroll IT Services Branch must maintain contractors who have the federal payroll subject matter expertise required to support the Payroll Modernization project which is currently in the execution phase.

Therefore, the Government has identified three (3) Federal Payroll/HR IT SMEs as Key Personnel for this Task Order.

6.1.1 Key Personnel Federal HR/Payroll IT SME Requirements

● At least 5 years of Federal Payroll data subject matter expertise;

● At least 5 years of Federal HR data subject matter expertise;

● At least 5 years of experience supporting Oracle based federal HR &

Payroll solutions;

● Recent experience (within 1 year) supporting a Federal Payroll Shared

Service Provider (SSP) with Evaluation Criteria preference given to Offeror’s whose proposals include Key Personnel who have developed interfaces directly with the Office of Personnel Management (OPM) and the Internal Revenue Service (IRS); This is important because GSA will continue to be a Payroll SSP even if GSA migrates to another payroll solution and decommissions PAR.

● In accordance with Homeland Security Presidential Directive 12 (HSPD-12), SMEs must possess a Department of Homeland Security (DHS) Public Trust Tier 2 clearance at the beginning of this Task Order’s Period of Performance (PoP)

● GSA IT domain expertise and experience

The contractor shall not remove or replace any personnel designated as key personnel, for this Task Order, without the written concurrence of the Contracting Officer (CO). This notification shall be no later than ten (10) calendar days in advance of any proposed substitution and shall include justification (including resume(s) and labor category of proposed substitution(s) in sufficient detail to permit evaluation of the impact on Task Order performance. The Government will approve initial contractor key personnel at time of award. Replacement key personnel will be approved in writing by the Government.

Key Personnel position vacancies shall be filled within 14 calendar days after start of vacancy, unless otherwise approved in writing or directed in advance by the CO. Position vacancies shall not exceed 14 calendar days from start of vacancy to replacement, unless otherwise approved in writing or directed in advance by the CO.

Prior to substituting personnel specified in proposals in response to an RFQ, the contractor shall notify the Government CO and the COR. Substitute personnel qualifications shall be equal to, or greater than, those of the person(s) that are being substituted for. If the Government CO and the COR determine that the proposed substitute personnel is unacceptable, or that the reduction of effort would be so substantial as to impair the successful performance of the work under the Task Order, the contractor may be subject to cancellation or termination for cause.

6.1.2 Non-Key personnel

Position vacancies shall be filled within 30 calendar days after start of vacancy, unless otherwise approved in writing or directed in advance by the CO. Position vacancies shall not exceed 30 calendar days from start of vacancy to replacement, unless otherwise approved in writing or directed in advance by the CO. The Contractor shall provide a detailed description of the change, to include the title and criteria for the position(s), and demonstrate the appropriate expertise and credentials to properly meet the requirements and qualifications of the subject position.

The Government shall be afforded the opportunity to review resumes and provide feedback on the final selection of proposed personnel replacing or substituting for non-key positions prior to their onboarding.

For Non-Key personnel the Contractor shall initiate a DHS HSPD-12 Tier 2 clearance adjudication process within three (3) days of position vacancies being filled.

6.2 Desired Skills and Knowledge

The Contractor shall provide adequate staffing resources to fully execute the requirements contained in this PWS, including the optional surge support as needed by the Government. Preference will be given to an Offeror who proposes Key Personnel who have a current Tier 2 (or MBI) level clearance, which will allow them to start work immediately after contract award. Non Key contractors performing under this Task Order must immediately be submitted for a Tier 2 clearance because they will have access to Sensitive But Unclassified (SBU) and Personally Identifiable Information (PII). GSA desires an Offeror to propose key personnel who have a current DHS Tier 2/MBI clearance and have demonstrated experience in similar IT domain expertise.

The Contractor shall possess the ability to design and develop software to fulfill technical and functional requirements utilizing, but not limited to, the following technologies and languages:

o Development and Office Support

▪ .NET Core and ASP.NET languages and technologies (e.g. C#, Entity

Framework, Web API, third-party components, etc...)

▪ Software Development IDEs (e.g. MS Visual Studio, Eclipse, IntelliJ, iText, etc.)

▪ Java Enterprise Edition (JEE), Java Server Faces (JSF)

▪ Web Services (e.g. WSDL, SOAP, REST, JSON, XML etc.)

▪ Business Objects Universe Design

▪ HTML

▪ Web Development (e.g. stylesheets, JavaScript, LESS, Bootstrap, JQuery, etc.)

▪ Google Office (i.e. Calendar, Gmail, Docs, Sheets, Chat, Meet, Slides, Forms, etc.)

▪ MS Office Suite (e.g. Excel, MSAccess, VBA, etc.)

o Databases

▪ Oracle Relational Database Management System (RDBMS)

▪ MySQL RDBMS

▪ MS SQL Server RDBMS o Interoperability

▪ Extract, Transform, Load (ETL) (e.g. Pentaho, ETL, etc

▪ Cloud technologies (e.g. AWS, GCP, Azure, etc.)

o Version Control tools

▪ ClearCase

▪ Git

▪ GitHub

7. DELIVERABLES

All deliverables shall adhere to the following general acceptance criteria, in addition to the acceptance criteria stated in the Deliverables and Acceptance Criteria table below.

All deliverables and all tasks to be performed shall be in accordance with the specifications defined in Sections 5, Task Requirements, and 6, Personnel Requirements.

All deliverables, including memoranda, records, reports, computer programs and inventions, developed specifically for this requirement by the contractor, shall become the property of the government, including the proprietary rights therein.

Deliverables and Acceptance Criteria

# PWS

Section

Frequency Deliverable Acceptance Criteria

1 5.1 Monthly, 30 days post award

Burn Rate Report Report the “burn rate” of the schedule-based budget, by labor category and the names of Contractor personnel, that lists the hourly labor rate and the number of hours per day expended against that labor category and/or person

2 5.1 Project Management Plan (PjMP)

– Receipt of incumbent’s project management plan is due within five (5) business days of award

– Monthly updates

– Receipt of incumbent’s project master schedule and updates are due within five (5) business day of award

– Monthly updates

– Within five (5) business days after project kick-off unless COR approves extension

– Addresses the project scope, assumptions, constraints, objectives, tasks, task durations, resources, key milestones, deliverables, and risks.

– Includes all planned projects, initiatives, and activities; due dates; dependencies;

primary resources; key milestones

– Identifies schedule conflicts and risks

3 5.1 Receipt of incumbent’s PjMP is due within five

(5) business days of award Monthly updates

– Project Master Schedule/IMS

– Receipt of incumbent’s project master schedule and updates are due within five (5) business day of award

– Monthly updates

– Within five (5) business days after project kick-off unless COR approves extension

– Includes all planned projects, initiatives, and activities; due dates; dependencies;

primary resources; key milestones

– Identifies schedule conflicts and risks

4 5.1 Within five (5) business days after project kick-off unless COR approves extension

Work Breakdown Structure for O&M and DM&E Activities

– Delivered via Microsoft Project. Excel or Smartsheet

– Provides detailed information about tasks, resources, duration, dependencies, start dates, end dates, and other information to calculate earned value variances

5 7.1 Weekly (Mondays) Weekly Status Report Will Include the following:

– Executive summary

– Prior week’s accomplishments

– Activities planned for the current week

– For new development and implementation work, the status, to include objectives met, work completed and work outstanding

– Successes stories

– Issues/actions, resolutions or obstacles

Section

Frequency Deliverable Acceptance Criteria impeding progress and recommended solutions

– Potential schedule, cost or scope problems

6 7.2 Monthly (Due no later than 10 business days

Monthly Status Report Will include the following:

– Status Report summary

– Key activities and deliverables for the past month by task

– Key activities and deliverables for the current month by task

– Key activities and deliverables proposed for the following month

– by task

– For new/existing development and implementation work, the status, to include objectives met, work completed and work outstanding

– Status on risks and mitigation strategies

– Contractual changes, if any

– Potential schedule, cost or scope problems

– Summary of meetings for the past month

– Staff/resource status

– Summary information on the memoranda delivered during the past month

– Contractor personnel contact information

7 5.2.1

As required or Per approved project plan

Impact Analysis (IA) Includes:

– Implications of the Proposed

Change

– System Elements Affected by the Proposed Change

– Effort Estimation for a

Requirements Change (by Task)

– Comments from government

8 5.2.1

Per approved project plan

Requirements Analysis

(RA)

Includes:

– Entity Relationship Diagram

– Functional Requirements

– Technical Requirements

– Operational Requirements

– Security Requirements

– System Availability Requirements

– Performance Requirements

– Requirements Traceability Matrix

– Final Approved Requirements

9 5.2.2 Per approved (System) Change Includes:

Section

Frequency Deliverable Acceptance Criteria project plan Development Plan

(CDP)

– Design and development for O&M projects

– Design and development for DM&E projects

– Code/Peer Reviews

10 5.2.2 – Per approved project plan

– At each Milestone Review

SDLC documents, including but not limited to:

– Project Charter (PjC)

– CONOPS

– Impact Analysis

– Project Plan

– System Boundary Document

– Functional Requirements

Document

– Interface Control Document

– Customer MOU

– System Disposition Document

– System Design Document

– Level 0 Document

– Software Development

Document

– Implementation Plan

– Not all documents are required for each project

– Small O&M projects require minimal SDLC documents

– Large DM&E projects require full documentation

– Final documents required by the COR must be Reviewed and Approved by COR or one of the Branch Chief

11 5.2.3 As required or Per project plan

Developed or Maintained Training Materials

– Approved User Manuals and corresponding training programs.

– Existing User Manuals must be maintained

12 5.3.4.1 – Due ten (10) days before DM&E testing starts or

– Per project plan

Test Strategy Documents are required for all major DM&E projects

– Must be reviewed and approved by COR or one of the Branch Chiefs

– All test strategy documents must be peer reviewed

13 5.3.4.2 – Due per project plan

– All project plans must be reviewed by the COR or one of the HRIT Branch Chiefs

Test Plans are required for all O&M and DM&E projects

– Must be reviewed and approved by COR or one of the Branch Chiefs.

– All test plans shall be peer reviewed

Section

Frequency Deliverable Acceptance Criteria

14 5.3.4.3 – Due per project plan

– All test scripts must be reviewed by the lead analyst

Test Scripts for each New Interface or Report Development and Upgrade

– Test scripts are directly traceable to functional and technical/system requirements

– All test scripts shall be peer reviewed

15 5.3.4.5 – Per project plan

– Immediately following Development of code

Unit/Module Test Results For all code changes are required

– All unit testing must be peer reviewed

– All planned tests/test cases/test scripts have been executed

– All identified defects have been addressed

– All defect fixes were verified and regression on adjacent areas was successfully performed as required

– No unresolved high-severity defects exist that would adversely affect transition to the next phase

– As required, system code changes are tested with pass rates high enough to warrant transition to the next phase

16 5.3.4.6 – Per project plan

– After System

Testing by analyst(s)

System Test Results – All planned tests/test cases/test scripts have been executed

– Pass rates TBD

– All identified defects have been addressed

– All defect fixes were verified and regression on adjacent areas was successfully performed as required

– No unresolved high-severity defects exist that would adversely affect transition to the next phase

– As required, system interfaces are tested with pass rates high enough to warrant transition to the next phase

17 5.3.4.7 System Readines s for UAT

– Per project plan

– After System Testing by analyst(s)

– Schedule must be coordinated with end users

– Deliver system for UAT

– For UAT, prior unit and system testing shall have achieved 95 % testing pass rate

Section

Frequency Deliverable Acceptance Criteria

18 5.3.4.9 Per Project Plan Regression Test Results for Each New Interface or Report Development and Upgrade

– All planned tests/test cases/test scripts have been executed

– Pass rates TBD

– All identified defects have been addressed

20 5.4.1 5.4.2

Per project plan

Maintain on an on-going basis for existing HR IT systems

Create new documentation for new implementations by leveraging existing documentation

– Upgrades and Patching

– Operational CADW

– Custom BO universes and reports

– Optimized performance

– Regular patching

– Help Desk ticket management and reporting

– Implementation of approved DM&E initiatives that meet customer requirements and are deployed within budget and on schedule

– New Business Objects (BO) universes and reports meet all organizational security requirements

– Accurate technical documentation

21 7.4 Quality Assurance Surveillance Plan

Include with proposal/quote – Provides visibility into the progress of the tasks

– Reports contract performance and identifies any problems or issues as early as possible

– Provides project level reporting for large projects

– Implements peer reviews for analysts that includes reviews of requirements documentation and testing

– Implements peer code reviews for programmers

– Ensures all major milestones are met

22 8.1.1 Include with proposal/quote

Phase In Plan Will include the following:

– Scope

– Project plan

– Work breakdown structure

– Schedule including timeline, milestones and actions required to complete the total transition effort within 30 calendar days

Section

Frequency Deliverable Acceptance Criteria

– Identification of Key Personnel positions and how they will be phased-in.

– Security clearance vetting;

and the acquisition of identification and/or facility access badges as applicable.

23 8.1.2 No later than (NLT) sixty (60) days prior to the expiration of the Task Order

Phase-Out Transition Management Plan

Will include the following:

– How the incumbent contractor will coordinate with the incoming contractor and/or Government personnel to transfer knowledge;

– Document and define the plan for providing on-the-job, application specific, training for the incoming Contractor personnel;

– Procedures for retaining the staffing levels necessary to maintain required services through the day of the contract’s expiration or termination;

– Schedule including timeline and milestones Provide a list of Government Off-The-Shelf systems (GOTS) and document and define the procedures and responsibilities for turning over all account access to the follow-on contractor required to manage GOTS;

– Project Management Processes;

– Points of Contact;

– Location of Technical and Project

Management Documentation;

– Status of Ongoing [Technical and

Operational] Initiatives;

– Appropriate Contractor-to-Contractor or

Contractor-to-Government Coordination (ensuring seamless transition);

– Transition of Key Personnel;

– Identification of Accomplished, Problematic, and/or Failed Schedules and Milestones;

– Identify Actions Required of the Government;

Section

Frequency Deliverable Acceptance Criteria

– Establish and Maintain Effective Communication with the Incoming Contractor/Government Personnel (for the remaining period of the transition via weekly status meetings);

– Procedures and responsibilities for performing physical inventory and reconciling and certifying of all Government Furnished Equipment (GFE) and Government Furnished Information

(GFI);

o Transition of Government Owned

Licenses, Accounts and Documentation to include project documentation o A timeline for offloading documents and the submission of final weekly and monthly reports o Detailed documentation sufficient to allow the follow-on Contractor to effectively transition into the contract.

o (Section 4.1.4.17 illustrates the types of documentation required.)

7.1 Weekly Status Reports

The Contractor shall prepare and submit a weekly status report to the COR that documents the activities and achievements in the prior week, by task; and the planned activities, milestones, deliverables due, by task, and meetings for the following week (Status Update). The weekly report shall document any risks that may impact the project(s) along with a mitigation plan to address each risk identified.

Weekly status reports shall include the following information for the Top 2 projects:

● Name of the project

● % Complete

● Target deployment date

● Status update

● Risks, conflicts, conflicting priorities; along with mitigation plan for each risk identified

● Benefit(s) to customer

7.2 Monthly Status Reports

To minimize the time spent on report preparation, the Contractor shall provide the Government with a Monthly Status Report (MSR) that includes the information below:

MSR shall include:

● Status Report summary;

● Key activities and deliverables for the current month, by task;

● Key activities and deliverables proposed for the following month, by task;

● For analysis, development and implementation work, the status, to include objectives met, work completed and work outstanding;

● Status on risks and mitigation strategies;

● Contractual changes, if any;

● Potential schedule, cost or scope problems;

● Staff/resource status, including new staff added to the contract or staff that have left the contract;

7.3 Risk Management Plan

The Contractor shall deliver a Risk Management Plan (RMP) to the Government for approval. The objectives of the RMP are to identify, address, and eliminate risks before they become threats to success or major sources of rework. The Contractor shall provide a process for identifying, documenting and handling risk and issues and help define appropriate mitigation strategies and solutions.

The Contractor shall support and participate in risk status reviews. The Contractor shall provide status information as specified by the COR in the correct format and level of detail.

7.4. Quality Assurance and Quality Control Plan (QASP)

The Contractor shall deliver a QASP to the Government for approval and implement a QASP program which establishes, implements, and maintains an effective QASP to ensure consistent technical quality for all deliverables, work products, and services performed under this Contract. The QASP program shall include management and technical reviews and audits to validate the quality of the work performed by the Contractor's personnel and of the work performed by its subcontractors. The QASP program shall incorporate all processes required to develop, document, monitor, review, analyze and conduct the Contractor's development, testing, deployment, maintenance and execution.

7.5 Delivery Instructions

7.5.1 Format

Deliverables shall be submitted electronically to the Government unless otherwise requested. The Contractor shall include a cover letter with each submission, on the prime contractor’s letterhead, describing the contents.

Prior to the submission of deliverables, the Government and the Contractor will agree on format and nature of the content for the deliverable, to improve deliverable quality prior to effort being expended. Industry Standards and best practices will also be used as a guideline for developing deliverables where applicable.

7.5.2 Deliverable Review and Acceptance

Any deliverable produced under this contract will be accepted or rejected in writing by the Government. Each deliverable shall be provided in draft form unless otherwise noted. The Government will have ten (10) business days to review the deliverable and provide comments to the Contractor.