Attachment 1-EATS_PWS_Draft_Rev_3.pdf

Department of Treasury Office of the Chief Information Officer (OCIO)

Enterprise Applications (Enterprise Apps) Enterprise Applications Technical Services (EATS)

Performance Work Statement (PWS)

April 2, 2024

Table of Contents I. Introduction II. Background IV. Enterprise Applications Organizational Structure V. HRConnect Profile VI. Current EATS Technology Stack VII. Statement of Need VIII. Scope IX. Task Area X. Key Personnel XI. Deliverables and Deliverables Schedule XII. Quality Management XIII. Risk Management XIV. Task Order Management

a. Request for Task Order Proposals (RFTOP)

b. Task Order Deliverables

c. Performance Level Agreement (PLA)

d. Service Level Agreements (SLA)

XV. Enterprise Applications Technical Services (EATS) BPA Overview

a. GSA Schedule

b. Authority

c. Order Period of Performance

d. BPA Volume and Estimated Total Value

e. Order Type

XVI. Contract Administration

a. Pricing Terms

b. Period of Performance

c. Authorized Ordering Officials

d. Designation and Technical Direction

e. Ordering Procedures

f. BPA Orders

g. Unauthorized Work

h. Invoicing Notification and Support Documentation

i. Advertisements, Publicizing Awards and News Releases

j. Cause for Termination

k. Identification of Contractor Personnel

l. Identification/ Badges

m. Communications

n. Personnel Removal and Replacement

o. Material Handling Fee

p. Place of Performance

q. Performance at Government Sites

r. Contractor Facilities

s. Government Furnished Equipment

t. Travel

u. Hours of Operation

v. Federal Government Holidays

XVII. Section 508 XVIII. Contract Clauses and Provisions XIX. Security and Privacy Requirements

Security Categorization

I. Introduction

Enterprise Applications (Enterprise Apps) within the Office of the Chief Information Officer (OCIO) of the United States Department of the Treasury provides leadership to the Department of Treasury and its Bureaus in all areas of information and technology management and supports Treasury's mission by implementing strategies that improve the efficiency and performance of Treasury information technology (IT) systems and business processes. OCIO has Department-wide responsibility for directing and developing Treasury's IT strategy, managing IT investments, and leading key technology initiatives. Enterprise Apps provides information technology solutions through shared and scalable products, platforms, and services.

II. Background

Enterprise Apps operates as a Shared Service Provider (SSP). It offers a broad spectrum of IT solutions and associated program responsibilities to Treasury and several Federal agencies to provide government‐wide, modern, standardized, and interoperable IT solutions. The Enterprise Applications division offers services through the Enterprise Applications Technical Services (EATS) BPA. As the EATS solution grows and matures, it has expanded its client portfolio and diversified its service offerings by introducing additional programs. A description of each program within Enterprise Applications is below:

Programs

● HRConnect (HRC) -The HRConnect Product Suite, which is built on Oracle's Peoplesoft platform, is offered as an Office of Personnel Management (OPM) officially designated Human Resources Line of Business (HRLOB), Shared Service Center (SSC). OPM’s designation enables Treasury to offer interoperable, portable, and scalable HR/payroll solutions across the federal space. While the HRConnect Program resides and is managed within the Department of the Treasury Office of the Chief Information Officer, its clients come from all Federal Government segments.

● Digital Services (DIG) – Digital Services provides public-facing, extranet, and intranet web solutions via the Workplace.gov Community Cloud (WC2) shared services offering to give the US Department of the Treasury with Software-As-A-Service (SaaS), Platform-As-A-Service (PaaS), and various professional services including consulting on business solutions. The WC2 platform addresses the ability to provide agile, cost-effective, and secure hosting services for internal, public, and extranet applications at the FISMA Moderate / FedRAMP level. The platform offers standard management and security services built by Commercial Cloud Service Providers (CCSP). The provided services include production and non-production environments supporting use case scenarios such as public websites and application hosting, Extranet services, development & test enclaves, and Customer Relationship Management (CRM). Digital Services strongly focuses on low-code/no-code platforms, emphasizing Salesforce and ServiceNow offerings.

● Talent Management Solutions (TMS) -The Talent Management Solutions (TMS) program provides a suite of software products utilized by federal agencies that address non-core human resource needs across the talent management life cycle. TMS administers talent management products such as Integrated Talent Management (ITM), USA Staffing and USA Hire, and training support services.

● Enterprise Content Management (ECM) – Enterprise Content Management is a strategy, architectural framework, and tools and technologies designed to help customers improve content management, document management, and intranet portals. ECM is governed by the ECM Customer Advisory Board (CAB) as a product suite. The ECM CAB is comprised of senior business executives from each Bureau or office within the Department of Treasury. ECM provides Treasury-wide solutions to meet collaboration and other customer requirements and is designated as the preferred Treasury content/collaboration platform. Many services offered within ECM are scalable and anticipated to be available to Federal entities across the public sector through the Treasury Shared Service Division. ECM is based on Microsoft SharePoint, offering Platform as a Service (PaaS) and Software as a Service (SaaS) solutions. ECM is also hosted in the Microsoft Azure environment.

