ECHA/2020/666  Annex 1 to Tender Specifications  Technical Specifications Restricted  19 (77) The contractor is welcome to proactively provide feedback on how ECHA can be a better  partner and make a better contribution towards the success of FWC666 (see also  Continuous Service Improvement Process (WP 1.7)). With regard to the above, it is important to recognise that inefficiencies incurred by one  contractor (e.g. delays) will ripple down to the other parties downstream, implying that all  contractors must take adequate steps to address this risk. In addition, the optimisation of  integration costs is essential. Any inefficiencies related to integration management  between Contractors will result in an additional cost for ECHA and shall therefore be  anticipated and limited to the extent possible.  The Contracting Authority may request other parties to  review  deliverables submitted by  the FWC666 Contractors. See Consultation and specialised data services (WP 5.3) for  details.  In the context of this FWC666, the contractor will interact with other contractors ( outside  this FWC666) in the context of (non-exhaustive list): The contractor may set quality and compliance requirements, in agreement with the  Contracting Authority, for a task, an object or a delivery package that will be re-assigned  by other parties. The contractor has the right to refuse task assignments, if the criteria  are not met and this would render the correct service provision unduly difficult. This must  be done by assigning the task back to the sender, including a justification. In case of  dispute, the Contracting Authority will decide based on the justification entered within the  tools and may use justification provided directly by the contractor(s) through other  channels. In those areas where ECHA is using the services of DG DIGIT (European Commission), the  contractor will also interact with the relevant entities within DG DIGIT (European  Commission). In those areas where ECHA is providing services to other organisations, the  contractor will also interact with the relevant services of those organisations.  The contractor must regularly report (on monthly basis by default) to the Contracting  Authority with the objective to ensure contractual and operational follow up of the activities  under the FWC666.  As a general rule, ECHA may require reporting on any relevant aspect associated with the  delivery of services. Reporting requirements may be further elaborated in specific  contracts. Reporting might be revised periodically through the Continuous Service  Improvement Process. Run  operational reports are produced by the contractor ’s service manager and handed  P.O. Box 400, FI-00121 Helsinki, Finland | Tel. +358 9 686180 | echa.europa.eu  Reporting for RUN activities  4.1.2.1. Monthly service reports  4.1.2. Reporting (WP 1.2)  • The deployment and operational aspects of the Platforms and the bespoke related  software • Assessment, advice, control and integration of the services offered by all the  Contracting Authority Contractors and the Contracting Authority • Architecture aspects and design of the Platforms  • Integration of cross-platform capabilities, identification of design patterns and  synergies • Conformance testing activities