CFO FMD OneStream - PWS Final.pdf

1 | P a g e Performance Work Statement

U.S. Citizenship & Immigration Services

(USCIS)

Office of the Chief Financial Officer (OCFO)

Performance Work Statement

For

OneStream Implementation for Financial

Management

February 2026

2 | P a g e Performance Work Statement

1. INTRODUCTION:

The USCIS Office of the Chief Financial Officer (OCFO) is responsible for ensuring sound stewardship of USCIS fiscal resources, delivering accurate and timely financial reporting, enhancing financial management processes, and strengthening enterprise risk management and internal controls. The OCFO’s mission is to secure and protect resources in support of USCIS operations as part of Homeland Security.

To fulfill this mission, USCIS OCFO requires professional services to further expand the use of the OneStream application to support financial management operations.

2. OBJECTIVE:

The objective of this Performance Work Statement (PWS) is to obtain professional services for system configuration, production deployment, and ongoing operational support of the financial management components of the USCIS OCFO OneStream system, which is based on the commercial off-the-shelf (COTS) OneStream software.

USCIS OCFO has acquired OneStream on a SaaS basis and currently utilizes it for budget formulation and execution, with planned expansion into people planning and strategic alignment. The system is hosted by OneStream, and USCIS holds sufficient software licenses.

Throughout the task order period, the Contractor will employ USCIS Agile development methodology and follow OIT IT system development best practices. The Contractor will collaborate with OCFO business subject matter experts and product owners to gather requirements, configure the system, and deploy capabilities/modules incrementally via Agile sprints. Upon deployment to the production environment—hosted in the OneStream FEDRAMP-authorized vendor cloud—the Contractor will provide operations and maintenance (O&M) support for the system components.

Implementation will be managed in accordance with industry standards and USCIS-provided software development project management tools. The Contractor must demonstrate expertise in OneStream software capabilities, architecture, and security parameters, and transfer this knowledge to federal staff through informal knowledge transfer for users both within and outside OCFO.

Upon completion of this task order, USCIS OCFO will have operationalized system components (see Section 3) that are adopted and used by OCFO accountants and Financial Management Division (FMD) Financial Operating Center (FOC) staff, comply with security requirements and federal financial management regulations, and interface effectively with USCIS, DHS, and other federal systems to support efficient business operations.

3. SCOPE OF WORK:

This task order will be the primary vehicle to obtain professional services to operationalize the OneStream capabilities listed below.

3 | P a g e Performance Work Statement

The following tasks are in scope for this task order:

• Implement OneStream solutions in alignment with USCIS OCFO FMD requirements, including:

• Financial Closeout

• Payroll Management

• Financial Reconciliation and reporting for open commitments, obligations, unliquidated obligations, etc.

• Guided and narrative reporting for key OCFO financial and accounting reports submitted to DHS

• Phase out legacy tools and MS Access databases currently used for these operations

• Integrate data from the USCIS transactional system and data lake required to properly automate these business functions in OneStream. Data validation, transformation, and mapping are in scope

• Ensure system adoption through specialized and USCIS system configuration-tailored knowledge transfer to federal staff

• Contribute to the maintained system security posture that is currently in compliance with federal system security standards and has a valid ATO

• Provide program and project management for the Agile implementation

The Contractor must have experience implementing these functions within other federal agencies, possess proficiency in federal financial management and accounting (beyond general system integration), and demonstrate knowledge and experience working with Department of Treasury systems and the National Finance Center (NFC). Preferably, the Contractor should also be familiar with the DHS financial landscape, including FFMS and

DHS TIER.

As part of this task order, the Contractor will collaborate with another integrator responsible for configuring OneStream for Planning, Programming, and Budget Execution (PPBE) functions within the same system instance. The government expects both integrators to cooperate and make a joint good faith effort to achieve project objectives.

This collaboration will require both parties to:

• Share the development environment and coordinate configuration activities.

• Work together on user access and security. Currently OneStream is already integrated with the identity management system (ICAM) and Single Sign-On authentication in the current production instance.

• Coordinate testing efforts to ensure system integrity and avoid conflicts.

• Communicate and coordinate on any activities that may impact the other party’s work.

4 | P a g e Performance Work Statement

USCIS reserves the right to adjust the strategic direction of the technical implementation under this task order. The scope includes adapting to new or evolving technical approaches resulting from major modernization initiatives, such as the Department’s Financial Systems Modernization program, other enterprise-wide IT programs led by the USCIS Office of Information Technology, or government-wide initiatives directed by the administration.

Such shifts in the technical approach under the umbrella of the Financial Management operations (OCFO FMD) implemented within OneStream are within the scope of this task order.

4. CURRENT STATE:

USCIS currently conducts financial closeout and financial reconciliation utilizing the following tools:

• DHS Analysis – proprietary tool consisting of a SQL server database and MS Access front end

• MS Excel

• MS Access

The Contractor will be required to analyze the current business process, assess how it can be best represented in the OneStream COTS product, and, if applicable, recommend changes to the business process such that the activities accomplish the same ultimate goal but do not require COTS system customizations that might prevent future software upgrades.