● Enterprise Data Management (EDM) – Enterprise Data Management institutes and fosters ongoing methodology and technology solutions to help analysts use enterprise data assets to measure, manage and influence improved organizational performance. EDM’s Data and Analytics (DnA) system platform organizes data from disparate systems to provide consolidated analysis and reporting for its customers. The Workforce Analytics module leverages the DnA platform to deliver value in the Human Capital domain and is fully integrated with the HR Connect product suite. EDM provides solutions to Treasury-wide and non-Treasury customers.

EDM is hosted in Microsoft's Azure environment and utilizes Microsoft Business Intelligence tools.

● Enterprise Application Cybersecurity (EAC) – EAC offers cybersecurity support for customer systems and applications. EAC’s offerings include Security Assessment and Authorization (SA&A) Package Development, Full & Partial Security Assessments, Vulnerability Management, Security Engineering, and Penetration Testing.

III. Enterprise Applications Overview: Portfolio – At a Glance1

HR Line of Business (LoB)

• Core Human Capital management system, talent acquisition, and a payroll interface

• Federal Shared; 31 customers, 87 Federal staff include IHRTT (7), ACIO, and CSM

Talent Management Solutions (TMS)

• Integrated Talent Management, Training Solutions, USA Staffing (recruiting and onboarding)

• Treasury Shared and Federal Shared; 20 Federal staff.

Enterprise Data Management (EDM)

• Data Warehouse Platform, Data Insight Portal, Analytics Gateway, and Data Support Services

• Treasury Shared and Federal Shared; 14 Federal staff.

Enterprise Content Management (ECM)

• PaaS and SaaS Solutions (e.g. Treasury Intranet, collaboration sites, clearance tracking and case management)

• Treasury Shared; 22 Federal staff include IA CFIUS (5)

Digital Services

• Web design hosting, and content delivery platform, low code application development and O&M

• Treasury Shared; 35 Federal staff include IHRITT (2)

Departmental Offices (DO)

• 40 Mission Specific IT services, Applications Development and Operation

• Departmental Offices: Four (4) CTAS Federal staff that are distributed across HRC (1), ECM

(1) & Digital (2)

Cybersecurity Enhancement Account (CEA)

• Strategic mitigation of cybersecurity risks through a centralized program with Department-wide impact (e.g., GRC or SecOps)

• Treasury Shared (all Treasury bureaus); 14 Federal staff.

1 Current state and subject to change

IV. Enterprise Applications Organizational Structure

The organization chart depicted below represents the current overarching composition of Enterprise Applications. The Contractor will work within the structure to support the Enterprise Applications Technical Services BPA.

Figure 1

V. HRConnect Profile

Components Description User Base 200,000+ users representing over 38 Federal agencies Hosting Oracle Gov Cloud Peoplesoft Application Version Peoplesoft 9.2

PUM Image 45 Peopletools 8.60

Database Oracle 19c Third-Party Integrations National Finance Center (NFC), USA Access, USA Staffing HR Connect Features ● Core HR Processing (HR-Personnel Action

Processing, Bi-Directional Payroll Interface, Payroll Administration, Talent Acquisition, Onboarding, Integrated Talent Management).

● Configurable Workflows

● Employee, Manager and HR Self-Service

● Mass Processing

● Person of Interest

● Separation Employee/ Contractor Clearance

● Real-Time Reporting for Managers and HR

● Contractor Management

● Positions Budget Management

● Contract Management

● Outside Employment

VI. Current EATS Technology Stack

ID System Platform S-1 HRConnect Hosting Oracle Cloud CSP S-2 HRConnect Platform Oracle Peoplesoft S-3 PeopleTools Oracle S-4 USA Staffing OPM CSP S-5 Enterprise Content Management SharePoint (Azure) CSP S-6 Enterprise Data Management Microsoft (Azure) CSP S-7 Treasury Application and Platform Services- High AWS CSP S-8 Treasury Application and Platform Services- Moderate AWS CSP S-9 Treasury Salesforce General Support System Salesforce CSP S-10 Treasury/ServiceNow General Support System ServiceNow CSP S-11 Treasury/Box.com Box CSP S-12 Enterprise Service Bus MuleSoft CSP

S-13 Dynamics 365 Dynamics 365 CSP S-14 FOAI Express AWS CSP S-15 Acquia Public Platform Acquia Fed RAMP CSP S-16 Workforce Analytics MS SQL Server 2016 S-17 Integrated Talent Management (ITM) SAP SuccessFactors

The EATS technology stack represents the current technologies that support various applications under EATS. This list is subject to change, and all applications may not need support under this

BPA.

VII. Statement of Need

Enterprise Applications needs a broad range of programs and technical services to support its ongoing Enterprise Applications Technical Services (EATS). EATS includes managing, developing, delivering, and supporting various IT Projects, which provide IT Enterprise services across Treasury and external agencies. EATS serves a large and diverse user base; these services also require exceptional and timely customer-centric support and delivery.

