Processing
PCP #1
Call for tender of SHIELD PCP for the future Pre-Commercial Procurement of R and D services on the security domainTender information
€ 3.675.000,00
Product categories
73 - Research and development services and related consultancy services
Phase information Phase 2
Prototype development and integration
€ 2.250.000,00
3
€ 750.000,00
Milestones and Deliverables Phase 2
| M2.1 - Kick off meeting | ||
|---|---|---|
| Individual meeting with each Contractor to discuss the Phase 2 work plan, prototype development approach and project abstracts (in the format required by the EU for publication). Contractors shall present the prototype architecture, integration and interoperability approach, testing objectives, KPIs, cybersecurity measures and planned validation activities. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| D2.1 - Prototype and testing plan and presentation | ||
| Testing plan finetuned and project abstracts prepared (in the format required by the EU for publication. The deliverable shall additionally define prototype architecture, integration approach, testing methodology, KPIs, validation criteria, cybersecurity testing activities, data management approach and measurable technical outputs expected during Phase 2. | Deliverable | Expected deadline |
|
D2.1 - Prototype and testing plan and presentation |
||
| M2.2 - Progress update - monthly monitoring meeting | ||
| Contractors shall provide information on technical progress, prototype development status and planned activities, and inform about any delays, deviations from the plan and/or non-mitigated risks. Updates shall include measurable progress indicators, integration status, identified technical or cybersecurity issues and mitigation measures. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.3 - Progress update - monthly monitoring meeting | ||
| Contractors shall provide updated information on prototype implementation progress, integration activities, testing preparation and identified technical or cybersecurity risks. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.4 - Testing update | ||
| Contractors shall present preliminary test results, including prototype functionality, integration validation, performance observations and cybersecurity-related findings where applicable. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.5 - Progress update - monthly monitoring meeting | ||
| Contractors shall provide updates on prototype refinement, testing progress, integration status and identified deviations from the work plan. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.6 - Progress update - monthly monitoring meeting | ||
| Contractors shall provide information on prototype maturity, system stability, testing coverage and remaining technical risks. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.7 - Testing update | ||
| Contractors shall provide updated testing results, including performance against KPIs, interoperability validation and cybersecurity-related observations. | Deliverable | Expected deadline |
|
D2.2 - Prototype testing report Progress on prototype testing results. The report shall include technical testing evidence, integration validation records, prototype execution logs, KPI performance observations and cybersecurity-related findings where applicable. |
||
| M2.8 - Testing update | ||
| Contractors shall provide information on ongoing testing activities and demonstrate measurable progress in prototype validation. Evidence shall include updated test reports, interface validation logs, technical observations and cybersecurity testing outputs where relevant. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.9 - Testing update | ||
| Contractors shall provide consolidated information on testing progress, identified issues, mitigation measures and prototype performance against planned KPIs and use cases. | Deliverable | Expected deadline |
|
D2.3 - Prototype testing finetuning Progress on prototype testing results finetuned based on feedback and interim observations. The report shall include updated testing evidence, corrective actions implemented, revised validation results, integration updates and cybersecurity mitigation measures where applicable. |
||
| M2.10 - Prototype Testing Cycle (Spanish site) | ||
| Contractors shall deploy and test the prototypes in operational conditions at the Spanish site. Activities shall include validation of interoperability, operational performance, cybersecurity measures and compliance with the defined use cases and KPIs. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M2.11 - Testing update on optimisation of the solution off-site | ||
| Contractors shall provide information on optimisation activities performed following the pilot testing cycle, including corrective actions, system refinements, performance improvements and mitigation of identified issues. | Deliverable | Expected deadline |
|
D2.4 - Interim report on testing results Report on testing results demonstrating prototype maturity, interoperability validation, KPI achievement and cybersecurity-related outcomes. The report shall include structured testing evidence, data logs, system interaction records, performance measurements and identified residual risks. |
||
| M2.12 - End of phase | ||
| Testing report and planning for Phase 3. Contractors shall provide measurable evidence demonstrating the prototype performance achieved during Phase 2, including testing against use cases and KPIs, integration validation evidence, cybersecurity assessment results and identified residual risks. | Deliverable | Expected deadline |
|
D2.5 - End of phase report and abstract The end of phase report should describe the work performed during Phase 2, the results and a section that explains the IPR measures taken by the Contractors to protect the results and lists the names and location of personnel that carried out the R&D activities. |
||
|
D2.6 - End of phase report and abstract A summary of the main results achieved by each Contractor and conclusions from Phase 2 (in the format required by the EU for publication). |
||
| M2.13 - Prototype demonstration | ||
| A demonstration to the EU of the prototypes developed during Phase 2. | Deliverable | Expected deadline |
|
D2.7 - Demonstration A demonstration to the EU of the prototypes developed during Phase 2. The demonstration report shall document the demonstrated functionalities, testing scenarios, achieved KPIs, interoperability validation, cybersecurity features, and operational observations. |
||