OCFO uses multiple systems to accomplish operations. The OneStream system is currently interfacing with the following systems:

• USCIS Data Lake called eCISCOR via a flat file transfer for FFMS data – bi-directional

The core OCFO business systems include:

• CostPerform – fee analysis system – USCIS internal

• Federal Financial Management System (FFMS) – supported by U.S. ICE

• Table of Organization Positions (TOPS) - supported by U.S. ICE

• WebView - supported by U.S. ICE

• OneNumber – budget formulation – DHS

• TIER – financial system -DHS

• Invest – Investment management - DHS

• PRISM – procurement system - DHS

• Concur – enterprise travel system – DHS

• G-Invoicing – Department of Treasury

• Pay.gov - Department of Treasury

• OTCnet - Department of Treasury

5 | P a g e Performance Work Statement

• Collection Information Repository (CIR) - Department of Treasury

• Central Accounting Reporting System (CARS) – Department of Treasury

• Intra-governmental Payment and Collection (IPAC) - Department of Treasury

• National Finance Center – Department of Agriculture

• EPIC (reporting interface to NFC) – Department of Agriculture

OCFO also interacts with external commercial entities for some of its processes, such as CITI bank for government travel and small purchases credit cards.

Information on additional systems and legacy data that needs to be migrated into the new system will be provided to the Contractor on a need-to-know basis during the execution of the task order.

4.1 Technology Stack

The following table contains technology platforms that the Contractor will/may use for successful execution of the project:

Data platform Data visualization

Databricks, Python, Scala USCIS data lake and data warehouse in USCIS AWS cloud Tableau

Development & Test & Production Environments

GitHub: Used for Code Repository, Source Control, Branching and Merging

Jenkins CI/CD for automated deployments

OIT provides platform support and administration, as well as executes most deployments to production environments.

Development Management

Atlassian Jira and Atlassian Confluence

508 Compliance

508 compliance is applicable

Legacy Technology Solutions

Excel, SQL, MS Access, VBA

USCIS uses the Agile development principles for most of its IT solutions development. The Contractor will be expected to organize its development activities based on Agile and/or Kanban approaches and maintain the proper organization in Jira and Confluence. Use of

6 | P a g e Performance Work Statement

Agile/SCRUM ceremonies which may include but are not limited to backlog creation and grooming, user stories creation and scoring, sprint planning, User Acceptance Testing (UAT), conducting demos, and retrospectives is expected and required.

All epics, user stories, and planned sprints must be properly documented in Jira and will be reviewed by the government ITPM during weekly status meetings.

5. SPECIFIC TASKS/REQUIREMENTS:

The contractor shall execute the requirements of this PWS through the following tasks.

5.1 Task 1 – Implement OneStream Capabilities for the Financial Management Division and Financial Operating Center

5.1.1 Financial Closeout

Under this task, the Contractor shall automate the financial closeout process in OneStream.

Implementation will include, but is not limited to, General Ledger (GL) entry management, impact assessment and analysis of GL entries, TIER file submission activities such as clear all GTAS and TIER errors, make on top adjustments to the TIER file, upload TIER file to DHS HQ, and generation of required reports such as the Abnormal Balance Report, the Analytic and Tie Point Reports and official certifications for DHS on a monthly, quarterly, and annual basis. All entries shall be traceable (who, when, and what was changed), and auditable.

To achieve this, the Contractor shall collaborate with USCIS OIT and United States Immigration and Customs Enforcement to establish a connection between the FFMS stand-by reporting server at ICE and OneStream in the OneStream cloud environment, enabling real-time data exchange between systems. This integration will allow accountants to view the impact of reconciled GL entries in the financial system and make necessary adjustments to ensure timely closeout. The Contractor shall enable the function of uploading the Trial Balance with all its attributes into DHS TIER.

Additionally, the Contractor shall phase out the legacy DHS Analysis tool, ensuring a seamless transition with no disruption to operations.

The Contractor shall work with the accountants to determine how much of the historical data is required to be migrated into OneStream for OneStream to fully pick up operations.

5.1.2 Payroll Management

Under this task, the Contractor shall integrate payroll data from external systems—FFMS (for salaries) and NFC (for payroll roster)—into OneStream using the most efficient and secure data transfer methods available. The Contractor shall ensure the accuracy and

7 | P a g e Performance Work Statement timeliness of data uploads, implementing validation rules to maintain the completeness and integrity of payroll data.

The Contractor will collaborate with payroll management staff at the FOC, FMD- Accounting and Reporting Branch (ARB), and other OCFO divisions as required to automate the reconciliation of payroll transactions against financial records. The system should assist OCFO staff in identifying and resolving discrepancies between payroll data and General Ledger (GL) entries, and in mapping payroll transactions to the appropriate GL accounts. Where feasible, payroll entries to GL accounts should be automated.

