EBA欧洲银行-02.-Website-Clarifications-No2_9页_210kb

Open Tender Procedure Clarifications No. 2 Summary

Core Content

This document provides clarifications and answers to various questions raised by tenderers during the procurement process for the European Banking Authority (EBA) Website Services. The tender is identified as EBA/2016/02/COMM/SER/OP, and the clarification date is 27th May 2016. The main focus is on technical requirements, service level agreements (SLA), compliance with European InfoSec policies, and the tenderer's qualifications.

Main Views and Key Information

1. Liferay Version and Compatibility

• The minimum required Liferay version is 6.1.1 CE.
• Higher versions may be used, provided the contractor ensures full compatibility with the current EBA website.
• The use of different components (e.g., full-text search engines, databases) is allowed as long as compatibility is maintained.

2. Service Level Agreement (SLA)

• The maximum response time is 5 seconds, measured based on user experience.
• The 99.8% availability requirement is based on 24/7 service availability on a monthly basis.
• A 5% reduction in monthly service fees applies for each percentage point below the target availability.
• The 24-hour implementation delay applies to tasks not covered by a specific contract or purchase order, such as bug fixes and non-enhancement activities.

3. Enhancements and Functional Requirements

• Enhancements are to be carried out on a case-by-case basis.
• The contractor must ensure that all pending issues are closed before production, or provide a resolution plan for unresolved issues.
• Existing functionalities of the EBA website do not need to be redeveloped.
• The platform reflects the full functional requirement perimeter.

4. Infrastructure and Hosting

• The infrastructure can be hosted in a data centre or cloud, but the cloud must be physically located in the EU.
• The use of a software load balancer is acceptable if it meets the compatibility and availability requirements.
• Infrastructure specifications (CPU, RAM, disk size, PostgreSQL version, etc.) are detailed in Section C of the Terms of Reference and Section 5 of the Annex I Architecture Document.
• The pre-production environment can be an exact replica of the production environment, though no minimum hardware requirement is specified.
• Test and development environments can be set up without redundancy, but tenderers may propose redundancy if desired.
• All environments must have HTTPS enabled and be accessible from the Internet.
• Some external services may require a VPN connection for access.

5. Documentation and Compliance

• The DNS configuration for eba.europa.eu and www.eba.europa.eu is managed by the EBA/EU, not the DNS registrar.
• Unaudited accounts can be submitted if audited accounts for 2015 are not yet available.
• The average annual turnover should be related to website hosting, maintenance, and enhancement services.
• The IT Project Manager must have 3 years of experience in managing web implementation projects.
• The tenderer must provide CVs of at least 6 staff; more CVs are allowed, but the number of staff must meet the minimum requirement.

6. Contract and Payment Terms

• The contractor is responsible for procuring, setting up, and maintaining the EBA website.
• No reuse of existing servers/infrastructure is permitted from the current provider.
• The price revision logic is fixed and cannot be discussed.
• Certifications are optional but must comply with European InfoSec policies.

Summary of Key Points

Conclusion

The EBA has provided detailed guidance on the technical and contractual aspects of the tender. Flexibility is allowed in certain areas (e.g., Liferay versions, components, and infrastructure), but compatibility, compliance, and performance remain strictly enforced. Tenderers must ensure that their proposals align with the European InfoSec policies, maintain the required SLA, and provide the necessary documentation and staff qualifications.