The subject of the present procurement procedure is the procurement of the service for the integration and introduction of SAP S/4HANA (hereinafter: S/4HANA Core).
Further details can be found in Section II.2) and Annexes VB (Procedure Letter) and LA (Specifications).
Objective:
The currently used SAP ERP is to be transformed to SAP S/4HANA. The aim is to exploit the potential benefits of the new S/4HANA generation and to optimize and standardize historically grown processes, data storage and workflows. In addition, the new SAP General Ledger and successor solutions for the discontinued SAP SRM and SAP WM are to be introduced. In doing so, the Contractor shall be responsible for both the preceding technical and content-related conception as well as the IT-side implementation or carry it out independently. A concretization of the exact scope of services as well as the expectations placed on the Contractor is made in the specifications (Appendix LA) together with the associated systems.
Specifications:
The specifications outline the essential characteristics of the advertised services and define their scope as well as the basic requirements to be fulfilled by the Contractor, and thus form the substantive basis for the tender. It has the function of a service description (§ 28 SektVO) and describes the status quo, the change in the system landscape, the project organization and processing, technical requirements, requirements for consultant support as well as required offer contents. The complete specifications with all attachments will only be published after the participation competition.
Migration and project services:
The transformation project is divided into five phases.
Phase 1 – Project initialization and planning: The aim of this phase is to plan the transformation project in detail and to coordinate it between the AG and the CONTRACTOR. Furthermore, the measures for establishing the operability of the system and defining milestones, quality gates, the quality assurance measures accompanying the project are to be planned.
Phase 2 – Conception: The aim of this phase is the successful development of all content concepts that are necessary for the subsequent implementation phase. In addition to the technical description, they must also contain an implementation concept that allows planning at work package level.
Phase 3 – Implementation: In the implementation phase, the technical and implementation concepts of the previous phase must be realized. The goal is the appropriate and complete implementation while adhering to predefined guidelines (e.g. developer policy) and standard procedures.
Phase 4 – Go-Live: The go-live phase requires a successful acceptance test. The measures and activities are carried out in accordance with the CutOver plan. This phase ends with the successful go-live.
Phase 5 – Stabilization phase: Successful go-live is followed by a stabilization phase and includes the following activities: Correction of errors in productive operation and operational support in the operational application of the system ("coaching").
Delivery items/project services:
The project services are broken down as follows:
•Conceptual activities;
o Detailed technical concept E-2-E processes;
o Detailed technical concept for process-relevant structures & master data;
o Technical detailed concept supporting functions;
o Fiori and surface concept;
o Concept for handover to the company;
the Berechtigungskonzept;
the Geschäftspartnerkonzept;
the Datenmigrationskonzept;
o Integration and interface concept;
the Schulungskonzept;
the Testkonzept;
o Cut-Over-Plan;
the Dokumentationskonzept;
•Transformation;
o Customizing for E-2-E processes;
o Customizing for process-relevant structures & master data;
o Customizing for supporting functions;
o Interfaces;
o Permissions;
o Migrated data;
o Test cases;
o Training;
o AG in-house developments;
o Cut-Over & Go-Live Aktivitäten;
o Documentation;