The Contractor shall enable payroll accruals and reconciliation in OneStream, support payroll-specific calculations (including overtime, bonuses, incentives, and garnishments), ensure traceability of payroll to individual employees, enable payroll reclassifications, and provide the capability to post payroll adjustments such as retroactive payments and corrections. Workflows for payroll certification and approval shall also be implemented.

All payroll processes must be audit-compliant and adhere to federal regulatory and policy requirements. The Contractor shall support payroll audit activities as needed.

Additionally, the Contractor shall support associated reporting requirements and work with FOC and FMD staff to decommission legacy MS Access databases related to payroll management.

5.1.3 Financial Reconciliation

Under this task, the Contractor shall collaborate with the FOC Accounting Branch and the FMD ARB to automate the reconciliation of commitments, obligations, and accounts in OneStream. The Contractor shall provide automated ways in OneStream for FOC and ARB to perform reconciliations at various levels, including obligation analysis, tracking and reporting of unliquidated obligations, and transaction matching. The solution should streamline these reconciliation processes, enhance accuracy, and facilitate timely financial reporting.

5.2 Task 2 - Phase Out Legacy Tools

As referenced in Section 4, OCFO currently relies on several legacy tools to perform the financial functions described in Task 1. As part of the OneStream implementation, the Contractor shall assist FOC and FMD-ARB in transitioning from these legacy tools and fully adopting the new processes within OneStream.

This effort will include comprehensive testing to ensure the accuracy of accounts and financial functions in OneStream. Assurance may be achieved by operating legacy tools in parallel with OneStream for a defined period, or by employing other appropriate validation methods to confirm accuracy and maintain stakeholder confidence in the results.

5.3 Task 3 – Data Integration and Reporting

8 | P a g e Performance Work Statement

5.3.1 Data Migration

The Contractor shall collaborate with FMD subject matter experts (SMEs), OCFO groups, and other contractors to analyze historical data required for loading into OneStream. USCIS will provide multiple MS Excel and MS Access data sources that will require migration.

For the data migration effort, the Contractor shall:

• Conduct data analysis and mapping between historical data sources and OneStream.

• Execute data migration into OneStream using appropriate upload methods or scripts.

• Validate that historical data is accurately and completely loaded into OneStream.

Once OneStream assumes FMD operations, the Contractor shall work with USCIS OCFO and OIT to determine if migrated data should be represented in the USCIS data warehouse and OCFO data lake.

For the data warehouse effort, the Contractor shall:

• Assist in establishing data connections between the OneStream system and the USCIS data warehouse, which is already operational for budget data.

• Provide OIT with a comprehensive data dictionary and explain data relationships to facilitate sourcing into the data lake, integration with other datasets, or transformation for inclusion in a data mart.

• Maintain relevant system interfaces with the data warehouse and resolve interface issues as part of ongoing operations and maintenance (O&M) support.

The Contractor shall adhere to data parameters and standards established by the USCIS Chief Data Officer.

USCIS will retain ownership of all data and system configuration code. The Contractor will not charge USCIS for data or system configuration retrieval. Upon termination of services, the Government will migrate all business data to a location of its choosing, ensuring data integrity and relationships are preserved. Following Government data migration, the hosting Contractor will delete all Government data from its hosting platform in accordance with applicable federal laws, regulations, and agency policies or directives in effect at the time-of-service termination.

5.3.2 System Interfaces

The OneStream system must exchange data with multiple OCFO operational systems, as well as systems at the Department and federal government levels. Where feasible, the Contractor shall develop automated interfaces between the OneStream system and other relevant systems. The choice of interface type and technical parameters—such as fully automated, API-based, file-based, or simple upload—will be determined based on the

9 | P a g e Performance Work Statement technical platforms involved, data volume, frequency of data exchange, and required level of effort. These decisions will be made collaboratively between the Government and the Contractor during project execution.

USCIS is currently upgrading its cloud-hosted OneStream environment from Version 7.2 to Version 9 and implementing the Smart Integration Connector (SIC) as part of this upgrade.

At a minimum, with government assistance, the Contractor will be required to connect OneStream to FFMS (or its potential future replacement SAP) via SIC to ensure fast and consistent interface between the two systems.

In parallel, USCIS OCFO is modernizing other core systems through the Department Financial Systems Modernization initiative, specifically FFMS and TOPS. As CFO data and its structure evolve due to these modernization efforts, the Contractor shall ensure that all downstream system interfaces are re-mapped and re-pointed to the new data structures and shall document all updated data parameters.

Similarly, the Contractor shall collaborate with other parties to modify system interfaces as needed if the underlying source system(s) are upgraded, relocated, or undergo security changes that disrupt the normal flow of data.

5.3.3 Reporting and Analytics

USCIS wants to take advantage of guided narrative reporting native capability of OneStream, which includes combining structural financial and operational data with explanatory text, comments, and contextual analysis.

The system shall provide guided narration reporting functionality within OneStream. The Contractor shall collaborate with the user community to design and configure guided and narrative reports as part of each business function implementation, ensuring reports meet operational and business needs.