This acquisition aims to award a Blanket Purchase Agreement (BPA) for Contractor resources with IT service capabilities and experiences capable of successfully satisfying Treasury's Shared Services by providing state-of-the-art industry support to stakeholders, operations, and maintenance, future systems development, enhancements, and deployments, with a better understanding of industry capabilities, potential sources, firm practices and changes in technology relevant to our operating business.

VIII. Scope

Enterprise Applications Technical Services (EATS) is a complex service offering designed to offer its customers leading-edge service delivery in a competitive marketplace. Enterprise Applications seeks support of the current functional and technical baseline and contemplates changes to its services concepts approach. To foster a cohesive environment, projects are conducted collaboratively with Federal government employees and other vendors with access to EATS to make changes/enhancements.

EATS provides mission-critical services and support for new and current applications for Treasury and its customers. Applications under EATS may interface with systems within Treasury and at other Federal agencies. Treasury seeks various IT services to support current and future EATS initiatives.

The scope of work under this BPA is categorized as follows:

Task Area Category

1.0 Program and Project Management

2.0 Application Development Services

3.0 Information Technology Operations and Maintenance (O&M)

4.0 Functional and Business Analysis Services

5.0 Quality Assurance and Test Support Services

6.0 Help Desk Support Services

7.0 Customer Implementation and Deployments

8.0 Data Management and Analytics

9.0 Additional Support Services

10.0 New and Evolving Technologies

11.0 Transition Support

IX. Task Area

Enterprise Applications require a systematic program and project management methodology with all IT support activities under this BPA. The methods shall use frameworks based on the Project Management Body of Knowledge (PMBOK), Capability Maturity Model Integration (CMMI), Agile, and International Organization of Standard (ISO), and/or other industry-recognized Program and Project Management methodologies to manage the overall work effort under this BPA and all awarded task orders for providing project planning and management.

1.1 Ensure program and project management fundamentals such as cost, schedule, and performance are effectively and appropriately managed, and project risks are actively identified, mitigated, and documented across all task orders awarded under this BPA.

1.2 Monitor legislative and policy changes, perform regulatory and legislative policy and standards research, and provide assessments to the Government detailing the impact on designated programs and IT products.

1.3 Work with leadership and other stakeholders to provide data and metrics for reporting on applications within the EATS enterprise. Reporting may include using Key Performance Indicators (KPIs), dashboards, charts, and graphs.

1.4 As requested by the Treasury, participate in, or facilitate, technical reviews, Program Management Reviews (PMRs), or business planning/governance meetings to establish and communicate critical project decisions related to functional, non-functional, and architecture areas, including obtaining Treasury approval of planned and completed customizations, functional enhancements, and architectural decisions.

1.5 Provide Level-of-Effort (LOE) estimations for new Task orders with pricing aligninment. LOE’s shall be reasonable and defined in good faith. If warranted, evaluation of previous Task Orders of similar work may be completed to reduce potential for over and under estimating.

1.6 Provide and review with the Treasury, contractor project metrics that report on the Contractor’s accomplishment of Service Level Agreements (SLRs) and other measurements (e.g., deliverables associated with each project phase, subproject, task, activity, critical and non-critical milestones).

1.7 Monitor all work and coordinate with designated government representatives and other vendors as required.

1.8 Conduct project status meetings, and/or provide Status Reports based a mutually agreed upon frequency. This will be conducted in accordance with the project communications plan with appropriate contractor resources, the Treasury representative and other key Treasury participants as required by the designated Treasury representative.

1.9 Coordinate services, activities and dependencies and serve as the single point of contact/interface to the Treasury including coordinating Contractor, Third Party and Treasury resources ensuring the on-time delivery of tested/quality-checked deliverables as defined in the project plan.

1.10 Create and maintain required documentation, may include written project status reports to the designated Treasury representative on a mutually agreed upon frequency, including status updates of applicable items in the project plan (e.g., the project schedule), in a format approved by Treasury.

1.11 Comply with all Treasury Security requirements in Section Q. This includes mandatory trainings, contractor onboarding and security requirements.

2.0 Application Development Services

IT development and support services, including modernization and enhancements, to various software applications for all existing, planned, and future systems that support various organizational and cross-organizational functions.

This may include capturing requirements; coordinating with appropriate Federal and other contractor personnel regarding enterprise architecture; identifying functional, security, and performance requirements; developing logical and physical database models; performing coding, testing, quality assurance, design, and program documentation; implementation; and maintaining interoperability between future and existing hardware and software applications.

Software applications include, but are not limited to, web applications, Software as a Service (SaaS), Commercial-Off-The-Shelf (COTS) integration, and custom applications development.

2.1 Support all phases of the Software Development Life Cycle (SDLC) process to build and manage applications. This includes planning, analysis, design, development, testing, implementation, operations, and maintenance.

2.2 Understand various project management methodologies to plan, manage, execute, and provide status of application development projects and activities.

2.3 Demonstrate knowledge for IT solutions using an agile approach for project planning, product roadmap creation, release planning, sprint planning, daily scrum/stand-ups, sprint review and retrospective.

