Workflowbasierte Rechnungsverarbeitung

The contract timeline is as follows:

• Contract Start Date: The contract is concluded upon award. The implementation phase is set to begin on May 1, 2027. The five-year contract term officially commences from the end of the month in which the implementation, acceptance, and go-live (Inproduktionsnahme) takes place, but no later than October 31, 2027.
• Contract End Date: The contract has a total duration of five years. This five-year period begins at the end of the month of implementation, acceptance, and go-live, and no later than October 31, 2027. Therefore, the contract will end five years from this start date, which is no later than October 31, 2032.
• Total Duration: 5 years.
• Key Milestones/Phases:
• Project Plan/Detailed Concept Creation: Must be established in collaboration with the client no later than two weeks after the contract award.
• Test Environment Availability: A test environment with the intended functionality must be ready no later than eight weeks before the go-live.
• Implementation, Acceptance, and Go-Live: The full solution, including implementation, acceptance, and go-live, must be completed by October 31, 2027, at the latest.
• Operational Transfer and Stabilization Phase: This phase starts after the go-live, specifically no later than November 1, 2027, and will last for a minimum of three months.

The core scope of work for this tender, "Rebel-2026," is centered around "Workflowbasierte Rechnungsverarbeitung" (workflow-based invoice processing) for BARMER. The Statement of Work and core deliverables can be summarized as follows:

Transitionsphase (Transition Phase):

• Implementation, including tests.
• Training.
• Parallel operation for a minimum of two months, starting November 1, 2027.

Betriebsphase (Operational Phase):

• Lease licenses (production and test systems) including maintenance, support, warranty, and operational services.

Beratungsleistungen (Consulting Services - optional):

• Consulting services provided on a daily rate (remote).

Service Management Processes (explicitly included processes and activities):

• General Management Processes:
• Manage Governance.
• Manage Programs and Projects.
• Manage Knowledge.
• Support Service Portfolio Management.
• Continuously improve service delivery.
• Manage Service Control, Customer Experience, and Customer Satisfaction.
• Manage Remuneration and Finances.
• Manage Risks and Compliance.
• Service Lifecycle Management Processes:
• Design Processes:
• Maintain Service Catalog.
• Maintain Architecture Specifications.
• Coordinate Service Design.
• Capture and Review Service Requirements.
• Create Organizational Service Design.
• Create Technical Solution Design.
• Build Processes:
• Manage Change.
• Plan Releases.
• Create and Integrate Releases.
• Test and Validate Services.
• Deploy Releases.
• Support Release Introduction.
• Manage Configurations (CMDB).
• Operate Processes:
• Provide Service Requests.
• Manage Access.
• Manage Events.
• Monitor Services.
• Control Operations.
• Manage First Level Incidents.
• Manage Second Level Incidents.
• Manage Problems.
• Management on behalf of the client:
• Manage Third-Party Services.
• Manage Customer's Own Software Assets.

General Process Requirements:

• Manage Capacity.
• Manage Availability.
• Manage Information Security.
• Manage IT Service Continuity.

ITSM System Requirements:

• Service Integration.
• ITSM-Integration Layer.
• ITSM-Connector.
• Interface Definition.
• Field mapping for ITSM processes/practices.
• Software Asset Management.
• Configuration Management (CMDB).
• Hardware Asset Management (HAM).