USCIS may choose to perform analytics on OneStream system data using other OCFO-supported data visualization and reporting tools, such as Tableau or Databricks. The Contractor shall coordinate with other contractor teams responsible for developing these analytics products, providing expertise on system data elements, relationships, and structures as needed.

5.4. Task 4 – User Adoption

The Contractor shall provide informal training, demonstrations, instructional videos, and user guides for system functionality deployed to production, supporting users both internal and external to OCFO.

The Contractor is expected to develop innovative and efficient approaches for delivering targeted user education that minimizes time commitment. User-centered and intuitive system and process design should reduce the need for intensive training.

10 | P a g e Performance Work Statement

Knowledge transfer to federal staff should be clear and manageable, enabling accountants and other personnel to become familiar with system functionality and capabilities in a structured manner that promotes comprehension and retention.

Successful user adoption will be the ultimate measure of effective implementation.

5.5. Task 5 – Contribution to OneStream Authority to Operate

The Contractor shall collaborate with the Government-appointed Information Systems Security Officer (ISSO) and the other integrator to provide all necessary system information related to the FMD portion of the system. This support is required for the USCIS OIT Information Security Division and USCIS CISO to maintain an active Authority to Operate (ATO) for the system.

5.6 Task 6 - Operations and Maintenance Support

The Contractor shall provide operations and maintenance (O&M) support for operational system modules upon their deployment to the production environment. The Contractor is responsible for monitoring system operations and taking proactive measures to prevent disruptions and outages within their area of responsibility.

O&M support shall include:

• Break-fix recovery for non-working functionality

• Operational support for the application, including resolution of broken interfaces resulting from changes in data structure and/or APIs in systems of record

• Refactoring and enhancement of functionality that does not meet user satisfaction, including redevelopment of workflows that are difficult for end users to execute

• Regression testing of operationalized system components during software upgrades

• Major functionality augmentation and enhancement to provide additional capabilities to operationalized system components, as required by regulatory, policy, or other changes in the operating environment

• During End of Year Closeout activities or other important reporting times, the Contractor shall provide on-site support to the federal accounting team.

The Contractor is expected to utilize and adhere to the same development practices outlined above and may use Kanban for break-fix and minor enhancement activities.

To ensure effective information flow and accountability, the Contractor shall work with the USCIS Service Desk to extend established mechanisms for user issue reporting and resolution to the FMD portion of the system. For example, users external to OCFO may contact the USCIS Service Desk to report system issues; therefore, appropriate Tier 0 and Tier 1 support must be provided. The Contractor shall collaborate with the Service Desk to establish clear lines of communication and proper procedures to support this objective.

11 | P a g e Performance Work Statement

5.7 Task 7 - Program Management

The Contractor shall provide Program Management support for planning, execution, and completion of all project activities in accordance with best project management practices.

While USCIS will provide management oversight, it is the responsibility of the Contractor to manage all corporate resources and supervise all Contractor staff in the performance of all work on this Task Order. The Contractor shall assign a Project Manager to this task who will manage the day-to-day activities of the Contractor staff.

The Contractor Project Manager shall be an employee of the Prime Contractor and have responsibility for the accomplishment of the task order. The Project Manager shall organize, direct, and coordinate the planning and execution of all activities, review the work of subordinates, including subcontractors, and ensure that the schedule, performance parameters, and reporting responsibilities are met. The Project Manager shall integrate the Contractor’s management and technical activities across this Task Order to ensure they are consistent.

The Contractor’s Project Manager shall be the primary interface with the CFO Technical PMO Program Manager or designee. Attendance at weekly status meetings and ad hoc meetings is required.

All lead personnel on the Task Order shall possess not only management skills, but technical skills as well and be hands-on executors, rather than just managers.

Independently of the number and size of subcontractors the prime Contractor partners with, the Contractor shall present a united team to the Government.

At the request of the COR, the Government Program Manager, or a Government Project Manager, the Contractor shall be required to prepare briefing materials, deliver briefings, participate in meetings with USCIS organizations and/or external organizations, and present program content. The Contractor shall develop, as necessary, written recommendations, oral presentations and/or executive briefing materials.

The following meetings are mandatory for the Contractor to attend and will be scheduled by the Government:

• Task Order Kick-Off meeting

• Technical Kik-off meeting with the program

• Weekly status meeting with Government BISS staff. The Contractor PM and technical leads shall participate (in person, if required)

• Other ad-hoc meetings scheduled by USCIS senior leadership or Government team

The Contractor will be required to interact with multiple other contractor teams. The Government expects full Contractor cooperation, proper meeting attendance, and good faith efforts to accomplish joint work.

12 | P a g e Performance Work Statement

6. APPLICABLE DOCUMENTATION:

The following documents apply to this PWS. It is expected that the Contractor will be familiar with these laws, regulations, and policies and will execute the tasks of this PWS in accordance with these regulations:

▪ Chief Financial Officers Act of 1990 (CFO Act)

▪ Federal Managers Financial Integrity Act of 1982 (FMFIA)

▪ Federal Financial Management Improvement Act of 1996 (FFMIA)

▪ Foundations for Evidence-Based Policymaking Act of 2019 (Evidence

Act)