2.4 Create, edit, and properly maintain any necessary documentation from the application development process.

2.5 Adhere to Treasury standard design and development policies and procedures.

3.0 Information Technology Operations and Maintenance (O&M)

Deliver system and infrastructure capabilities that scale to meet enterprise demand, while utilizing innovative industry best practices and technologies that maximize efficiencies and cost savings. Responsible for developing and maintaining IT software and systems to support availability, facilitating, managing, and monitoring the integration, interoperability, and synchronization of enterprise-wide systems and infrastructure solutions and services is paramount.

Services may include but are not limited to activities related to planning and implementing information technology infrastructures; network administration which may consist of network access and security; server management; application system administration; user support, database administration; hosting application and ancillary software on servers.

3.1 Day-to-day operational processing and fixes in a manner which meets the defined reliability requirements of the users, system uptime, and customer needs.

3.2 Modifying and enhancing existing applications as approved to accommodate hardware, software, requirements change, or software problems.

3.3 Test and install application upgrades and patches in a timely manner consistent with change control requirements.

3.4 Manage, monitor, and maintain databases instances in compliance with industry best practices and standards. Database administration services include but are not limited to database monitoring and troubleshooting, tuning, space management, refreshes, exports, backups, patch analysis and application, and capacity planning.

3.5 Monitor system and problem correction, backup and recovery, performance monitoring and tuning, system modification, and production emergency support. The Contractor is responsible for architecture, key interfaces, ports, protocols, services and application, configuration, hardware/software, and security controls.

3.6 Work collaboratively with the SaaS and PaaS providers and Treasury government teams to troubleshoot and remediate service outages and problems, including maintaining networking engineering and network security expertise to deploy, maintain, troubleshoot, document and monitor.

3.7 Experience supporting hybrid infrastructures (onsite and cloud) by managing, migrating, and monitoring changes with system/application or other IT to ensure that the system/application or other technological solution meets ongoing functional and non-functional needs.

3.8 Experience with rapidly modernizing and migrating on-premises, federal applications to FedRAMP certified cloud service providers. Contractors should demonstrate vendor best practices, risk mitigation strategies, lessons learned, and methodologies for rapid migration and cutovers from legacy/original environments

3.0 Information Technology Operations and Maintenance (O&M)

with minimal impact to operational availability requirements.

4.0 Functional and Business Analysis Support

Responsibilities include, but are not limited to, consulting with and gathering customer requirements, analyzing IT requirements necessary to meet user need, plan and design secure, cost-effective, user-centric IT solutions consistent with Federal and Department of Treasury guidelines and standards, identify problems, facilitation, and execution of requirements while demonstrating how a proposed methodology can provide a repeatable framework that the Government can expect to apply for each task order under this BPA.

4.1 Follow and apply industry-standard requirements management practices collaboratively with the Federal government employees and other vendors with access to make changes/enhancements to the system.

4.2 Develop, update, and track detailed functional and non-functional specifics reflected in each task order, tracking all changes that may occur during the project's lifecycle.

4.3 Prepare collaborative functional and technical design documents, including Business Requirement Documents (BRD) and Change Requests (CR) for each application O&M enhancement approved by the Government.

Apply processes and practices to ensure developed products reach an established quality threshold.

The main goal of QA services is to increase the efficiency of development processes by constantly improving on them. QA and software testing services ensure software meets requirements and user expectations.

508 Testing

5.1 Comply with the following technical standards of the Section 508 Accessibility testing. Support shall be provided while following DHS Trusted Tester standards and procedures. Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (PL 105-220), requires that when Federal agencies develop, procure, maintain, or use information and communication technology (ICT), it shall be accessible to people with disabilities.

5.2 Provide justifiable documentation when Section 508 Accessibility standards cannot be met.

Software Testing

5.3 Conduct testing and quality assurance across various activities, supporting all phases of application development: static, dynamic, unit, integration, system, regression, performance, and acceptance testing.

5.4 Provide defect and regulatory test support while following established QA processes following Enterprise Applications approved change management procedures.

5.0 Quality Assurance and Test Support Services

6.0 Help Desk Support Services

Providing support on EATS products and services to Treasury and its customers. Respond and resolve customers inquires. Focus is on customer satisfaction, issue management and tracking, and resolution.

6.1 Support Tier-2 helpdesk support services for customer issues for EATS applications, escalating as appropriate to Tier-3 support.

6.2 Support activities needed for the smooth maintenance, operation, and continued service of the systems.

6.3 Knowledge of customer service best practices and federal ethics and principles is expected.

6.4 Provide KPI’s and metrics to measure and monitor help desk service delivery and process improvements.

7.0 Customer Implementation and Deployments

Managing the process to integrate new customers into the EATS landscape. This includes understating the goal and purpose, providing analysis, understanding of the EATS model for implementation and integration in the existing shared services infrastructure.

7.1 Capability to support new customer deployments, this may include project management support, requirements gathering, development, testing, and monitoring, and change management activities for the Enterprise Applications products and services being deployed to customers.

