The file's text, extracted by GovTribe without its formatting.
SCEIS Modernization - IV&V Services
Attachment A Deliverables List and Descriptions
Solicitation No. 5400027230
Table of Contents Deliverable List and Descriptions 2
Deliverable List and DescriptionsMonthly Deliverables play a crucial role in the early detection of any project areas going off-track. They are presented in a predictable monthly delivery format and shall not duplicate information contained in one-time deliverables except to the extent relevant to the monthly assessment report.
| Identifier |
| Deliverable Name |
| Description |
| General Timing or Phase |
| M1 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| January, 2025 |
| M2 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| February , 2025 |
| M3 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| March, 2025 |
| M4 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| April, 2025 |
| M5 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| May, 2025 |
| M6 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| June, 2025 |
| M7 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| July, 2025 |
| M8 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| August, 2025 |
| M9 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| September, 2025 |
| M10 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| October, 2025 |
| M11 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| November, 2025 |
| M12 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| December, 2025 |
| M13 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| January, 2026 |
| M14 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| February, 2026 |
| M15 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| March, 2026 |
| M16 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| April, 2026 |
| M17 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| May, 2026 |
| M18 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| June, 2026 |
| M19 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| July, 2026 |
| M20 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| August, 2026 |
| M21 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| September, 2026 |
| M22 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| October, 2026 |
| M23 |
| Monthly Risk Assessment Report |
| Evaluation of emerging risks from across the S/4 HANA Migration project. Identify risks and conduct a current assessment of health of the project against project deliverables, project plans, and schedule. The deliverables shall include, at minimum, an assessment of all workstreams that are part of executing a successful program against plan, updates on existing risks, emerging risks, assessments of risk potential impact on project objectives, and recommended mitigation strategies to ensure project success. An Executive Summary, Dashboard by workstream, and details with supportable evidence is expected. |
| November, 2026 |
One-time deliverables supplement the regular monthly deliverables and are designed to increase the depth and scrutiny of critical activities and phases of the project to verify its on-track status. Offerors may recommend additional deliverables as part of the response.
Overall Deliverables
| Identifier |
| Deliverable Name |
| Description |
| General Timing or Phase |
| R1 |
| Initial Comprehensive Assessment |
| This assessment will focus on an initial assessment of the Program with a focus on how prepared the Program is to succeed. This assessment shall, at a minimum, cover resource plans that describe clear roles and responsibilities across all parties noting any gaps in the plans, program plans, tools, methods, change management, and governance. |
| February, 2025 |
| R2 |
| Updated Comprehensive Assessment with Recommendations |
| This assessment shall build on the initial assessment but have increased depth and be updated to reflect new information since the first assessment. This deliverable shall include a detailed assessment of the Requirements Documentation (including the Requirements Traceability Matrix) to ensure clarity, completeness, testability, consistency, and stakeholder agreement with requirements. It shall include a heavy focus on recommendations for early action needed to increase the likelihood of a high-quality project delivered on time. Any updates to content in the Comprehensive Assessments (R1 and R2) shall be documented as part of the Monthly Risk Assessment Reports (M1-M24). |
| April, 2025 |
| R3 |
| Enterprise Readiness Verification Report |
| Report shall verify plans have been executed to ensure readiness of all State Agencies in all their uses of SCEIS as the ERP of the State. This includes agency user readiness (e.g., training, change management), agency interfaces and integrations, agency reporting, and any other impact to agencies discovered during the IV&V engagement. Report shall provide feedback as to the readiness of the State Agencies and any recommendations as to further actions that shall be taken to ensure agency readiness is achieved. |
| Plan and Design Phase |
| R4 |
| Operational Readiness Verification Report |
| Report shall include a comprehensive summary of the readiness of the SCEIS S/4HANA System, sustainment organization and provider(s), staff, customer support mechanisms including the hypercare period, and any other system, repository, provider, staff, governance, or organizational structure, process, or tool that is a dependency for a successful Go Live. This verification is largely internal to the SCEIS Organization and its partners. |
| Plan and Design Phase |
| R5 |
| Testing Plans Review and Verification Report |
| Comprehensive review and report of all testing methodology and plans including but not limited to parallel payroll, end-to-end, unit, and user acceptance testing. |
| Plan and Design Phase |
| R6 |
| Organizational Change Management and Communication Plans Review and Verification Report |
| Comprehensively assess and report on the strategies and plans for all Organizational Change Management activities (including Training), Documentation, and Communication. Assess the effectiveness of the approaches and plans for mitigating disruption and ensuring smooth adoption of the upgraded system. |
| Plan and Design Phase |
| R7 |
| Post-Production Support Plan Review and Verification Report |
| Comprehensively assess and report on all strategies and plans for post-production support activities (e.g.., hypercare support, system maintenance, Help Desk, incident handling). Assess the effectiveness of the approaches and plans for mitigating disruption and ensuring smooth transition into production and stable operating production system and services. |
| Plan and Design Phase |
| R8 |
| Go Live Readiness Verification #1 |
| This verification shall consider all aspects of the cutover from SCEIS ECC to S/4HANA in production and verify readiness of the system, customer support, operations and people that must work together for a successful launch. This report shall be detailed and include verification by workstream or category. The report shall include any recommendations for action needed where gaps or issues are present that could impact a successful Go Live. Assessment of the cutover/deployment, cutover/deployment testing, and backout plans shall be part of this assessment. Security and Compliance shall be included in this assessment. |
| Go Live minus 3 months |
| R9 |
| Go Live Readiness Verification #2 |
| This verification report will build on Go Live Readiness Verification #2 and provide a refreshed verification on Go Live readiness. Key to this report will be updates on recommendations made in Go Live Readiness Verification #1 and actions taken as well as feedback on the effectiveness of the actions taken. Assessment of the cutover/deployment, cutover/deployment testing, and backout plans shall be part of this assessment. Security and Compliance shall be included in this assessment. |
| Go Live minus 6 weeks |
| R10 |
| Go Live Readiness Verification #3 |
| This final Go Live Readiness Verification report will build on the first two and provide a refreshed verification on Go Live readiness. Updates on recommendations made in Go Live Readiness Verification #1 and #2 and actions taken as well as feedback on the effectiveness of the actions taken shall be included. Key to this report will be highlighting any remaining issues that could create Go Live success with recommendations for mitigation. Assessment of the cutover/deployment, cutover/deployment testing, and backout plans shall be part of this assessment. Security and Compliance shall be included in this assessment. |
| Go Live minus 1 week |
| R11 |
| Post-Implementation Review |
| This post-Go-Live assessment shall assess how the system (and supporting aspects) are performing post Go-live. This assessment shall provide overall findings and specific findings by each workstream. Included in this assessment shall be performance metrics and monitoring, issue resolution verification, user feedback, service desk operations, and all other aspects of the Go-live that could create significant impact the use of SCEIS for in State agencies, their partners, and by State employees. |
| Go Live + 2 weeks |
System-specific Deliverables
| Identifier |
| Deliverable Name |
| Description |
| General Timing or Phase |
| S1 |
| System Design, Configuration, Workflow Review and Verification Report |
| Conduct a comprehensive assessment that verifies the system design, configuration, and workflow meet requirements and produce a report. This assessment shall include an independent review of the architecture for scalability, reliability, and performance as appropriate, noting any challenges that other customers have had using the SAP RISE platform. This may involve reviewing plans, process flows, configuration management protocols including version control procedures, workflow design, and attending meetings or work sessions where this topic is discussed. Identify and report on discrepancies or deviations from the current system operations and whether changes to the system function, configuration, or workflow are required and being tracked and managed to ensure proper change management. |
| Plan and Design Phase |
| S2 |
| System Integration and Interface Review and Verification Report |
| Conduct a comprehensive assessment that verifies the system integration, and interfaces will meet requirements and produce a report. This may involve review of plans, integration lists, meeting with integration partners, and attending meetings or work sessions where this topic is discussed. Identify and report on discrepancies or deviations from the current system operations and whether changes to the integrations or interfaces are required and being tracked and managed to ensure proper change management. |
| Plan and Design Phase |
| S3 |
| Data Conversion/Migration Strategy Review and Verification Report |
| Review all data conversion strategy and plan documents and assess. Report on the assessment and include such areas as the completeness of the plan, how well it handles all data that needs to be converted (automated and manual conversions), unique use cases, the approach to handling data that fails conversion, the data conversion testing approach, environment usage, refresh schedules in coordination with project team needs, and number of test data conversions to be executed. Accuracy of data mapping and data conversion/migration testing shall be included. |
| Plan and Design Phase |
| S4 |
| System Security, Roles, Access, and Segregation of Duties Plan Review and Verification Report |
| Conduct a comprehensive assessment that verifies the security of the S/4HANA system, roles, access, and segregation of duties meet requirements and produce a report. This may involve review of plans, reviewing security policies and requirements, meeting with the CISO or their designee to understand requirements, and attending meetings or work sessions where this topic is discussed. Identify and report on discrepancies or deviations from the current system operations and whether known issues are being properly tracked and managed to ensure proper a secure system at Go Live. |
| Plan and Design Phase |
| S5 |
| End to End Testing Completion Report |
| Report shall provide a comprehensive description of the outcomes, findings, and assessment of the S/4HANA systems end-to-end testing phase. This report shall verify that the methods, execution, capturing and addressing of found issues, and system were executed and identify any gaps, issues, or risks that were detected in the end-to-end testing phase (both methods used and execution results). Report shall also verify that any issues found in End-to-End testing will be addressed before Go Live or have an effective mitigation plan that has or will be executed. |
| One week after completion of End-to-End Testing Phase effectively ends |
| S6 |
| User Acceptance Testing Completion Report |
| Report shall provide a comprehensive summary of the outcomes of UAT sessions and verify that system requirements and expectations are met. Where a system requirement or expectation will not be met, verification shall be included that those issues are documented and have a mitigation plan. Feedback from consuming agencies shall be included as part of this assessment. |
| One week after completion of User Acceptance Testing Phase effectively ends |
| S7 |
| System Design, Configuration, and Workflow Validation Report |
| Develop a validation report that comprehensively reviews the anticipated S/4HANA system against system design, configuration and workflow plans and process documentation to ensure alignment with plans and expected outcomes. The report shall reference the source documents that are assessed and note any gaps, issues or deficiencies uncovered in validating readiness for Go Live. Use of rigorous methods in the assessment is expected to ensure that difficult to find issues are surfaced. If any issues emerge in the assessment, recommendations shall be provided. |
| Testing Phase |
| S8 |
| Data Conversion Strategy Review and Validation Report |
| Develop a validation report that comprehensively reviews the data conversion process and testing results against the strategy and all plans and documentation. Validation of error rates associated with data that could not be converted and plans for the data conversion cutover shall be part of this assessment. Critical business tables that contain GL, demographic, employment and other critical data sources shall be verified as part of this process. |
| Testing Phase |
| S9 |
| System Security, Roles, Access, and Segregation of Duties Validation Report |
| Develop a validation report that comprehensively reviews the anticipated S/4HANA system against system security, roles, access and segregation of duty plans and process documentation to ensure alignment with plans and expected outcomes. The report shall reference the source documents that are assessed and note any gaps, issues or deficiencies uncovered in validating readiness for Go Live. Use of rigorous methods in the assessment is expected to ensure that difficult to find issues are surfaced. If any issues emerge in the assessment, recommendations shall be provided. |
| Testing Phase |
IV&V Project Management Deliverables
| Identifier |
| Deliverable Name |
| Description |
| General Timing or Phase |
| E1 |
| IV&V Engagement Kick- Off Meeting |
| Conduct a kick-off meeting that describes such things as the IV&V team, how they will work with the S/4HANA Project Team, the engagement approach, and outlines the first activities. Other relevant topics can be added. |
| November, 2024 |
| E2 |
| IV&V Engagement Plan and Associated Project Plan |
| Deliver an IV&V Engagement Plan and associated Project Plan. These plans shall contain sufficient detail to allow Executive and Project leadership to understand the approach, schedule, and time commitments related to the IV&V work. Included in this shall be a Stakeholder Engagement plan that clearly defines roles and responsibilities for the IV&V team and communication protocols the IV&V team will use with stakeholders. This Deliverable shall address, in detail, the automated tools and approaches that will be used to conduct testing including security testing. |
| December, 20254 |
image1.png