▪ Immigration and Nationality Act of 1952 (INA)

▪ Office of Management and Budget (OMB) Circular A-11, Preparation

Submission and Execution of the Budget

▪ OMB Circular A-50, Audit Follow-up

▪ OMB Circular A-123, Management’s Responsibility for Internal Control

(effective beginning fiscal year 2006) (Appendices A, B, C, and D)

▪ OMB Circular A-127, Financial Management Systems

▪ OMB Circular A-134, Financial Accounting Principles and Standards

▪ OMB Circular A-136, Financial Reporting Requirements

▪ DHS Financial Management Policy Manual (FMPM)

▪ DHS Financial Accountability Act (FAA) of 2004

▪ DHS 4300A Sensitive Systems Handbook

▪ DHS Internal Control Playbook

▪ Federal Accounting Standards Advisory Board (FASAB) accounting standards, as issued

▪ Treasury Financial Manual (TFM), as issued by the Bureau of Fiscal

Service (BFS)

▪ Digital Accountability and Transparency Act of 2014 (DATA Act)

7. CONTRACTOR KEY PERSONNEL & QUALIFICATIONS:

The Contractor shall provide qualified personnel to perform all requirements specified in this PWS. An adequate number of cleared and qualified personnel shall be readily available to ensure continuity of services. All personnel working on this task order shall possess the necessary security clearance as addressed in the Security Requirements section of this PWS. The Contractor shall be timely and responsive during the performance of work. This is a “Non-Personal Services” contract. Contractors are not subject by the contract’s terms or by the manner of its administration, to the supervision or control prevailing in relationships between the Federal Government and its employees. Only the Contracting Officer (CO) can obligate USCIS for contract responsibilities. Although no contract employee or official is authorized to officially represent USCIS to any other party, contractor personnel will display decorum, dress, and behavior comparable to USCIS personnel.

13 | P a g e Performance Work Statement

The Government shall have the opportunity to review the qualifications, education, and experience of proposed key personnel to ensure compliance with this section. In accordance with HSAR 3052.215-70, before removing or replacing key personnel, the contractor shall submit sufficient information to support the proposed action to the CO at least ten (10) calendar days before the effective date of the proposed change.

7.1. PROGRAMMANAGER:

The Contractor shall appoint one (1) Program Manager (can be part-time at Contractor’s discretion) who shall organize, direct, and coordinate the planning and execution of all activities, review the work of subordinates, including subcontractors, and ensure that the Government requirements for the OneStream system are met, as specified by Section 5.

The Project Manager shall be the single point of contact for the CO and COR and primary interface with the USCIS Program Manager. The Project Manager shall be employed by the prime contractor.

The contractor designated Program Manager position is considered key personnel and must meet the following qualifications:

▪ Minimum/General Experience: Five (5) years of overall program management experience obtained within the last ten (10) years, including supervision of employees supporting a program/contract. Program Management Professional (PMP) certification is desirable.

▪ Minimum Education/Credentials: Bachelor’s Degree in one (1) of the following disciplines: Program Management, Business or Public Administration, Information Systems, Engineering, Finance/Accounting, or related fields. USCIS will not accept a PMP certificate in lieu of the educational requirements.

7.2. SUBJECT MATTER EXPERT:

All personnel designated SME and billing at the SME rate are automatically designated key personnel.

The Contractor designated SMEs must meet the following qualifications:

▪ At least 7 years of experience in the field/subject in which the individual is designated as SME proven by professional experience and certifications applicable and or directly in that field/subject

7.3. TECHNICAL LEAD/TECHNICAL ARCHITECT:

The Contractor shall appoint a technical lead or a technical architect who shall be responsible for the technical implementation of the project, coordinate all development activity and be the ultimate responsible party to implement all technical tasks.

14 | P a g e Performance Work Statement

The Contractor designated Technical Lead/Technical Architect must meet the following qualifications:

• Minimum of three (3) years of experience in similar-scale OneStream implementations for federal agencies, as demonstrated by the candidate’s resume and supported by a verifiable government reference that the government may contact.

8. STAFF ADDITIONAL QUALIFICATIONS & EXPECTATIONS:

The contractor shall provide qualified personnel to perform all requirements specified in this PWS.

8.1. CONTINUITY OF SUPPORT:

The Contractor shall ensure required level of support for this requirement is maintained at all times. If for any reason the Contractor staffing levels are not maintained due to vacation, leave, appointments, etc., and replacement personnel are not provided, the Contractor shall provide e-mail notification to the COR prior to employee absence.

Otherwise, the Contractor shall provide a fully qualified replacement in accordance with the HSAR 3052.215-70 requirements outlined above.

8.2. EMPLOYEE CONDUCT:

Contractor’s employees shall comply with all applicable Government regulations, policies, and procedures (e.g., fire, safety, sanitation, environmental protection, security, “off limits” areas, wearing of parts of DHS uniforms, and possession of weapons) when visiting or working at Government facilities. The Contractor shall ensure contractor employees present a professional appearance at all times and that their conduct shall not reflect discredit on the United States or the DHS. The Program Manager shall ensure contractor employees understand and abide by DHS established rules, regulations and policies concerning safety and security.