7.2 Manage and execute system release including releasing and managing user acceptance testing, systems deployments, and post-deployment support.

8.0 Data Management, Analysis, and Analytics

Support data analytics activities utilizing mathematics, statistics, computer science, and application-specific knowledge to gather, make, and communicate principled conclusions from data and develop various business intelligence tools and applications to support Enterprise Applications' data science and analytics needs.

8.1 Provide an analytics framework to support a decision management that enables Data Analysis, Modeling, Predictive Analytics, Test and Learn, and implementing initiatives for innovations and services that help critical businesses process and risk management strategies

8.2 Employ and utilize technical data analytics methodologies, processes, architectures, and technologies to support the understanding, problem solving, issue identification, and decision making for Treasury and their customers.

9.0 Additional Support Services

Provide Enterprise Applications support services across the division to execute core program objectives and maintain high customer satisfaction.

Training

9.1 The Contractor shall provide training delivery, and training materials support using many mediums. All materials shall be delivered to the Government with the ability to address and make updates as requested by the Government and be utilized in the Government approved training management system.

Payroll Support

9.2 The Contractor shall provide payroll support services for HRConnect and/or National

Finance Center with an understanding of Federal payroll and human resource legislation changes and regulations. Payroll support services may include conducting research, gathering information, resolving service issues, presenting recommendations, and developing payroll requirements for regulation, legislation, or integration changes.

Advisory Services (Consultation)

9.3 The Contractor shall provide advisory and consulting assistance focusing on using and implementing existing and emerging best practices, processes, and technologies on various activities related to the EATS landscape.

Areas may include but are not limited to technology consulting, data call support, technical documentation support, strategic planning, technical guidance, executive management, and administrative support, regulatory and compliance advisory, and ad-hoc project management.

9.0 Additional Support Services

9.4 The Contractor shall prepare executive briefings, including status updates for senior leadership and governance committees, and coordinate communications and outcomes from EATS stakeholders and other Enterprise Applications programs.

Change Management

9.5 Execute program and project level change management providing specific strategies, plans, actions, and steps in alignment with a project deployment.

9.6 To streamline and meet customers' changing needs, recommend improvements to existing products or services.

10.0 New and Evolving Technologies

Support Enterprise Applications by providing sound guidance and advisement in emerging technologies, including information technology, robotics, and artificial intelligence. New technological fields may result from the technological convergence of different systems evolving towards similar goals.

10.1 Serve as an advisor and technical consultant to design, build, and implement solutions on various EATS landscapes.

10.2 Provide guidance for new projects and products to ensure best practices are implemented and that projects are developed in compliance with Treasury standards and security.

10.3 Plan and design healthy and sustainable architecture for EATS landscape.

10.4 Conduct research and make recommendations on innovative technology products and services that support or enhance EATS.

10.5 Create, maintain, and update applicable documentation and reports.

Build and maintain a strong knowledge management strategy to identify, capture, and transfer knowledge for the entire BPA and associated task orders. This should include but not limited to knowledge of Treasury Shared Services operating model, Enterprise Applications organizational structure, tech stacks, integrations, hosting platforms, project details, risk and challenges, deployment procedures, and any other technical information relevant to the continued support of the programs.

Transition In

11.1 The performance base year includes transition-in activities for 90 days. The transition-in is to perform all actions necessary to be prepared to assume full responsibility for the contract requirements. Therefore, any activities not explicitly identified in this plan are included in the task order scope if they meet this definition.

Transition Out

11.2 The period of performance for this option shall be for 90 days and not expected to exceed 90 days unless otherwise contractually defined. The incumbent Contractor shall work proactively with Enterprise Applications and any other organizational stakeholders designated by Treasury to ensure a smooth, orderly, cooperative transition of services to a new Contractor.

11.3 The incumbent Contractor shall complete all transition-related tasks and activities and submit a phase-out plan describing the Contractors' methodology, processes, and phase-out transition activities. The incumbent Contractor shall negotiate the delivery date and plan content for the phase-out plans as soon as possible after notification of the new Contractor's transition completion date.

X. Key Personnel

Particular skilled experienced professional and/or technical personnel are essential for successful contractor accomplishment of the work to be performed under the BPA. These are defined as Key Personnel and those persons whose resumes shall be submitted for evaluation.

The key personnel cited below are considered essential to the work being performed under this BPA. Experience must consist of working on large scale IT programs and enterprise systems, preferably in a shared service or dispersed organizational environment, contract value at least $10 million a year.

The Contractor shall assign to this contract the following key personnel to the identified positions/functions:

Role Description Program Manager ● Serves as the primary liaison between the Contractor and the

Government.

● Responsible for the overall management and coordination of the contract and serves as the central point of contact for the Government.

● Works with relevant stakeholders to regularly identify, monitor, and mitigate risks.

● Interfaces with the customer and other relevant stakeholders to meet their needs.

● If applicable, manages subcontractors.

● Guides direct reports and the program support staff for all technical and administrative matters.

● Requires Project Management Professional (PMP) or Agile Project

Management certification.

