RMV-KombiTicketsystem (Wallet, Mobil und Print@Home)

The contract comes into force with the award of the contract, and the obligation to provide services and the project itself begin immediately after the contract is awarded. The award decision is expected by October 30, 2026.

The initial contract duration is 48 months. The client has the right to extend the contract three times, each for an additional year.

Key milestones and phases include:

• Technical detailed concept including migration concept: November 2, 2026 – January 15, 2027.
• Setup of ticketing products and templates: November 23, 2026 – January 18, 2027.
• Implementation of any necessary additional developments: January 18, 2027 – February 26, 2027.
• Test operation with selected organizers: March 1, 2027 – March 30, 2027.
• Start of regular operation for all scenarios: March 31, 2027. The earliest possible start for all scenarios is January 18, 2027.
• Migration of prioritized ticketing service providers: April 1, 2027 – June 30, 2027.
• Migration of all other ticketing service providers: July 1, 2027 – November 30, 2027.

These dates represent the latest possible completion times, and the schedule can be adjusted earlier if tasks are completed faster, in consultation with RMV.

The core scope of work for this tender involves the conception, development, and operation of a provider- and user-based RMV-KombiTicket system delivered as Software as a Service (SaaS). This system is primarily for the issuance and administration of public transport travel authorizations, which are linked with event and service tickets.

Key components and deliverables include:

• System Development and Operation: The contractor is responsible for the overall conception, development, and continuous operation of the RMV-KombiTicket system. This also includes ensuring the system's secure, reliable, and permanently available operation, along with all associated services.
• System Components: The system must feature web access for RMV administrators, a web application, and appropriate interfaces to connect various event providers and ticketing service providers.
• Technology and Compatibility: The system requires a responsive user interface (UI) and must be compatible with Windows, macOS, iOS/iPadOS, and Android operating systems. Ongoing support for new versions and developments of these operating systems is also required.
• Infrastructure: The system's provision will be on the contractor's server, with the contractor ensuring highly performant computing power and sufficient storage and data processing capacity.
• Product Configuration: The system must be capable of initially setting up and storing all 23 specified RMV-KombiTicket products, which include templates for "return trips" and "period tickets" with varying temporal, spatial, and tariff parameters.
• Ticket Issuance: The system needs to issue and personalize public transport travel authorizations as VDV-Barcodes for use within the RMV, throughout Hesse, and across the tariff areas of RNN, VRN, and NVV. Personalization includes the first and last name of the user.
• Ticketing Provider Integration: The contractor must facilitate a straightforward initial connection for ticketing service providers, provide a final and regularly updated interface description, and conduct initial kick-offs with these providers.
• Migration Support: The contractor is also tasked with supporting an 8-month migration phase from the existing system to the new RMV-KombiTicketsystem.
• Documentation and Communication: A "Connection Recommendation" document, no more than 5 pages, must be developed and updated annually to guide ticketing service providers. Project communication, including system setup, changes, and extensions, must be handled through the RMV-Ticket-System (Jira) and be in German. Regular bi-weekly (before go-live) and monthly (after go-live) Jour fixe meetings via video conference are required for project reporting and coordination.