Amazon Web Service (AWS) -pilvipalveluiden hankinta 31.7.2026

The contract becomes effective upon signature by both parties, provided the Procurement Agreement is also in force. The contract is valid indefinitely. It remains in effect until all contractual obligations are met or until it is terminated or canceled. The Client has the option to terminate the contract with a six (6) month notice period, while the Supplier has a nine (9) month notice period.

Key milestones and phases include:

• The delivery project must commence no later than three months after the agreement becomes effective.
• The system is required to be fully operational in production within 10 months of the delivery project's commencement.
• The project concludes once the Client has approved the delivery in accordance with the "Implementation and Commissioning Plan."
• For phased deliveries, interim acceptance inspections are carried out within seven (7) working days after the supplier delivers an intermediate result and notifies the client.

The core scope of work for this tender primarily involves the procurement of public cloud services, specifically Amazon Web Services (AWS). This encompasses IaaS, PaaS, and SaaS service models, along with other similar public cloud service forms and Marketplace services. The tender also includes support and maintenance services for the public cloud, as well as expert and training services. Furthermore, the scope extends to new services developed by the supplier or public cloud provider that leverage artificial intelligence to enhance existing services or improve data security. The supplier's responsibilities include providing services like reporting, order management, and other related administrative and operational tasks as defined in the agreement.

Deliverables and project content are detailed in the project plan and procurement agreement, which specify the outcomes to be handed over to the client and/or end-customer. The tender also requires a service description outlining mandatory and optional service modules, service content, and related processes such as ordering, user management, customer support, changes, and service termination. This description must also cover supporting systems and tools. Additionally, a description of the system, solution, and technical architecture is required, covering aspects like general overview, user rights, integrations, scalability, fault tolerance, data security, continuity, recovery, implementation, testing, and maintenance.