a. If this individual leaves the Contractor's employ or are reassigned to other programs, the Contractor shall notify the Contracting Officer 15 days in advance and shall submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on the program. The Contractor shall make no diversion or replacement without the Contracting Officer's written consent.

b. The Contractor shall not substitute key personnel identified above unless the substitution is necessitated by illness, death, or termination of employment. The Contractor shall notify the Contracting Officer and the Contracting Officer Representative within one (1) business day after these events and provide the information required by paragraph (c) below at least 10 working days before making any permanent substitutions. Any substitution not necessitated by illness, death, or termination of employment requires a 15 days’ notice and shall submit justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on the program.

c. The Contractor shall provide a detailed explanation of the circumstances necessitating any proposed substitution, provide resume(s) for the proposed substitute(s), and provide any additional information requested by the CO. Proposed substitute(s) must possess qualifications comparable or superior to the original key person, as well as satisfying any minimum standards. The CO will notify the Contractor within five (5) working days after receipt of all required information of the decision regarding acceptability of substitutions. The Contracting Officer will modify this clause to reflect any approved key personnel changes.

d. Additional key personnel can vary by Task Order and will be defined at the Task Order level.

XI. Deliverables and Deliverables Schedule

Work products, software, hard-copy, and electronic documents including data and any potential source code including any other products to support requirements or developed by the Contractor while working on this contract are the sole property of the United States Government.

Enterprise Applications retains the right to acquire new systems and enhancements to existing systems, to ensure the best value for the Government. All licenses, source codes (except COTS), products and ownership are the Government’s at the end of each task order under this BPA. The Contractor shall have no rights of ownership.

Additional deliverables can vary by Task Order and will be defined at the Task Order level.

Deliverables under this BPA are as follows:

Deliverable # A-0001 Deliverable Title

HRC BPA Report (Active)

Description This report at a minimum shall be organized as follows:

1. Task Order numbers (if awarded any)

2. Type (FPP, LH, Hybrid)

3. Prime labor $

4. Prime labor %

5. Prime ODC $

6. Sub-contractor Labor $

7. Sub-contractor labor %

8. TO total ceiling

9. POP Start

10. POP End

11. Total amount invoiced.

12. Task Order close out date

13. Prime total labor to date $ & %

14. Sub-Contractor total labor to date $ & %

The BPA report is not required if no task orders have been awarded to the BPA awardee.

Deliverable Due Date

This report is due by the first day of each quarter (Oct 1, Jan 1, April 1, July 1).

Submitted To Contracting Officer and the COR

Deliverable # A-0002

Deliverable Title

Program Management Plan- Shall describe the Contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of projects, tasks and activities required under this contract.

Description The Program Management Plan shall include, at a minimum:

1. The Contractor organizational structure identifying program leadership and personnel and the assignment of functions, tasks, duties, and responsibilities.

2. The alignment of the Contractor’s team to the Enterprise Applications organizational structure.

3. The program management methodology established for reporting contractual projects, activities and tasks and associated review timelines.

4. The program management processes and controls the Contractor will manage the Contractor's operations and any procedures in place for corporate risk management.

If applicable, the master subcontracting plan including all work packages expected to be completed by subcontract personnel.

Deliverable Due Date

30 calendar days after BPA award and updated as needed to ensure currency

Submitted To COR and Government Technical Program Manager

Deliverable # A-0003 Deliverable Master Resource Report- The Contractor shall deliver a Master Resource Roster containing a complete list of each resource working under all task orders under this BPA.

Description Report shall contain the following information:

a. Company name,

b. Contractor PM,

c. HRC BPA COR,

d. Program (HRC, ITM, etc..)

e. Task Order #

f. Resource Legal name (Last Name, First Name in separate columns),

g. AKA name ( if applicable),

h. Labor category,

i. Start date,

j. Expected end date,

k. Labor rate,

l. Resource location,

m. Government Project Leader,

n. COR assigned to the Task Order,

o. Footer: Date and Version #.

Deliverable Due Date

Initial resources report due 60 calendar days after BPA award and 30 days after Task Orders.

Ongoing report- Updated as needed to ensure currency, updated monthly, or upon request whichever occurs first.

Format Excel Submitted To COR

Deliverable # A-0005 Deliverable Transition Plans Description Transition plans for both incoming and outgoing shall include the following:

● Duties & responsibilities outlining the main tasks, so the workflow experiences as few interruptions as possible.

● Outstanding projects.

● Upcoming deadlines.

● Key contacts.

● List of resources.

Deliverable Due Date

Within 90 days

Deliverable # A-0004 Deliverable Treasury Annual Trainings Description All contractors are required to adhere to Treasury’s annual trainings Deliverable Due Date

Varies, will be communicated by the COR or authorized official at least 60 days in advance.

All Contractor deliverables shall remain categorized as "Official Use Only.” The release of any portion must be authorized in writing by the Government.

Final inspection and acceptance of deliverables can be conducted remotely and /or at the Government site (on-site at 1750 Pennsylvania Avenue, 13th floor, Washington, DC). Deliverables are only final once reviewed and approved by the COR or Government Technical Operations Manager.

