Transition sap erp hcm auf sap hcm for s/4hana (h4s4)

The contract timeline is as follows:

• Contract Start Date: February 1, 2027. The project is also proposed to begin in January 2027 with preliminary projects.
• Contract End Date: December 31, 2027. The productive use of the target architecture must occur by this date at the latest.
• Total Duration: Approximately 11 months, from February 1, 2027, to December 31, 2027.
• Key Milestones/Phases:
• Project beginning in January 2027 with preliminary projects.
• Go-Live of the H4S4 productive system in October 2027.
• A three-month Hypercare phase is planned following the Go-Live for system stabilization.
• The project phases include: Project Start and Initialisation, Conception, Preliminary Projects (Vorprojekte), Pilot Upgrade(s) and Test, Upgrade Phase, and Go-Live, Operation including Hypercare.

The core scope of work for this tender involves the transition of SAP ERP HCM to SAP HCM for S/4HANA (H4S4) and the replacement of SAP BTP Neo. The project aims for a Go-Live of the H4S4 productive system in October 2027, followed by a Hypercare phase. Existing functional processes and master data structures are generally expected to be retained.

The Statement of Work is structured across several phases, with key work packages and deliverables:

1. Project Start and Initialisation:

• Identification and setup of the project team.
• Definition of project approach, methodology, and communication.
• Development of project structure and milestone plans, including work packages, communication plan, and resource plan.
• Identification of organisational interfaces and coordination needs with parallel projects.
• Conducting a project kick-off.
• Deliverables: Project structure and milestone plan (including work packages, communication plan, resource plan), and a project handbook.

2. Conception:

• Project management and reporting.
• Preparation and conception of preliminary projects, including technical conversion to Business Partner, code adjustments, inventory of OData services, replacement of BTP Neo with BTP Cloud Foundry, and Fiori ESS/MSS conversion to BTP Cloud Foundry.
• Development of the upgrade concept.
• Creation of the project system architecture for H4S4, including DB RAM Sizing, AS vCPU, RAM, and SAN.
• Provision of SAP H4S4 licenses.
• Organisation and execution of workshops for functional and technical detailing of project requirements, and creation of workshop documents.
• Documentation of workshop results and creation of functional and technical specifications for necessary project adjustments.
• Provision of guidelines for roles and authorisations (e.g., release processes, job role descriptions).
• Review of the role and authorisation concept, and specification of roles and authorisations.
• Adaptation/extension of the instruction concept for IT application support and key users in ESS/MSS, including the procedure for end-user training.
• Development of a test concept, defining test cycles (e.g., Unit Tests, Integration Tests), provision of a test tool, and templates for test cases.
• Coordination with third-party service providers regarding interfaces.
• Specification of development requirements and an overview of interfaces and the system landscape (development, test, and production landscapes).
• Creation of a concept for the cut-over scenario for presentation and Go-Live.
• Acceptance of the concepts by MDC.
• Deliverables: Workshop presentations and documentation, functional concepts (including functional specification), technical specification and IT architecture, upgrade concept, test concept, and concept for cut-over scenario.

3. Preliminary Projects (Vorprojekte):

• Project management and reporting.
• Execution of preliminary projects (technical conversion to Business Partner, code adjustments, replacement of BTP Neo with BTP Cloud Foundry, Fiori ESS/MSS conversion to BTP Cloud Foundry).
• Provision of a Sandbox environment.
• Deliverables: Handover of preliminary project results, and written acceptance of the project phase.

4. Pilot Upgrade (Pilotupgrade):

• Project management and reporting.
• Execution of the pilot upgrade.
• Handover and test release.
• Test planning, test management, and monitoring of test results.
• Creation of test cases and test data.
• Execution of Unit Tests and Integration Tests (including S/4HANA <-> H4S4), performance and load tests.
• Implementation of necessary adjustments based on test results.
• Creation of a decision document for release.
• Deliverables: Documentation of final monitoring of test results, decision document for release, and written acceptance.

5. Upgrade Phase:

• Project management and reporting.
• Management of upgrade development, quality assurance, and productive system.
• Quality assurance of upgrades (Dev, Qas, Prod).
• User and authorisation maintenance for the productive system environment.
• Planning and scheduling of end-user training.
• Creation of training materials for end-user training.
• Execution of end-user training.
• Setup of the productive environment (e.g., importing transports, performing manual cut-over activities).
• Execution of a "Smoketest".
• Acceptance by the data protection officer, IT security, and auditors.
• Acceptance by MDC.
• Deliverables: Upgrade and cut-over procedure, documentation of Smoketest results, and written acceptance including release for commissioning.

6. Go-Live, Operation including Hypercare:

• Project management and reporting, including cut-over management.
• Commissioning of the H4S4 system and handover to MDC.
• Execution of HyperCare activities, including support for users and system operation, and stabilisation and optimisation of the H4S4 system.
• Consulting for processual and organisational adjustments.
• Handover to the operational process.
• Acceptance by MDC.
• Deliverables: Cut-over documentation, necessary input for other MDC documentation, and acceptance of the overall system.