Tender Specifications - ECHA - Europa

1.4 Description of the project organization, i.e. description of the structure of the different
teams participating in the project, approach to ensure effective interaction and collaboration
among the teams (including both the teams of the Contractor and of the Agency).
1.5 Description of the resource plan 22 . The resource plan should include the estimation of
person days of the contractor’s resources per profile (as listed in section 4.3) per work
package. The sum of all person days of the contractor’s resources should be equal to the
number of the person days as indicated in the section “Effort of contractor” of the scenario
below.
Special attention should be given to ensure that the project team will have the necessary
skills to successfully implement the requirements related to the portability of the plug-in of
eCHEM (as described in the scenario below).
1.6 The infrastructure plan (regarding the IT environments to be built both at the Agency
and at the Contractor’s premises), including also information about
• what environments will be built and for which purpose
• how the transfer of components among different environments (e.g. from a test to the
production environment) will be achieved
• infrastructure implementation schedule
Special attention should be given to tailor the infrastructure plan to ensure effective support
in production in parallel to the effective execution of the other project activities.
The structure/layout of the project plan document is to be defined by the Tenderer.
The proposed project plan must not be more than 25 A4 pages long (a paper sheet filled in with
content in both sides is considered as 2 pages and not as one page), written with Arial font, font
size of 10.
Scenario
This section contains a scenario that the Tenderer is required to consider and provide a
proposal for a project plan. This scenario will be used to assess the tenders during the
evaluation. It does not necessarily mean that the tasks mentioned in the scenario will be
requested by the Agency in one of the specific contracts. The scenario is imaginary and the
assumptions made do not necessarily reflect the reality.
It is noted that the scenario concerns all three lots, except where it is explicitly clarified that it
refers to a specific lot.
Objective
The objective is to implement the version 2.0 of the IT system eCHEM, while in parallel
supporting in production the existing version of eCHEM (v1.0).
Background information
eCHEM is a web-based IT system that allows the companies in the Member States to issue to
ECHA their dossiers describing the process they follow to asses the properties of the chemical
substances they use in their products.
The companies are obliged to comply with specific rules imposed by the related EU regulations.
22 See footnote 20
38