ECHA/2020/666  Annex 1 to Tender Specifications  Technical Specifications Restricted  45 (77) 4.6.2.2. Deliverables  4.6.2.3. Pricing  Table 10: Corrective maintenance deliverables (WP 6.2)  ECHA expects to select the level of Maintenance and Service requests that is relevant in  view of the projected activities over a period of 12 months and to be contracted yearly on  a fixed price basis. The expected level of activity is defined:  The contractor is expected to be flexible, i.e. in case the expected volumes for a month  P.O. Box 400, FI-00121 Helsinki, Finland | Tel. +358 9 686180 | echa.europa.eu  o Peak period  o High volume  o Medium volume  o Low volume  • Either at FWC666 level (covering all the products in scope the lot), or at a lower  level, e.g. distinguishing the Industry channel and the Data platform  • On yearly basis, using for each month in the year, one of the load as expected:  Deliverable  Description  Post-mortem / root  cause analysis  reports  Document produced after the resolution of a bug/incident in  production environment, explaining the issue and the actions  performed to address it, and the cause(s), in order to perform  the appropriate solution (i.e. if only a workaround is provided),  prevent future bugs/incidents of similar nature, and if not  possible, to improve the reaction and resolution time.  Workaround  procedures  Operation modes for workarounds and its complexity, in order to  ensure proper operation of the service while the appropriate  solution for a bug/incident is implemented.  Patch release notes  Release notes for the patch version(s)  Test reports  Covering unit tests reports, test coverage KPIs, and report of the  execution of end-to-end scenarios (feature files) in the QA  environment  Binary artefacts  packaged binaries of the application components in JAR, WAR,  Docker image, NPM or any other applicable packaging format,  deployed to the appropriate package repository manager at  ECHA.  QA Deployment  deployment of the patch(es) to the ECHA QA environment,  including, whenever relevant, statistics on new data volume,  average data increase per day, duration, amount of events  processed, impact of new development in overall load plan in  terms of time and volume, etc.  Production  Deployment  deployment of the patch(es) to the ECHA production  environment, for those distribution channels that mandate it,  including, when relevant, statistics on new data volume, average  data increase per day, duration, amount of events processed,  impact of new development in overall load plan in terms of time  and volume, etc.  Meeting minutes  Minutes of the audio, video or face to face meetings with ECHA  and other involved stakeholders, as well as any other meeting  on which the contractor participates, not covered under other  reports.