8.3. EMPLOYEE IDENTIFICATION & BADGING:

Contractor employees visiting Government facilities shall wear an identification badge that, at a minimum, displays the contractor’s name, the employee’s photo, name, clearance-level and badge expiration date. Visiting contractor employees shall comply with all Government escort rules and requirements. All Contractor employees shall identify themselves as contractors when their status is not readily apparent and display all identification and visitor badges in plain view above the waist at all times.

All Contractor employees are required to have a suitability clearance. USCIS requires that Contractor employees be designated differently than USCIS employees. This may be

15 | P a g e Performance Work Statement accomplished via a different style or color ID badge provided by USCIS. ID badges are to be worn conspicuously at all times while contract employees are on-site at USCIS facilities.

Should a badge be lost, damaged, or destroyed, the contractor will immediately notify the local office COR upon discovery of the loss so that the badge can be deactivated and replaced by USCIS.

8.4. REMOVING EMPLOYEES FOR MISCONDUCT OR SECURITY REASONS:

The Government may, at its sole discretion (via the CO), direct the Contractor to remove any Contractor employee from DHS facilities for misconduct or security reasons. Removal does not relieve the Contractor of the responsibility to continue providing the services required under the contract. The CO will provide the Contractor with a written explanation to support any request to remove an employee.

In the event the Contractor terminates associated contract employees, or any contract employee resigns, the Contractor is obligated to inform the CO and COR in writing within five (5) business days of each occurrence.

9. OTHER APPLICABLE CONDITIONS:

9.1. PERIOD OF PERFORMANCE:

The following is the projected period of performance for this task order. Actual POP will be established after the Notice to Proceed is granted by the Contracting Officer.

Period Dates

Base 08/01/2026-07/31/2027

1st Option 08/01/2027-07/31/2028

2nd Option 08/01/2028-02/28/2029

***Period of Performance is an estimate.

9.2. PLACE OF PERFORMANCE:

The principal place of performance will be at the Contractor’s facility or a designated alternate workplace. The Contractor will be required to attend important meetings at the government facility in Camp Springs, MD, and may work onsite at the government office if preferred.

Once the system takes over operations from the legacy tool, the government expects on-site support and at least one support person working at the government facility.

9.3. HOURS OF OPERATION:

The Contractor shall schedule contractor personnel, ensuring adequate office coverage between the hours of 8:00 AM and 5:00 PM Eastern Standard Time (EST).

16 | P a g e Performance Work Statement

Contract employees shall not perform work at a Government site without a Government employee being present. Facility hours of operation are between the hours of 7:00 AM and 6:00 PM (EST) Monday through Friday. Work on Government Holidays and/or weekends, or before after operation hours is not permitted without prior approval from the CO or the COR and Government Program Manager. The Contractor shall not be allowed to work when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings.

Contract employees must be available via the organization’s primary business communication platform (currently Microsoft Teams) during duty hours.

9.4. GOVERNMENT HOLIDAYS:

A current list of Federal Government holidays is located at the following website:

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=2026

Also included are days specifically declared by an Executive Order from the President of the United States of America as a national holiday.

When such holiday falls on a Saturday, the preceding Friday will be considered a holiday.

When such holiday falls on a Sunday, the following Monday will be considered a holiday.

9.5. TRAVEL:

Contractor personnel shall not be reimbursed for local travel, which is defined as within a fifty (50) mile radius from the primary place of performance.

There might be a need for the contractor to travel to Vermont, where the Financial Operating Center is located. If the need arises and is authorized by the Government, travel will be reimbursable by the Government under this contract.

10. GOVERNMENT FURNISHED PROPERTY (GFP):

GFP will be provided to the Contractor for use in the performance of this contract in accordance with the FAR Part 45. The contractor must comply with clause 52.245-1, Government Property and clause FAR 52.245-9 Use and Charges, included in this order.

The CO authorizes the COR to assume the role of Property Administrator for this contract/order.

The GFP to be provided under this order is as follows:

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/#url=2026

17 | P a g e Performance Work Statement

DESCRIPTION

OF PROPERTY

QUANTITY UNIT OF

MEASURE

UNIT COST UNIQUE

ITEM

IDENTIFIER

Government

Issued Laptop After EOD

1 per person EA $2,000 Asset Tag

The property may not be used for any tasks outside the terms and conditions of this order. The Contractor bears full responsibility for all loss of this property, whether accidental or purposeful, at full replacement value. No personal or company owned storage devices, (thumb drives, DVDs, or CDs) will be used with the GFP.

The Contractor shall have a system of internal controls to manage GFP in its possession as set forth in FAR clause 52.245-1. Specifically, under FAR 52.245-1(f)(1)(iii), the Contractor shall create and maintain records of all Government property accountable to the contract, including Government-furnished, and contractor-acquired property. The property records shall enable a complete, current, auditable record of all transactions and shall, unless otherwise approved by the property administrator/COR, contain the ten elements listed in clause 52.245-1(f)(1)(iii)(A). Under FAR 52.245-1(f)(1)(iv), the Contractor shall periodically perform, record and disclose physical inventory results to the Property Administrator/COR. The frequency of inventory and reporting required by this contract is provided in the deliverables table below.