The Contractor shall proactively inform the designated government Project Managers, Task Order COR and BPA COR of any issues, problems and recommendations that should be addressed to effectively accomplish task order goals.

Recommendations for actions that need to be taken by Treasury staff, or other contractors, shall be clearly defined and communicated to the responsible party and the government, and have identified dates for completion.

XII. Quality Management

Quality Management can vary among task orders and will be defined at the task order level.

XIII. Risk Management

Risk Management can vary among task orders and will be defined at the task order level.

XIV. Task Order Management

a. Request for Task Order Proposals (RFTOP)

When a requirement has been identified, the Task Order PWS shall be submitted to the CO by the HRC program office. After REVIEW AND APPROVAL, the RFTOP and PWS shall be distributed to the BPA awardee. If the awardee has no intention to respond with a proposal, the awardee must notify the CO and COR within 3 business days of receiving the RFTOP. All proposal responses shall include a price quote and technical proposal. The CO shall specify the due date of proposals.

b. Task Order Deliverables

Deliverables can vary among task orders and will be defined at the task order level. Deliverables may include but are not limited to:

● Task Order Status Report

● Invoice Backup and Financial

Tracking

● Work Breakdown Structure (WBS)

● Monthly Management Reports

● Project Schedules

● Quality Management Plan

● Release Management Plan

● Resource Management Plan

● Risk Management Plan

● Risk Register

● Service Level Agreements Metric

Reports

● Time and Burn Report

● Resource Roster

● Task Order Closeout Report

For each task order issued, the Contractor shall prepare a Management Plan describing the technical approach, organizational resources, risk management and other management controls to meet the cost, performance, and schedule requirements throughout task order execution.

c. Performance Level Agreement (PLA)

Performance Level Agreements (PLA) can vary among task orders and will be defined at the task order level. The Contractor shall adhere to Task Order PLA and Government’s Quality Assurance Surveillance Plan (QASP) to monitor the Contractor’s performance. The QASP will provide oversight to ensure that service levels reach and maintain the required levels for performance of this contract. Further, the QASP provides the COR with a proactive way to avoid unacceptable or deficient performance and gives verifiable input to the required Past Performance Information Assessments. The QASP is a living document and may be updated by the Government as necessary.

Any updates to the QASP will be provided to the Contractor.

d. Service Level Agreements (SLA)

Service Level Agreements (SLA) can vary among task orders and will be defined at the task order level. The Contractor shall adhere to SLAs and Government’s Quality Assurance Surveillance Plan (QASP) to monitor the Contractor’s performance. The QASP will provide oversight to ensure that service levels reach and maintain the required levels for performance of this contract. Further, the QASP provides the COR with a proactive way to avoid unacceptable or deficient performance and gives verifiable input to the required Past Performance Information Assessments. The QASP is a living document and may be updated by the Government as necessary. Any updates to the QASP will be provided to the Contractor.

Deliverables that meet the standards outlined in the PLA table and are accepted by the COR/ITM PMO will result in a positive contractor performance assessment. Deliverables that meet those standards and are accepted by the COR/HRC PMO will result in a positive contractor performance assessment. The Contractor shall perform any necessary rework at the Contractor's expense.

XV. Enterprise Applications Technical Services (EATS) BPA Overview

a. GSA Schedule

At the time of quote submission for this BPA and before the exercise of BPA options years, the Quoters must have a valid GSA Schedule that covers the appropriate performance year of the BPA.

Also, the current Schedule must be posted at GSA in accordance with GSA terms and conditions.

Please comply to avoid the Quoters being ineligible for award or in the case of options the order/BPA may not be renewed. The Quoters shall notify the Contracting Officer, no later than 12 months before its GSA schedule expiration, whether they will establish a new GSA schedule, extend its current schedule, or establish a new schedule with similar scope.

The terms and conditions of the GSA Schedule do not supersede the pricing and terms conditions outlined in the resulting BPA. In the event a specific term and/or condition of the BPA conflicts with a particular term and/or condition of the GSA, then the specific terms and conditions of the resulting BPA will prevail. Unless otherwise mutually agreed to in writing by the Government and the Contractor, the terms and conditions of the GSA Schedule contract will remain in effect. The Contractor shall not change, condition, or deviate from the resulting BPA pricing, terms and conditions, or cause such to occur by virtue of not strictly complying with the terms and conditions of the resultant BPA.

b. Authority

Pursuant to FAR 8.405-3, one Blanket Purchase Agreements (BPA) will be awarded as a result of this Request for Quote (RFQ) for the Enterprise Applications Technical Services (EATS) BPA.

c. Order Period of Performance

Orders issued against the BPA will have their own Period of Performance and may include options.

Orders issued before but not completed before the BPA expires shall be completed within twelve months after the final BPA expiration (including any order options).

d. BPA Volume and Estimated Total Value

The estimated total value of all BPA orders will be added at time of award. The Government is obligated only to the extent of authorized purchases made under the BPA and orders are not guaranteed.

e. Order Type

