PWS 25-X-0002.docx
DOCX document 142 KB Posted
- Solicitation number
- 2032H5-25-X-0002
About this file
This Performance Work Statement (PWS) details the Department of the Treasury's requirements for Integrated Talent Management (ITM) Technical Support Services. The solicitation seeks a contractor to provide comprehensive technical support for the Treasury's enterprise-wide SAP SuccessFactors talent management system, which supports approximately 125,000 employees and contractor staff across all Treasury bureaus. The PWS outlines six primary service tasks: Project Support Services, Technical Support Services, Functional Support Services, Data Integration and Migration Services, Training Services, and Upgrade Support.
Key requirements include the contractor being a certified SAP/NS2 partner, possessing at least two federal government past performance examples in SuccessFactors implementation, and having staff certified in SAP talent management modules. The anticipated contract is a 5-year Blanket Purchase Agreement (BPA) with one 12-month base period and four 12-month option periods, starting around March 2026. The system covers talent management activities such as learning management, performance management, succession planning, and potential future modules like compensation and competency management. Contractors must provide high-risk public trust cleared personnel and demonstrate ability to support system configuration, issue resolution, data integration, governance activities, upgrade planning, and user training.
View the file
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
| Department of the Treasury | ITM Technical Support Services | |
| Enterprise Applications (EA) | Performance Work Statement (PWS) |
Department of the Treasury Integrated Talent Management (ITM)
Technical Support Services Performance Work Statement (PWS)
1.0 Introduction
The Treasury Offices of the Chief Information Officer (OCIO) and the Chief Human Capital Officer (CHCO) purchased a single, enterprise-wide Integrated Talent Management (ITM) solution, branded ITM for all Treasury employees. The ITM solution includes a full range of talent management-related activities such as learning management, competency management, performance management, succession planning, workforce analytics and other learning management requirements. Treasury plans to implement the entire solution across all Treasury bureaus, encompassing roughly 125,000 employees and contractor support staff. Currently the Department has deployed Learning Management, Performance Management and Succession Planning. Additional deployments for Compensation Planning, Competency Management and other modules may be implemented in the future.
2.0 Background
To innovate and provide a state-of-the-art Human Resource (HR) solution, OCIO and CHCO created a program focused on an ITM system offered via a Software as a Service (SaaS) model. The ITM program resides within OCIO, Enterprise Applications (EA) and provides shared services to the Treasury, including Departmental Offices (DO) and the bureaus.
The BPA scope includes:
a. Access to technical Contractor resources who can sustain, consult and improve the ITM system by executing work on the back-end of the application
b. Provide subject matter expertise on the functionality of the SAP National Security Services, Inc. (SAP/NS2) system as well as guidance on the best ways to configure ITM
c. Deploy and utilize the SAP/NS2 system to meet the needs of the Department
3.0 Statement of Need
The Department of the Treasury requires flexible Contractor support services to maintain ITM program and customer needs and improve and expand ITM functionality and usage. Treasury requires support in project management, technical and functional support, configuration management, training and annual upgrade support.
Services shall include subject matter expertise to:
a. Support the deployment of modules and customers to the system;
b. Support the configuration of modules;
c. Identify and resolve issues with the system not covered by the Secure Preferred Care provided by Carahsoft/SAP/NS2;
d. Identify and resolve data quality issues that may arise related to the deployment of additional modules;
e. Support data integrations, extensions, and connectors within the ITM, as well as other applications;
f. Provide best practice guidance and advice on the optimal configuration and use of the modules including continuous evaluation of the system to improve performance;
g. Support the development and maintenance of enterprise system design documentation;
h. Support the work of the Treasury ITM Configuration Control Board;
i. Subject matter expertise to support the Department with vendor upgrades of the ITM system (usually biannually) or upgrades based on changes to underlying technology supporting the system (example migrating from Oracle to HANA database platform);
j. Analyze web services and Application Programming Interfaces (API) requirements, configure products / offerings to support authentication and authorization adhering to industry standards
k. Support assessments analyzes, establishing best practices and trainings to promote use of the system.
4.0 Scope Requirements
The Contractor shall be responsible for providing subject matter expertise support in project management, technical and functional support, data integration and migration management, and upgrade support as specified below.
The Contractor is required to be a certified partner with Original Equipment Manufacturer (OEM) software vendor SAP/NS2 and must be able to provide written proof of partnership with SAP/NS2. The Contractor shall be able to provide multiple (2+) past performance examples of providing relevant SuccessFactors Talent management implementation services as a prime vendor on contracts supporting the U.S. Federal Government. The Contractor is required to have sufficient number of employees on staff with relevant SAP talent module certifications to be able to meet the scope, skillset, and capacity required by ITM Treasury and its customer base.
ITM SERVICES SUMMARY
| TASK |
| TITLE |
| 1 |
| PROJECT SUPPORT SERVICES |
| 2 |
| TECHNICAL SUPPORT SERVICES |
| 3 |
| FUNCTIONAL SUPPORT SERVICES |
| 4 |
| DATA INTEGRATION AND MIGRATION SERVICES |
| 5 |
| TRAINING SERVICES |
| 6 |
| UPGRADE SUPPORT |
Task 1: Project Support Services The Contractor shall offer Treasury strategic project management and system administration (including problem solving, answering technical questions, assisting in configuration workshops, documenting decisions, and providing functionality demonstrations). The Contractor shall provide a description of project management support provided, including core and optional services, overarching system implementation services methodology. The Contractor shall have a flexible staffing model with the ability to surge and ramp up resources, as needed, throughout the duration of the period of performance. Working closely with the Contracting Officer’s Representative (COR) and the ITM program, the Contractor shall execute sound project management principles. The project management approach shall integrate the people, process, technology and business readiness components including time, resources, integration, quality, risk, scope and budget. The Contractor shall complete the following:
1.1 Upon award, the Contractor shall host a kick-off meeting, within two (2) weeks of award, in collaboration with the COR and the project delivery team. This meeting shall be designed to review and clarify program objectives, confirm roles and responsibilities, understand tasks and sub tasks, and agreed upon expectations from Treasury in collaboration with the Treasury project leadership team.
1.2 Within two (2) weeks of the project kick-off of each order the Contractor shall develop project charters, project schedules and other governance tools, as needed, such as: RACI matrices, process flow charts, approval gates, documentation/templates, information repositories, and forms. All tools shall be updated and submitted annually thereafter or as determined in each task order.
1.3 Within three (3) weeks of the date of each order award the Contractor shall develop, execute, and maintain an integrated Project Management Plan (PMP) that identifies project start and completion dates, milestones, interdependencies between tasks, timelines necessary to measure progress toward project goals. Other content may include Critical Success Factors, Quality Management Plan. Human Resources Plan, Stakeholders List, Communication Management Plan, and Risk Management Plan. Where appropriate, this PMP shall address all aspects of either Waterfall or Agile software development (depending on the method chosen by agreement), of functional modules and deployments.
1.4 The Contractor shall utilize MS Project Server or another web-based project management tool within four (4) weeks of award. This should be designed as a central platform to manage the project and project management disciplines of the work plan, quality and risk management.
1.5 The Contractor shall facilitate the gathering, documentation and validation of scope and requirements for new modules, enhancement of existing modules, pilots, and evaluation of new technologies.
1.6 The Contractor shall provide senior leadership oversight to ensure the successful completion of order deliverables.
1.7 The Contractor shall provide web-based risk and issue tracking.
1.8 The Contractor shall provide lessons learned as requested to improve performance in subsequent tasks.
1.9 The Contractor shall develop and deliver weekly progress reports to the project COR that include current and projected resource allocations, work plans, critical path milestones, risks, delays, and projected burn rate (for Labor Hour requirements). In addition, the Contractor shall deliver monthly reports that highlight accomplishments for each month, any issues encountered and resolved, status updates on all tasks and remaining forecast and current burn rates.
1.10 The Contractor shall host a monthly call with the CO, COR, ITM PMO and other stakeholders identified by the team to review the following contractual items:
a. Delivery status against scope
b. Delivery Quality
c. Issues/Risks
d. Schedule
e. Actual expenditures and spend plan
1.11 The Contractor is responsible for proper project close out for each awarded Order.
1.12 The Contractor shall not provide project management support directly to Treasury sub-organizations without expressed approval by the COR and Treasury PMO.
Anticipated Deliverables upon Order award (Services/Products)
Kick-off Meeting
Project Charter
Project Schedule
Project Management Plan
Web-based Project Management Tool
Communications Support
Scope and Requirements Validation
Senior Leadership Oversight
Weekly and Monthly project status report to COR/ITM PMO
Web-Based Risk & Issue Tracking
Lessons Learned
Project Close Out
Task 2: Technical Support Services The Technical Support Services task shall be used to manage global and customer specific issues, questions, concerns, or changes to technical configurations. This includes enterprise configuration settings, role-based permissions, customizations / extensions, data integrations, data migrations, and custom reports. This support is focused on receiving, tracking and managing reported errors and corrections, review and analysis of technical error logs, and ensuring configuration management of changes to the Enterprise System Design Documents (ESDD) – for each module – and concomitant scripts. These services may be requested via the ticketing system, email or verbal interactions.
2.1 As needed, develop and maintain configuration management of, and document changes in the ESDD.
2.2 Provide system technical support and subject matter expertise when requested.
2.3 Develop enterprise system and data landscape architecture documents when requested.
2.4 Develop Functional Design Documents (FDD) and technical Design Documents to capture requirements, diagrams, and designs for technical work.
2.5 Develop, implement, and deliver customizations to standard system functionality
2.6 Develop and maintain custom reports and dashboards
2.7 Ensure all custom development adheres to and clears Federal Information Security requirements.
2.8 Ensure all products delivered that are covered under 508 requirements are in compliance with Section 508 and other federal regulatory standards.
2.9 Maintain and implement technical configuration changes to global configurations managed through the provisioning/backend and application
2.10 Work with Treasury’s Configuration Control Board (CCB) to review change requests, including identifying and recording significant changes as requested.
2.11 Assist with the work of the Treasury’s CCB that shall meet regularly to review change requests. In coordination with the Government, assess the associated impacts for any system changes formally proposed by the CCB, and when applicable, develop a test plan
2.12 Develop system and custom development test plans and scripts.
2.13 Resolve issues identified during testing and document summary of findings and actions in a summary report.
2.14 Provide technical post go-live support to ensure the successful transition to Operations & Maintenance for Treasury projects, initiatives, and customers.
Anticipated Deliverables upon Order award (Services/Products)
Technical Subject Matter Expertise
Enterprise System and Data Landscape Architecture Document
Enterprise System Design Documents (ESDD) for all ITM Modules
Functional Design Documents (FDD) and Technical Design Documents (TDD)
Custom Code Development & Maintenance
Custom Report Development & Maintenance
CCB Support
Information Security Compliance & Documentation
Section 508 and Regulatory Compliance
System & Custom Development Testing Plans
System & Custom Development Test Scripts
System & Custom Development Test Summary and Remediation Report
Task 3: Functional Support Services The Functional Support Services task shall be used to address issues, questions, or concerns for localizations – bureau specific configurations and templates – and evaluate new use cases to address functional business needs. This support is focused on business process analysis, business process reengineering, and functional subject matter expertise to aid in the adoption of ITM modules and continual improvement of localizations. These services may be requested via the ticketing system, email or verbal interactions.
3.1 Provide system configuration support and subject matter expertise when requested
3.2 Deliver system demonstrations and walkthroughs to Treasury stakeholders and customers
3.3 Support fit / gap assessments and requirements analysis in preparation of new work to meet customer requirements
3.4 Deliver up to three (3) cycles of design and configuration workshops tailored to module and/or functionality. The number of cycles will be determined in each order.
3.5 Develop documentation to capture findings and recommendations from requirements and use case analysis activities
3.6 Plan and facilitate Business Process Reengineering activities to support customer transitions from paper-based processes and/or other systems
3.7 Document gaps and solutions within the configuration workbooks for each module and/or localization
3.8 Document and maintain configuration decisions and changes in the configuration workbooks
3.9 Develop and deliver knowledge transfer documentation, frequently asked questions, and playback sessions for configured processes, modules, and functions as directed in the order.
3.10 Develop and deliver process design workshop and decks.
3.11 Develop plans, scripts and reports in support of User Acceptance Testing and Quality Assurance Testing
3.12 Resolve configuration issues identified during User Acceptance Testing and Quality Assurance Testing
3.13 Assist with the work of the Treasury’s Deputy Assistant Secretary of Human Resources / Chief Human Capital Office (DASHR/CHCO) and the ITM Program to continuously engage, educate and drive adoption of the ITM modules / functions
Anticipated Deliverables upon Order award (Services/Products)
Functional Subject Matter Expertise
Fit / Gap Assessments
Requirements & Use Case Analysis
Business Process Reengineering & Supporting Documentation
System Demonstrations / Walkthroughs
Configuration Workshops Cycles I-III
Configuration Workbooks
Knowledge Transfer / Frequently Asked Questions / Playback Sessions
Process Design Workshop and Decks
Process Flows & Design Documentation
User Acceptance Testing and Quality Assurance Testing Plans
User Acceptance Testing and Quality Assurance Testing Scripts
User Acceptance Testing and Quality Assurance Testing Summary and Remediation Reports
Task 4: Data Integration and Migration Services The Data Integration and Migrations Services shall be used to execute technical work to meet Treasury requirements for the management, movement, automation, and integration of data. These services may be requested via the ticketing system, email or verbal interactions.
4.1 The Contractor shall maintain current integrations and create new data integrations as needed. For existing data integrations, the Contractor shall work with System Owners of the target systems to assess the operations, quality, and responsiveness of the current feed. If changes are required, the Contractor will document requirements for changes, and provide solutions that improves data delivery to the target systems.
4.2 Requests for new data integrations will be provided by the ITM PMO in conjunction with the COR. The Contractor shall provide a list of system infrastructures used for integration management and manage data integration through one of the following three ways: Integrate using standard automated SAP connectors (e.g. to PeopleSoft HCM suite and Java Message Agent Client (JMAC) and component application programming interfaces (APIs).
4.3 The Contractor shall hold data design workshops if mutually determined necessary by the ITM PMO and the Contractor.
4.4 Integrate using a batch/flat-file so provided data is formatted and transmitted through SFTP.
4.5 The Contractor shall work closely with the Treasury Enterprise Data Management Team to determine data format, data capture/retention (historical/deltas), source data cleansing, data changes (new data fields), and understand current data management and reporting technologies maintained in OCIO. This will be a critical need as data is prepared to flow from the ITM system to downstream reporting systems (i.e. Data Warehouse, etc.)
4.6 The Contractor shall document all integration interface designs with Functional and Technical specifications, which shall include data flow models, data models, data mapping, and detailed schema definitions for involved data objects. The Contractor shall submit all data definition tables, mapping and mapping and diagrams to the ITM PMO.
4.7 Maintain, modify and/or establish new connectors between the ITM modules.
4.8 Support existing integrations and data feeds, as well as perform configuration changes on existing integrations when requested. Examples include:
a. Web services configuration support
b. Performance Ratings Feed Process Integration (PI) configuration support
c. OLSA Connector configuration
d. Employee Feed from HR Connect Process Integration (PI) configuration support
e. Organizational File Feed/LMS Domain changes support
f. User profile manual catch-up when Federal User Connector fails
g. IRS, Treasury and OCC Datamarts configuration support
h. SSO configuration changes
4.9 Support data migrations from existing sources to the ITM by conducting an analysis of the data, mapping the data and testing to produce data migration procedures
4.10 Upon request, the Contractor shall migrate data from existing systems to ITM. The Contractor shall support the process of loading data in an iterative approach which shall include conducting an analysis of the data, mapping the data and testing to ultimately produce a data migration procedure which shall be executed according to the project plan and schedule. The Contractor shall assist in testing and develop test scripts. Whenever possible the Contractor shall use existing data connectors to execute data migration. After conducting an analysis of the requested data migration, the Contractor shall notify the Department in their proposal if a standard connector cannot accommodate all data (types, columns, tables, etc.) and provide a proposed solution to mitigate. The contractor will deliver updates to already existing documentation to include data mapping, FDD and TDD updates or deliver new documentation. The Contractor shall submit all documentation to Treasury.
4.11 The Contractor shall provide up to three (3) cycles of conversion loads to test system instances for Treasury’s acceptance and approval of quality. The Contractor shall coordinate between the COR, Treasury PMO, and program offices managing existing systems to identify data fields that will be pursued. Migrations shall produce a turnkey solution for Treasury to operate, uninterrupted, on “go-live” dates.
Anticipated Deliverables upon Order award (Services/Products)
Design Specification Documentation (e.g. ETL Processes, Migration Procedures)
Data Design Workshops
Data Design Requirements
Script Development
Data Dictionary / Data Elements / Data Taxonomy
Data Modeling Design Document
Data Loading (Business rules for translation and mapping from source to target system)
Data conversion load cycles
Error Handling Mechanisms
Performance testing / regression testing cases
Data Integration & Migration Testing Plans
Data Integration & Migration Test Scripts
Data Integration & Migration Test Summary and Remediation Report
Data Validation & Issue Remediation
Cutover Plan for Integrations, Migrations & Validations
Task 5: Training Services The Contractor shall deliver training both tailored to Treasury’s specific and/or generic to SAP standard subject matter. Examples include Super Admin, Learning, Succession, Performance, Compensation, and Workforce Analytics topics. The Contractor shall customize the SAP standard, out-of-the-box training materials to meet the needs of Treasury. The Contractor shall be able to deliver a variety of training depending on the need. Training mediums shall include classroom, on-site or remote and on-line. Courses may be for either Administrators, Train-the-Trainer (to train other administrators internally), or end-user.
5.1 The Contractor shall provide computer-based training courses.
5.2 The Contractor shall provide instructor led training courses (on-site or online).
5.3 The Contractor shall develop job aids.
5.4 The Contractor shall provide course materials.
Anticipated Deliverables upon Order award (Services/Products)
Computer Based Training Course
Instructor Led Training Course (On-site or Online)
Job Aids
Course Materials
Task 6: Upgrade Support The Contractor shall provide managed Upgrade Support Services for any upgrades or critical functionality releases. The Contractor shall supply comprehensive “Delta” document(s) in order for the customer to determine how the capabilities included in the upgrade should be implemented. These services may be requested via the ticketing system, email or verbal interactions. The Contractor shall provide the following information in release notes and other documentation to support the change management process:
a. New features/functionality
b. Modified features/functionality
c. Removed features/functionality
d. Known bugs/issues that have been documented regarding the release/build
6.1 The Contractor shall provide functional guidance, and project team and customer workshops on upgrade changes. The Contractor shall schedule and participate in workshops to describe options and features available in the release and document the customer’s decisions in workbooks for the upgrade.
6.2 The Contractor shall support the development and updating of program documentation impacted by each upgrade. Required documents are subject to change and the Contractor shall adhere to the most current version.
6.3 The Contractor shall provide a draft update to the ITM PMO 20 days prior to upgrade implementation. The contractor shall also deliver the final update of the ESDDs no later than 20 days following the upgrade. Each upgrade shall include the following efforts:
a. Develop and deliver a schedule representative of the contractor, and ITM customer tasks and responsibilities
b. Conduct analysis of Universal and Opt-In Application Changes and develop documentation to present to customers and use case specifications
c. Conduct virtual Upgrade workshops
d. Provide virtual demonstrations to the customer
e. Develop required test scripts for UAT. The Contractor shall deliver the completed test scripts to customers and ITM PMO team
f. Provide assistance for customer required testing for user acceptance
g. Help research customer upgrade questions
h. Implement upgrade configuration changes and decisions
i. Provide updated and editable out-of-the-box training materials three months prior to scheduled upgrade
j. Provide subject matter support and update all necessary system documentation with Upgrade changes/impacts
k. Participate in weekly status meetings via teleconference to discuss release task progress, risks, and issues, taking minutes listing decisions reached, discussions held and action items, and then sending the draft to the facilitator for approval and distribution.
Anticipated Deliverables upon award (Services/Products)
Updated System Documentation including: ESDD Documentation configuration guides, product guides, Delta Documentation, and UST-required artifacts
Assistance with UAT test script development and customer required testing for user acceptance
Customer configuration decisions implementation
Editable Training Materials for the Upgrade
Release Notes
Use Case Specifications
Virtual configuration workshops on all modules tailored to UST’s needs
Virtual customer demonstrations
Upgrade Workshop materials and briefings
Tracking Risks, Actions, Issues, & Decisions
Upgrade and release test scripts
Upgrade weekly status meetings
5.0 Contract Deliverables
All deliverables, work products, hard-copy and electronic documents including everything developed by the Contractor while working on the resulting contract are the sole property of the United States Government. The Contractor shall have no rights of ownership. The Contractor may not share or reproduce content without express, written consent from Treasury EA.
Deliverables will be established at the Order award. The Contractor and Treasury PMO may adjust timelines and upon agreement.
Treasury will perform an initial review of deliverables, and if problems are encountered during the review, the Contractor must correct them. If necessary, a meeting may be convened to resolve any differences. The contractor shall make all required changes to achieve an acceptable deliverable. The Government will perform its review within approximately 15 calendar days from receipt of the deliverable When the review of a deliverable results in necessary modifications, Treasury will, in accordance with the approved order schedule, provide the necessary documentation to correct the deliverable. It will then be the responsibility of the contractor to properly and consistently incorporate the comments in the final product.
5.1 Details: Anticipated Deliverables upon Order award
The anticipated deliverables/services/work products required by the resulting contract are specified below:
Task 1 – Project Support Services
| ID |
| Description |
| 001 |
| Kick-Off Meeting |
| 002 |
| Project Charter |
| 003 |
| Project Schedule |
| 004 |
| Project Management Plan |
| 005 |
| Web-based Project Management Tool |
| 006 |
| Communications Support |
| 007 |
| Scope and Requirements Validation |
| 008 |
| Senior Leadership Oversight |
| 009 |
| Weekly and Monthly project status report to COR/ITM PMO |
| 010 |
| Web-Based Risk & Issue Tracking |
| 011 |
| Lessons Learned |
| 012 |
| Project Close Out |
Task 2 – Technical Support Services
| ID |
| Description |
| 013 |
| Technical Subject Matter Expertise |
| 014 |
| Enterprise System and Data Landscape Architecture Document |
| 015 |
| Enterprise System Design Documents (ESDD) for all ITM Modules |
| 016 |
| Functional Design Documents (FDD) and Technical Design Documents (TDD) |
| 017 |
| Custom Code Development & Maintenance |
| 018 |
| Custom Report Development & Maintenance |
| 019 |
| CCB Support |
| 020 |
| Information Security Compliance & Documentation |
| 021 |
| Section 508 and Regulatory Compliance |
| 022 |
| System & Custom Development Testing Plans |
| 023 |
| System & Custom Development Test Scripts |
| 024 |
| System & Custom Development Test Summary and Remediation Report |
Task 3 – Functional Support Services
| ID |
| Description |
| 025 |
| Functional Subject Matter Expertise |
| 026 |
| Fit / Gap Assessments |
| 027 |
| Requirements & Use Case Analysis |
| 028 |
| Business Process Reengineering & Supporting Documentation |
| 029 |
| System Demonstrations / Walkthroughs |
| 030 |
| Configuration Workshops Cycles I-III |
| 031 |
| Configuration Workbooks |
| 032 |
| Knowledge Transfer / Frequently Asked Questions / Playback Sessions |
| 033 |
| Process Design Workshop Decks |
| 034 |
| Process Flows & Design Documentation |
| 036 |
| User Acceptance Testing and Quality Assurance Testing Plans |
| 037 |
| User Acceptance Testing and Quality Assurance Testing Scripts |
| 038 |
| User Acceptance Testing and Quality Assurance Testing Summary and Remediation Reports |
Task 4 – Integration and Migration Services
| ID |
| Description |
| 039 |
| Design Specification Documentation (e.g. ETL Processes, Migration Procedures) |
| 040 |
| Data Design Workshops |
| 041 |
| Data Design Requirements |
| 042 |
| Script Development |
| 043 |
| Data Dictionary / Data Elements / Data Taxonomy |
| 044 |
| Data Modeling Design Document |
| 045 |
| Data Loading (Business rules for translation and mapping from source to target system) |
| 046 |
| Data conversion load cycles |
| 047 |
| Error Handling Mechanisms |
| 048 |
| Performance testing / regression testing cases |
| 049 |
| Data Integration & Migration Testing Plans |
| 050 |
| Data Integration & Migration Test Scripts |
| 051 |
| Data Integration & Migration Test Summary and Remediation Report |
| 052 |
| Data Validation & Issue Remediation |
| 053 |
| Cutover Plan for Integrations, Migrations & Validations |
Task 5 – Training Services
| ID |
| Description |
| 054 |
| Computer Based Training Course |
| 055 |
| Instructor Led Training Course (On-site or Online) |
| 056 |
| Job Aids |
| 057 |
| Course Materials |
Task 6 – Upgrade Support Services
| ID |
| Description |
| 058 |
| Updated System Documentation including: ESDD Documentation configuration guides, product guides, Delta Documentation, and UST-required artifacts |
| 059 |
| Assistance with UAT test script development and customer required testing for user acceptance |
| 060 |
| Customer configuration decisions implementation |
| 061 |
| Editable Training Materials for the Upgrade |
| 062 |
| Release Notes |
| 063 |
| Use Case Specifications |
| 064 |
| Virtual configuration workshops on all modules tailored to UST’s needs |
| 065 |
| Virtual customer demonstrations |
| 066 |
| Upgrade Workshop materials and briefings |
| 067 |
| Tracking Risks, Actions, Issues, & Decisions |
| 068 |
| Upgrade and Release Test scripts |
| 069 |
| Upgrade weekly status meetings |
5.2 Deliverable Acceptance Criteria
IAW 52.212-4, Alternate I (a) Inspection/Acceptance -- Contract Terms and Conditions -- Commercial Items; the Government and Contractor define acceptance of the deliverables as follows:
Final inspection and acceptance of all work performed, reports and other deliverables will be performed at the government site (on-site at 1750 Pennsylvania Avenue, 10th floor, Washington, D.C.). Deliverables are not final until reviewed and approved by the COR. All deliverables, including anything and everything developed while working under the resulting contract are the sole property of the United States Government.
All Contractor-produced deliverables shall be reviewed using the following criteria:
a. Accuracy – Services and work products shall be accurate in presentation, technical content, and adherence to accepted elements of style.
b. Clarity Work products shall be clear and concise. All diagrams shall be easy to understand and relevant to the supporting narrative.
c. Specifications Validity All services and work products must satisfy the requirements of the Government as specified herein and with each resulting Order.
d. File Editing All text and diagrammatic files shall be editable by the Government.
e. Format - Work Products shall be submitted in hard copy (where applicable) and in media as required by the project per COR’s direction.
f. Timeliness – Work products shall be submitted on or before the due date as mutually agreed upon by the EA COR and the Contractor On-Site Manager.
The Government will deliver, in writing, acknowledgement of receipt and acceptance of a document, plan or similar written deliverable within five (5) business days upon receipt from the Contractor.
5.3 Deliverables/ Work Products
All Contractor deliverables or work products shall remain categorized as "Official Use Only.” The release of any portion must be authorized in writing by the Government.
6.0 Required Knowledge, Skills And Abilities
Specialized experience shall include the current application of knowledge and expertise in such areas as the following: project management, technical and functional support services of the SAP/NS2 SuccessFactors System and Human Capital Suite and Federal HR Regulation and Policy, data integrations and migrations, training services and upgrade support services. The Contractor shall be able to provide expertise using collaborative tools such as Microsoft SharePoint. Reference PWS Attachment 1 for Labor Category descriptions.
7.0 Performance Level Agreements
The Contractor shall adhere to the BPA and subsequent Task Order Performance Level Agreements (PLAs).
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 do not meet those standards and are rejected by the COR/ITM PMO will result in a negative contractor performance assessment. The Contractor shall perform any necessary rework at the contractor’s expense.
| CLIN |
| PLA |
| Required Service/Product |
| Performance Standard/Level/Criteria |
| Acceptable Quality Level (AQL) |
| Monitoring Method |
| 0001 |
| 1 |
| Project Management Support |
100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
(LHTO) REMEDY FOR AQL PROBLEMS –
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
100% Review by ITM PMO / COR
COR will log all instances of problems found
| 1a |
| Provides draft meeting agendas (meetings) |
| At least two (2) business days prior to the scheduled meeting |
| 1b |
| Provides draft meeting minutes (meetings) |
| Within two (2) business days after the meeting occurred |
| 1c |
| Escalates issues |
| As needed |
| 1d |
| Provides timely communications and responses (meetings, emails, phone conferences) |
| As requested |
| 1e |
| Tracks and reports on risks, action items, and issues. |
| As defined in project charter or plan |
| 1f |
| Delivers status call and report on time. |
| As defined in project charter or plan |
| 1g |
| Kick-off Meeting |
| Within two (2) weeks of task order award |
| 1h |
| Project Charter |
| Within three (3) weeks of task order award |
| 1i |
| Schedule |
| Within three (3) weeks of task order award |
| 1j |
| Management Plan |
| Within three (3) weeks of task order award |
| 1k |
| Web-based Project Management Tool |
| Within-four (4) weeks of task order award |
| 1l |
| Communication Support |
| As needed |
| 1m |
| Scope and Requirements Validation |
| As determined by the mutually agreed upon schedule |
| 1n |
| Weekly and Monthly project status report to COR/ITM PM |
| Weekly/Monthly |
| 1o |
| Web-Based Risk & Issue Tracking |
| As determined by the mutually agreed upon schedule |
| 1p |
| Lessons Learned |
| Weekly |
| 1q |
| Project Close Out |
| As determined by the mutually agreed upon schedule |
| 2 |
| Technical Support Services |
100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
(LH TO) REMEDY FOR AQL PROBLEMS –
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
100% Review by ITM PMO / COR
| 2a |
| Maintains configuration management of and documents changes in the ESDD |
When requested
| 2b |
| Provides system configuration support and subject matter expertise. |
When requested
| 2c |
| Coordinates and manages instance refreshes through customer-initiated tickets |
| When requested |
| 2d |
| Supports existing connectors in current state and through future configuration changes. |
When requested
| 2e |
| Supports existing integrations and data feeds, as well as performing configuration changes on existing integrations. |
| When requested |
| 2f |
| Supports planning and determining the scope and level of effort for additional support service requests |
| When requested |
| 2g |
| Supports the development and maintenance of the Enterprise System and Data Landscape |
| When requested |
| 2h |
| Creates and or maintains the Architecture Document |
| When requested |
| 2i |
| Supports the development and maintenance of Enterprise System Design |
| When requested |
| 2j |
| Creates and or maintains documents not otherwise specified for all ITM modules |
| When requested |
| 2k |
| Supports the development and maintenance of Functional Design Documents (FDD) and Technical Design Documents (TDD) |
| When requested |
| 2l |
| Creates custom development and provides maintenance to custom development |
| When requested |
| 2m |
| Creates custom reports and provides custom report maintenance |
| When requested |
| 2n |
| Creates and maintains information security compliance & documentation |
| When requested |
| 2o |
| Maintains compliance with Section 508 requirements (see Section 8.0) |
| When requested |
| 2p |
| Maintains compliance with regulatory requirements |
| When requested |
| 2q |
| Develops System & Custom Development Testing Plans |
| When requested |
| 2r |
| System & Custom Development Test Scripts |
| When requested |
| 2s |
| System & Custom Development Test Summary and Remediation Report |
| When requested |
| 0003 |
| 3 |
| Functional Support Services |
100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
| 3a |
| Functional Subject Matter Expertise |
| When requested |
| 3b |
| Fit / Gap Assessments |
| When requested |
| 3c |
| Requirements & Use Case Analysis |
| When requested |
| 3d |
| Business Process Reengineering & Supporting Documentation |
| When requested |
| 3e |
| System Demonstrations / Walkthroughs |
| When requested |
| 3f |
| Configuration Workshops |
| When requested |
| 3g |
| Configuration Workbooks |
| When requested |
| 3h |
| Knowledge Transfer / Frequently Asked Questions / Playback Sessions |
| When requested |
| 3i |
| Process Design Workshop Decks |
| When requested |
| 3j |
| Process Flows & Design Documentation |
| When requested |
| 3k |
| User Acceptance Testing and Quality Assurance Testing Plans |
| When requested |
| 3l |
| User Acceptance Testing and Quality Assurance Testing Scripts |
| When requested |
| 3m |
| User Acceptance Testing and Quality Assurance Testing Summary and Remediation Reports |
| When requested |
| 0004 |
| 4 |
| Data Integration and Migration Services |
100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
(LH TO) REMEDY FOR AQL PROBLEMS –
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
100% Review by ITM PMO / COR
| 4a |
| Design Specification Documentation ( e.g. ETL Processes, Migration Procedures) |
| When requested |
| 4b |
| Data Design Workshops |
| When requested |
| 4c |
| Data Design Requirements |
| When requested |
| 4d |
| Script Development |
| When requested |
| 4e |
| Data Dictionary / Data Elements / Data Taxonomy |
Data Modeling Design Document When requested
| 4f |
| Data Loading (Business rules for translation and mapping from source to target system) |
| When requested |
| 4g |
| Data Conversion Loads |
| When requested |
| 4h |
| Error Handling Mechanisms |
Performance testing / regression testing cases When requested
| 4i |
| Data Integration & Migration Testing Plans |
Data Integration & Migration Test Scripts When requested
| 4j |
| Data Integration & Migration Test Summary and Remediation Report |
| When requested |
| 4k |
| Data Validation & Issue Remediation |
| When requested |
| 4l |
| Cutover Plan for Integrations, Migrations & Validations |
| When requested |
| 0005 |
| 5 |
| Training Services |
100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
| 5a |
| Formal materials and communications |
| When requested |
Shall be Section 508 Web Content Accessibility Guidelines (WCAG) A & AA compliant. (See Section 8.0)
Meets all 508 requirements per the BPA; this includes removing items identified by 508 review tools as warnings errors as well as defects.
Grammatically correct, no more than 1 formatting, grammatical or typographical error per 10 pages of documentation.
Identifies each step in the process correctly Identifies appropriate actions for end user to take Meets Treasury’s formatting requirements (will be provided) Are compliant with the established ITM branding imagery and color scheme (will be provided) Have removed any production user accounts and/or other personally identifiable information (PII) from screen shots, or data Screen shots reflect the finalized Treasury configured product and template Meets all 508 requirements per the BPA; this includes removing items identified by 508 review tools as warnings errors as well as defects
| 5b |
| Computer Based Training Course |
| See 5a |
| 5c |
| Instructor Led Training Course (On-site or Online) |
| See 5a |
| 5d |
| Job Aids |
Course Materials See 5a
| 0006 |
| 6 |
| Upgrade Support |
100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
| 6a |
| Upgrade project schedule |
Delivered and finalized within two (2) weeks of the project kick-off Contains sprints which define rollout support and knowledge transfer activities Schedule status updates are provided weekly
Schedule is completed with no greater than a 5% deviation from planned milestones and deadlines
| 6b |
| Updated System Documentation including: ESDD Documentation configuration guides, product guides, Delta Documentation, and UST-required artifacts |
| See 5aDocument shall be error free. |
Document shall be delivered 20 days prior to the end of the upgrade cycle.
Updates to the document outside of the upgrade will take no more than two (2) weeks.
| 6c |
| Provides updated and editable out-of-the-box training materials three (3) months prior to scheduled upgrade |
| See 5a |
| 6d |
| Provides Release Notes |
| See 5a |
| 6e |
| Provides Use-Case Specifications |
| See 5a |
| 6f |
| Provides Upgrade Workshop materials and briefings |
| See 5a |
| 6g |
| Tracks Risks, Actions, Issues, & Decisions |
| As defined in project charter or plan |
| 6h |
| Conducts virtual configuration workshops on all modules tailored to UST’s needs |
| As requested |
| 6i |
| Provides virtual demonstrations for the customer |
| As requested |
| 6j |
| Assists with UAT test script development and customer required testing for user acceptance. |
| As requested |
| 6k |
| Helps research questions asked by customer resources updating and creating new scripts. |
| As requested |
| 6l |
| Subject matter support for customer data and system security and documentation |
| As requested |
| 6m |
| Implements customer configuration decisions |
| As requested |
| 6n |
| Participates in status meetings via teleconference to discuss release task progress, risks, and issues, taking minutes listing decisions reached, discussions held and action items, and then sends the draft to the facilitator for approval and distribution |
| As defined in project charter or plan |
0001, 0002, 0003, 0004,0006
| 7 |
| Ticket response, request for level of effort, and resolution of issues |
| Priority 1 – One (1) hour response time. Four (4) hour correction time. |
Priority 2 – Two (2) hour response time. One (1) business day correction time.
Priority 3 – One (1) business day response time. Three (3) business days for correction/ completion.
Priority 4 – Two (2) business days for response time. Three (5) business days for correction/completion.
A plan of action will be identified in response to requests for level of effort (LOE) no later than two (2) days after initial receipt of request.
Plans of action will determine the duration and LOE for support requests. LOE will identify requests already covered under NS2 Secure Preferred Care.
Support services shall provide input into updating documentation as related to and impacted by ticket items 100%
Deliverable Services/Products are delivered "on time" in accordance with official schedules or milestones.
Deliverable Service/Products are at an acceptable level (each product). An un-acceptable product is a product that is not completed; or it has flawed or missing information, analyses, assumptions or conclusions; or it has numerous grammatical problems (i.e. No more than 1 formatting or typographical error per 10 pages of documentation)
(FFP TO) REMEDY FOR AQL PROBLEMS -
Rework until corrected with no change in price.
COR/CO determine if task is worth rework, completion, or if contract warrants termination for default. If worth rework – vendor effort is at no charge.
7.1 Period of Performance (Anticipated)
The period of performance shall be for one Base Period of 12 months, and four 12-month Option Periods. The contract includes FAR 52.217-8 Option to Extend Services and may be executed up to a six-month period.
| Period |
| Period of Performance |
| Base Period (12 months) |
| 3/19/2026-3/18/2027 |
| Option Period 1 (12 months) |
| 3/19/2027-3/18/2028 |
| Option Period 2 (12 months) |
| 3/19/2028-3/18/2029 |
| Option Period 3 (12 months) |
| 3/19/2029-3/18/2030 |
| Option Period 4 (12 months) |
| 3/19/2030-3/18/2031 |
7.2 CLIN Detail
| CLIN |
| Title (Service) |
| Billing Type Base |
| 0001-4001 |
| Project Support Services |
| FFP/LH |
| 0002-4002 |
| Technical Support Services |
| FFP/LH |
| 0003-4003 |
| Functional Support Services |
| FFP/LH |
| 0004-4004 |
| Integration and Migration Support Services |
| FFP/LH |
| 0005-4005 |
| Training Services |
| FFP/LH |
| 0006-4006 |
| Upgrade Support Services |
| FFP/LH |
7.3 Personnel Staffing
7.3.1 The Government anticipates the Contractor will require a total maximum level of effort (LOE) as identified in Attachment 1, Pricing Template, to complete the respective tasks in the Base and Option Periods. The Government anticipates the use of the following Labor Categories (LCATs).
Labor Category
IT Consultant
IT Senior Consultant
IT Manager
IT Senior Manager
IT Partner/Principal/Director
IT Project Delivery Specialist
IT Analyst
Project Controller I
7.3.2 The Contractor shall assign to the resulting contract the following key personnel:
| Title |
| Name |
IT Manager
IT Senior Manager
IT Partner/Principal/Director
7.3.3 LCATs listed by the Government have been determined relevant to the performance of this contract. These LCATs are to be used as a guide. The Contractor may add alternate proposed solutions for key and non-key personnel to the already listed LCATs, or propose their own LCATs altogether. Reference the ITM RFQ, Section V, Volume I, Factor 2, Part 2, which includes instructions for proposing alternate key personnel and non-key personnel.
7.3.4 The Government considers 1,920 hours (excludes holidays) to be a full year labor mix for one (1) individual.
7.3.5 The Prime Contractor shall work closely with the Government Contracting Officer and COR and shall have the responsibility to ensure that the Contractor’s performance meets all Government contracting requirements within cost and schedule. The Prime Contractor shall have the requisite authority for full control over all company resources necessary for the resulting BPA and Task Order performances and shall be available to support emergent situations. The Prime Contractor shall ultimately be responsible for the following: personnel management; onboarding; management of Government material and assets; and personnel and facility security. In support of open communication, the Contractor shall initiate periodic meetings with the COR. The Prime Contractor shall respond to email requests from the COR within 24 hours of receipt.
7.4 Performance at Government Sites
If any of this contract effort is performed at specified government facilities, the Contractor shall abide by Department of the Treasury Directive (TD) 71-10 regarding provisions for authorized entrance and exit at these facilities.
8.0 PERSONNEL SECURITY
8.1 Security Categorization
This Contract is categorized as unclassified at the High (Tier 4/BI) Risk Level. This Contract does have the requirement to issue Task Orders (/work/other identified method of requesting work). This Contract does not have Tasks that require different levels of investigations.
Contractors are required to comply with the Treasury Directive P 15-71, Treasury Security Manual in the handling, protection, and safeguarding of government information in their possession. The TD P 15-71 will be followed as it specifies Treasury-specific personnel, physical, industrial and information security policy, processes and requirements that apply to this contract.
Personnel security investigations conducted for access to unclassified or sensitive but unclassified (SBU) information will be initiated by Personnel Security, Office of Security Programs (OSP). The contract employees must have and maintain favorable background investigations at the High Risk level throughout the life of the contract. Contractor personnel who perform work on IT systems or applications will be required to obtain and maintain the appropriate investigation, adjudication or suitability determination commensurate with the information contained within the application or system.
8.2 General Security
Department of Treasury, otherwise known as the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .