Tender Specifications - ECHA - Europa
Tender Specifications - ECHA - Europa
Tender Specifications - ECHA - Europa
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Other tools: XML editors (e.g. XML Mind), JMeter, UIbinder, jReport, PrimeFaces<br />
During the execution of a specific contract, it is the Contractor’s responsibility<br />
(a) to make available the licences for the afore-mentioned tools that may be required to be<br />
used for setting up the development and test IT environments in the Contractor’s premises<br />
and<br />
(b) to install and configure the hardware and software needed in order to timely prepare the IT<br />
environments that must be setup at the Contractor’s premises during the implementation of<br />
the specific contracts.<br />
The Agency has the right to ask from the Contractor to use the latest version of any of the aforementioned<br />
tools.<br />
The Agency has the right to ask from the Contractor to use any other Open Source software or<br />
other free software tools.<br />
The <strong>Tender</strong>ers are required to provide a list of additional software tools that, if they are awarded a<br />
contract, they will make available free of charge for use in the IT environments built in their<br />
premises for the implementation of a specific contract.<br />
For this purpose, the <strong>Tender</strong>ers are requested to use the template of annex 5.14<br />
4.2.5 Tasks/activities<br />
The tasks/activities to be carried out by the Contractor as well as the relevant deliverables are<br />
described in the following sections. The description is indicative and non-exhaustive. The detailed<br />
list of the deliverables will be defined in the specific contracts.<br />
In most cases, the implementation of a specific contract will be organised in three work streams<br />
(which can be partly overlapping):<br />
• The takeover work stream<br />
• The support, maintenance and development work stream<br />
• The handover work stream<br />
<strong>ECHA</strong> will also define the extent to which these work streams will be followed (e.g. if a new specific<br />
contract starts to continue the work of a previous specific contract of this framework contract,<br />
<strong>ECHA</strong> may decide to skip the takeover work stream if the project team of the Contractor is the<br />
same in both specific contracts).<br />
During the execution of all work streams, the Contractor will ensure resource availability to cover<br />
the role of a Senior Architect (with skills of a Senior Architect, according to section 4.3.7) that will<br />
work with <strong>ECHA</strong> staff to ensure the work being executed by the Contractor is in alignment with the<br />
overall enterprise architecture of the Agency. The details of the work of this Architect will be defined<br />
in a specific contract.<br />
4.2.5.1 The takeover work stream<br />
Some or all of the following aspects of the work will be provided by <strong>ECHA</strong> during this work stream<br />
• Guidance to set up the development and testing environments<br />
• Decisions on the development tool chain and development related repositories<br />
48
Change language