BPA Orders will be Firm Fixed Price (FFP). The quantity of each item or labor category ordered will be multiplied against the rate listed in this schedule, or as negotiated if lower rates are proposed; and the cumulative extended total of all items ordered will define the firm-fixed price. FFP type orders shall align with the Contractor's proposed technical approach to the work.

XVI. Contract Administration

This contract shall be a BPA against the General Service Administration (GSA) IT Schedule 70 with a one (1) year base period and four (4) option years. There is a mix of required and optional tasks within the scope of the BPA. Task Orders issued under this BPA will be enterprise-wide and highly visible across the Department of Treasury and its customers.

Treasury may place orders against this BPA as workstreams and/or individual initiatives identified for contractor support. However, there are no intended or implied guarantees regarding using this vehicle and some orders may be conducted simultaneously or separately.

The Contracting Officer will determine the applicable contract type for each Task Order under this BPA and will include this in the Government’s requirements document for each project. Each Request for Task Order Proposal (RFTOP) issued under this contract shall identify the Government’s determination of contract type.

a. Pricing Terms

This BPA shall be performed under Firm Fixed Price (FFP). The applicable unit price for FFP task order shall be a unit price for the period in which the services are estimated to be performed, as agreed to by the Government and the Contractor.

The Contractor shall comply with FAR 52.232-7 in regard to the ceiling price for the individual task order(s).

b. Period of Performance

The Period of Performance for this Contract will be a 12-month base period and four (4) 12-month option periods.

Contract Term Period of Performance Base 12 months from award date Option Year 1 12 months Option Year 2 12 months Option Year 3 12 months Option Year 4 12 months

c. Authorized Ordering Officials

US Department of Treasury, Internal Revenue Service (IRS) Contracting Officers are authorized as ordering officials to place task orders under this BPA.

The Contracting Officer, in accordance with FAR Subpart 1.6, is the only individual authorized to enter, administer, and terminate work under this BPA. Notwithstanding any clauses contained elsewhere in this contract, this said authority remains solely with the Contracting Officer.

If the Contractor makes any changes at the direction of any person other than the Contracting

Officer, the change will be considered to have been made without authority and no adjustment will be made in the contract price to cover any increase in cost incurred.

All correspondence related to this order shall be directed as follows:

The Contracting Officer (CO) for the contract is: TBD

DT1052.201-70 COR Appointment and Authority (APR 2004)

The Contracting Officer Representative (COR) for the contract is: TBD

The Alternate Contracting Officer Representative (ACOR) for the contract is: TBD

d. Designation and Technical Direction

The CO may designate CORs for individual Task Orders that will be responsible for the day-to-day oversight of the Order. The COR will represent the CO in administrating technical details within the scope of the order. The COR is also responsible for the final inspection and acceptance of all order deliverables and reports and other responsibilities as may be specified in the order.

The COR is not otherwise authorized to make any representations or commitments on behalf of the CO or the Government. The COR does not have authority to alter the Contractor’s obligations or to change the order specifications, price, terms, or conditions. If, as a result of technical discussions, it is desirable to modify order obligations or the specification, changes will be issued in writing and signed by the CO.

The designated COR may provide written technical direction to the Contractor concerning the work performed under the contract. Technical direction is limited to direction that fills in details or completes the general description of the work outlined in the contract.

Technical direction includes:

1. Directions to the Contractor that suggest pursuit of certain lines of inquiry, shift work emphasis, fill in details or otherwise serve to accomplish the contractual statement of work.

2. Guidelines to the Contractor, that help interpret technical portions of work descriptions.

3. Technical direction must be within the general scope of work stated in the contract.

Technical direction may not be used to:

1. Assign additional work under the contract.

2. Direct a change as defined in the “CHANGES” clause of the contract.

3. Increase or decrease the contract price or estimated contract amount (including fee), as applicable, the direct labor hours, or time required for contract performance.

4. Change any of the terms, conditions, or specifications of the contract.

5. Interfere with the Contractor’s rights to perform the terms and conditions of the contract.

6. All technical direction has to be in writing (or via e-mail) by the applicable COR.

e. Ordering Procedures

1. The CO will provide a technical request to the Contractor.

2. The CO will request a quote and technical approach. The Contractor shall evaluate the scope of the request and provide a quote.

3. The quote shall indicate either compliance with the requirements, risks, assumptions, and any conflict-of-interest issues.

4. Written technical quotes shall address as appropriate: (other items may be requested at CO discretion):

a. Proposed personnel (labor mix).

b. Technical Approach.

c. Other quote elements (travel and purchase parts and supplies etc.).

d. Order terms.

e. Other pertinent data, (e.g., potential conflict of interest issues).

5. The quote shall include detailed pricing for all requirements requested at prices equal to or lower than those established in the BPA.

6. Other related information shall always be in writing and address relevant information as required by the BPA or requested by the CO. The Contractor shall assume all expenses associated with quote preparation for Orders.

f. BPA Orders

Orders issues under this BPA may contain the following information:

● Date of order.

● Contract number and Order number.

● Description, quantity, or units ordered and contract…