ECHA/2020/666  Annex 1 to Tender Specifications  Technical Specifications Restricted  63 (77) 6.2.2. Provision for electronic means of implementing specific contracts,  and ordering and receiving services  6.3. Acceptance procedure  6.3.1. Deliverable types  6.3.1.1. Method of delivering  6.3.1.2. Means of Acceptance  6.3.2. Acceptance of software  For all exchanges with the Contractor during the implementation of the FWC666 as well  as for future possible subsequent proceedings for the purposes of EDES (European Union's  Early Detection and Exclusion System) ECHA may use an electronic exchange system in  line with the requirements of Article 148 of Regulation (EU, Euratom) 2018/1046 of the  European Parliament and of the Council of 18 July 2018 on the financial rules applicable to  the general budget of the Union. At the request of ECHA the use of such a system shall  become mandatory for the Contractor(s) at no additional cost for ECHA. Details on  specifications, access, terms and conditions of use will be provided in advance. The Agency is planning to set up an electronic exchange system during the foreseen  duration of this Framework Contract. All exchanges with recipients, including the entering  into legal commitments and any amendments thereto, may be done through such system. In such an electronic exchange system, the Specific Contracts shall be implemented in an  electronic form. An electronic form of documents and exchange has no impacts to the  conditions of the contract or to the contractual terms.  This section describes the applicable acceptance procedures for different types of  deliverables.  Within this FWC666 ECHA specified deliverables are of different types of  nature , as  follows:  At the end of each specific contract (or at the end of each Subtask if requested by ECHA),  the contractor shall transfer the set of deliverables to ECHA in a manner compliant with  instructions that will be provided by ECHA. Typically, the contractor shall use remote  secure  connection and transfer the deliverables  electronically  and maximizing  automations, to ECHA repositories. All document deliverables will be in a format that is compatible with ECHA's way of  working. Amongst others, ECHA extensively uses Microsoft technologies (Office / Visio /  Project / SharePoint etc).  The default means of acceptance is described in the sections below. If the specific contract  applies a different way of acceptance, the specific contract will describe in detail the  acceptance procedure.  If not specified otherwise in a specific contract, the acceptance procedures described below  will be applicable for software deliverables.  P.O. Box 400, FI-00121 Helsinki, Finland | Tel. +358 9 686180 | echa.europa.eu  • Software deliverables (source code and deployment package, etc.)  • Services deliverables (e.g. application management)  • Other deliverables (e.g. documentation) 