Bouw en beheer twee websites waarvan één met crisisfunctionaliteit

The contract is set to begin on December 1, 2026, and is scheduled to conclude on November 30, 2030, marking an initial duration of four years. The agreement includes an option for the client, IJsselland, to extend the contract twice, with each extension lasting two years, under the same terms and conditions. If an extension is utilized, the client must inform the contractor in writing at least three months before the current agreement's end date.

Key milestones related to the tender process leading up to the contract start date include:

• Publication of the tender on TenderNed: August 18, 2026
• Latest date for submitting questions for Memorandum of Information 1: September 1, 2026, 12:00 PM
• Answering Memorandum of Information 1: September 15, 2026
• Latest date for submitting questions for Memorandum of Information 2: September 24, 2026, 12:00 PM
• Answering Memorandum of Information 2: October 8, 2026
• Latest deadline for submitting bids: October 20, 2026, 12:00 PM
• Sending of the award decision: November 4, 2026
• Verification interview: November 18, 2026
• End of expiry period: November 24, 2026
• Start date of the Agreement: December 1, 2026

The core scope of work and statement of work summary for this tender involve the implementation and ongoing management of a System, including a Content Management System (CMS) and associated websites.

Key aspects and deliverables include:

• System Implementation: This encompasses the phased development of websites, establishment of test and acceptance environments, and related services, with a definitive planning and Go/NoGo moments to ensure the system is operational by June 15, 2027. Training is also a key component.
• Project Organization: The tender requires a detailed outline of the project team's structure, including roles, tasks, responsibilities, and internal collaboration, demonstrating how this setup will lead to the successful and timely realization, migration, and launch of the websites. Communication strategy during system development is also required.
• Content Migration: A comprehensive approach to content migration is required, covering inventory, migration to the new website structure, adaptation to new templates and navigation, content enrichment, optimization, merging, or rewriting, and ensuring the quality, completeness, and findability of content during and after migration, including the retention of search results.
• SAAS Services: The core of the agreement involves the provision of one or more SAAS-Diensten (SAAS Services), primarily the remote delivery of functionality through electronic means, which includes Support and Documentation.
• Implementation Plan: A detailed Implementation Plan, to be led by the supplier, covers project objectives, project organization, work distribution, required client involvement, necessary integrations (Koppelingen), the relationship with the existing Application Landscape, specific partial deliveries (milestones) with functional specifications, an overview of intended users, the implementation timeline, delivery methods for partial components, the acceptance procedure, and methods for data conversion and migration. It also outlines the responsibilities for development, test, acceptance, and production environments.
• Management, Services, and Contract Agreements: The contractor is responsible for the technical management, maintenance, security updates, availability, and continuity of the CMS. Regular (monthly) SLA reports are required, detailing availability, maintenance activities, performance, disruptions, resolution times, and any deviations from agreed service levels. An acceptance environment, separate from the production environment, must be provided and managed according to the OTAP process.