GOVERNMENT FURNISHED PROPERTY DELIVERABLES:

TYPE OF

REPORT

TIMEFRAME AND

FREQUENCY

GOVERNMENT RECEIVER

Initial

GFP

Report

Within ten (10) business days of initial receipt of

GFP upon contract commencement.

Contract identified CO, COR, and GFP mailbox:

USCISGovernmentFurnishedProperty@uscis.dhs.gov

Annual

Each year by August 30th

CO, COR & GFP Mailbox

Interim

Within (10) business days of any GFP inventory changes (i.e. when new property is

CO, COR & GFP Mailbox mailto:USCISGovernmentFurnishedProperty@uscis.dhs.gov

18 | P a g e Performance Work Statement issued or property is returned to the

Government), or as requested by the

CO.

Closing

Five (5) business days before contract ends or as otherwise directed by the CO.

CO, COR, & GFP Mailbox

11. PERFORMANCE STANDARDS & QUALITY ASSURANCE:

11.1. OVERVIEW:

The USCIS has specified performance standards in each task area related to processes that USCIS believes are critical to successful performance. These requirements and their associated performance standards define the work to be performed, although these may change over time. The USCIS established these performance requirements and associated standards after careful analysis of current operations based on historical performance against similar established standards.

USCIS requires the Contractor to conduct ongoing quality and process control and to effectively monitor performance continually. USCIS will measure performance against the published requirements and standards on an ongoing basis and will report the summarized results monthly.

11.2. QUALITY ASSURANCE SURVEILLANCE PROCEDURES:

The Quality Surveillance Procedures involve all planned and systematic actions necessary to provide adequate confidence that the services and resulting product from the contractor will satisfy the requirements. This program involves making sure that quality standards are met and includes a continuing evaluation of adequacy and effectiveness with a view toward the use of timely corrective and preventive measures where necessary. Quality Assurance Surveillance is the activity the Government utilizes to monitor the in-process product quality based upon the outcome of attribute inspection of product units. Quality Assurance Surveillance will be performed on all performance requirements to some extent.

The COR will inspect Contractor performance for compliance with the Performance Work Statement and Performance Requirements Summary (PRS) requirements throughout the

19 | P a g e Performance Work Statement contract period of performance. The Government intends to monitor the contractor’s performance by performing checks in accordance with the Performance Requirements Summary.

11.3. QUALITY CONTROL PLAN (QCP):

11.3.1. The contractor shall be responsible for exercising quality control of the processes called for in the PWS.

11.3.2. The contractor shall develop, maintain, and manage all quality control measures to ensure compliance with the standards of the performance requirements.

11.3.3. The contractor shall analyze trends and identify cost-saving approaches and productivity improvements to maintain performance while operating within budget constraints.

11.3.4. The contractor shall provide the COR with a quality assurance report no later than the tenth (10th) calendar day following the end of each month and attend quality review meetings with the COR.

11.3.5. The COR will review the Quality Assurance Monthly Report as part of the QCP. The COR will provide oversight and review performance standards based on the Acceptable Quality Level (AQL) below.

11.3.6. The COR and/or Government Program Manager will hold monthly quality assurance meetings to ensure performance standards are met.

GENERAL QUALITY MEASURES:

▪ Accuracy: Deliverables shall be accurate in presentation; technical content; and adherence to accepted elements of style. All deliverables shall conform to the appropriate DHS Directive and/or policy.

▪ Clarity: Deliverables shall be clear and concise and appropriate for the intended audience; plain language is preferred. Industry and technical terminology, acronyms, and complicated language should be avoided. All diagrams shall be easy to understand and relevant to the supporting narrative.

▪ File Editing: All text and diagrammatic files shall be editable by the Government using the Microsoft Office Suite of Products.

▪ Timeliness: Deliverables shall be submitted on or before the specified and/or agreed due date.

20 | P a g e Performance Work Statement

▪ Quality Assurance/Acceptance: The COR shall review, for completeness, draft and final work products and deliverables that the contractor submits and may return them to the contractor for correction. Absence of any comments by the COR shall not relieve the contractor of the responsibility for complying with the requirements of the contract.

11.4. CONTRACTOR DEFICIENCY REPORTS:

When the Contractor’s performance is unsatisfactory, the COR will prepare and submit a Contract Deficiency Report (CDR) to the CO for issuance. The Contractor shall reply to the COR in writing within fifteen (15) calendar days of notification and in accordance with instructions contained therein, giving the reasons for the unsatisfactory performance, corrective action taken, and procedures to preclude recurrence.

11.5. PERFORMANCE REQUIREMENTS SUMMARY (PRS):

PERFORMANCE STANDARDS:

This contract includes a PRS. The PRS plays an integral role in the administration of the contract. In addition to any applicable inspection clauses or other related terms and conditions contained in the contract, the PRS shall serve as a primary tool for inspection and acceptance of services as facilitated by the COR. Evaluation of the contractor’s overall performance shall be in accordance with the performance standards set forth in the PRS, and will be conducted by the COR. The PRS constitutes a material aspect of the contract and will not be changed or otherwise modified without prior written approval of the CO.

Performance standards define desired services. The Government performs surveillance to determine if the contractor exceeds, meets or does not meet those standards. The PRS, of the Performance Work Statement, includes performance standards. The Government shall use these standards to determine contractor performance and shall compare contractor performance to the stated AQL.

The PRS tables below sets forth the expected requirements of the contract. The PRS is not an exclusive remedy and inclusion of the PRS does not preclude the Government from using any other remedy available by law or contract terms, including reductions in payment in accordance with any clause for inspection of services. Changes to the standards will be made by bi-lateral agreement.

Performance Objective

Performance Standard(s)

Acceptable Quality Level (AQL)

Performance Measure/

Monitoring Method

Error (bug) free development products

UAT results in less that 10% of identified incompliances

>90% bug-free development products (releases)

UAT results

21 | P a g e Performance Work Statement

Performance Objective

Performance Standard(s)

Acceptable Quality Level (AQL)

Performance Measure/

Monitoring Method

Error (bug) free deployments

No emergency bug-fix deployments post release

0 emergency bug-fix deployments post release

Deployment records in CI/CD or otherwise documented

Accuracy of development activity representation in Jira and other program management tools

User stories in Agile and Kanban boards are fully documented and appropriately labeled in Jira.

Project-specific information is accurately populated

On-going work is fully documented and transparent – user stories are scored and qualified. Team capacity and velocity can be derived.

Backlog is maintained.

Government monitoring of Jira and other PM tools

Proactive identification of possible break-fix scenarios

Minimize impact of potential break of application functionality due to upgrades and releases

Number of functionality breaks - < 5 incidents per performance period

Proactive monitoring of platform upgrades and potential break of operating tools and applications

Adherence to development schedule

Fully planned sprints that utilizes the team’s development capacity

95% completion of user stories in a planned sprint, unless re-directed by the government

Jira records and monthly velocity/ burndown reports

Break-fix O&M resolution

Timely resolution of production application functionality outage

Restore impacted functionality - < 24h

Time between functionality break to resolution.

Does not apply if caused by network or platform-related outage

Cooperation with internal and external teams

Good faith cooperation with other contractor teams to accomplish OCFO work

0 incidents of non-cooperation.

Government surveillance

Customer Service

OCFO product owners’ satisfaction with delivered functionality

95% CFO divisions’ satisfactions with delivered functionality/products

TPMO surveys of OCFO staff

12. DELIVERABLES:

22 | P a g e Performance Work Statement

The Contractor shall provide all deliverables to the COR and Technical PMO Program Manager, as specified in the Performance Work Statement, for review and acceptance.

The Contractor shall provide the deliverables in electronic format to the maximum extent possible. All deliverables developed by the Contractor shall become the property of the Government, shall not contain proprietary markings, and shall be delivered with unlimited rights as per FAR 52.227-14 – Rights in Data-General. The Government will have thirty (30) calendar days to review and provide comments to the Contractor prior to acceptance of all deliverables. The Contractor must then respond as described below within fourteen (14) calendar days after receipt of Government comments.

DELIVERABLE DUE DATE PERFORMANCE WORK

STATEMENT REFERENCE

Code/configuration workflow/process flow/data models/dashboards, etc.

In accordance with scheduled SCRUM/Kanban deployments

Section 5

System documentation (Agile track)

In accordance with scheduled SCRUM/Kanban deployments

Section 5

Automated test scripts or test scenarios

In accordance with scheduled SCRUM/Kanban deployments

Section 5

Documentation in Jira and other provided project management tools

In accordance with development timelines

Section 5

Operations and Maintenance Records

As occurring Section 5

Standard Operating Procedures

As required Section 5

Program Roadmap in the tool required by the government

Monthly updates or as required

Section 5

Risk Registry in the format directed by the government

Weekly Section 5

Weekly Status Meeting Weekly Status Meeting is to be coordinated through the Government PM for time/day to remain consistent with agency requirements

Section 5

Monthly Status Report Monthly in the format specified by the government

Section 5

Briefings/Documents As required Section 5

Task Order Kick-off Meeting (Post Award Conference)

Within 10 business days after Task Order award

23 | P a g e Performance Work Statement

DELIVERABLE DUE DATE PERFORMANCE WORK

STATEMENT REFERENCE

Technical Kick-off Meeting Within 15 business days

Program meeting materials As required Section 5

Key Personnel Resume 3 business days after task order award and at the time of any proposed replacement

Section 7

Separation Notification Within ten (10) days of each occurrence

Section 7

Telework Plan 3 business days prior to the Task Order-Award Kickoff Meeting

Section 9.2

Quality Control Plan

Within 30 calendar days

Section 11.3