Internet-Webdienstleistung

The contract timeline indicates that the provision of maintenance services begins on the date of the award ("Tag der Zuschlagserteilung"). The duration for these services can be indefinite, for a specific number of months, or for periods defined in Annex No. 1. For other services, the start date is either the day after acceptance ("dem Tag nach der Abnahme"), the day after the expiry of the limitation period for claims for defects ("dem Tag nach Ablauf der Verjährungsfrist für Sachmängelansprüche"), or a specific date. The duration for these services is specified in Annex No. 1.

Key milestones and phases are mentioned implicitly through the "Termin-, Leistungs- und Zahlungsplan" (schedule and performance plan), which is detailed either in a table or in Annex No. 1. This plan includes various types of terms such as "MS Meilenstein" (milestone), "BzA = Bereitstellung zur Abnahme" (readiness for acceptance), "BzTA = Bereitstellung zur Teilabnahme" (readiness for partial acceptance), "TA = Teilabnahmetermin" (partial acceptance date), and "VE = Vertragserfüllungstermin (Abnahme)" (contract fulfillment date/acceptance).

Explicit contract start dates, end dates, or total durations as concrete values are not stated in the provided documents, as these are referred to in Annex No. 1, which is not available.

The core scope of work for this tender involves the further development, maintenance, upkeep, and support of Reutlingen University's existing web presence, which comprises nine TYPO3-based websites (a central university website, six faculty websites, and two university-affiliated institution websites).

The key deliverables and responsibilities of the contractor include:

• Ongoing Development and Adaptation: Continuous further development and adaptation of the existing TYPO3 websites to meet current requirements.
• Maintenance and Upkeep: Performance of maintenance and upkeep tasks for the TYPO3 websites in ongoing operation, including TYPO3-Core-Minor-Updates as part of a monthly flat rate.
• Support Services: Providing support for the web pages, including a concept for ongoing operational support. This entails acting as a substitute for the university administrator for urgent support tasks, ensuring availability from Monday to Friday during usual office hours (e.g., 9:00-18:00 Uhr), and managing support communication via an agency-provided ticket system with specified reaction times for different urgency levels (High: immediately/max 4 hours; Medium: 8 hours; Low: 24 hours/next working day).
• Operational Readiness: Ensuring the existing TYPO3 CMS installation (based on current LTS releases with all necessary core-, third-party-, and custom-extensions) remains in an operational state.
• Infrastructure Management: Maintaining a containerized deployment environment (LAMP stack, preferably Docker-Compose or similar container orchestration), adhering to infrastructure architecture requirements such as using official/certified base images, strict separation of application code, configuration, and persistent data, externalization of configuration parameters, and ensuring reproducibility, portability, and easy backup/restore processes.
• License Management: Performing a license inventory (Software Bill of Materials - SBOM) for the standard software.
• Project Management: Participation in bi-weekly Jour Fixe meetings.

Content creation, page building, content filling within the CMS, and English translations are generally performed by the university's internal teams and are not part of the agency's primary responsibilities.