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 3
Validation in real operational environment
€ 975.000,00
2
€ 487.500,00
Milestones and Deliverables Phase 3
| M3.1 - Kick off meeting | ||
|---|---|---|
| The PBG shall present expectations on the planning and forecasted activities of Phase 3: planning testing in operational environment and project abstracts (in the format required by the EU for publication). Contractors shall present the operational deployment approach, testing methodology for the pilot sites, KPI validation strategy, interoperability arrangements, cybersecurity monitoring measures and operational support procedures. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.2 - Testing setup in operational site 1 | ||
| Finetuned plan for site 1. Contractors shall demonstrate deployment readiness, operational integration approach, KPI monitoring arrangements and cybersecurity measures applicable to the pilot environment. | Deliverable | Expected deadline |
|
D3.1 - Plan to test solutions in operational environments in 3 sites Testing plan finetuned and project abstracts (in the format required by the EU for publication). The deliverable shall additionally define operational deployment arrangements, interoperability validation methodology, KPI monitoring mechanisms, cybersecurity monitoring activities, operational data collection procedures and measurable technical outputs expected during operational testing. |
||
| M3.3 - Testing progress in operational site 1 | ||
| Progress and test results in site 1. Contractors shall provide measurable evidence of operational performance, interoperability validation, user interaction observations and cybersecurity-related monitoring results where applicable. | Deliverable | Expected deadline |
|
D3.2 - Interim report on finetuned plan for 3 sites Testing plan finetuned. The report shall include updated deployment arrangements, testing scenarios, integration validation activities, KPI monitoring strategy, operational support procedures and cybersecurity mitigation measures. |
||
| M3.4 - Testing progress in operational site 1 | ||
| Progress and test results in site 1. Contractors shall present updated operational testing results from Site 1, including service stability, user feedback, operational performance measurements and identified technical or cybersecurity issues. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.5 - Testing progress in operational site 1 | ||
| Progress and test results in site 1. Contractors shall provide consolidated testing updates for Site 1, including performance against operational KPIs, interoperability status and optimisation measures introduced following operational feedback. | Deliverable | Expected deadline |
|
D3.3 - Progress report of testing in site 1 Site 1 testing results. The report shall include operational testing evidence, KPI measurements, integration validation results, operational data logs and cybersecurity-related findings where applicable. |
||
| M3.6 - Testing setup in operational site 2 | ||
| Finetuned plan for site 2 Contractors shall present deployment readiness, operational integration arrangements, KPI validation strategy and cybersecurity monitoring measures adapted to the Site 2 environment. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.7 - Testing progress in operational site 2 | ||
| Progress and test results in site 2 Contractors shall provide evidence of operational performance, interoperability validation, service usability and cybersecurity-related monitoring outcomes where applicable. | Deliverable | Expected deadline |
|
D3.4 - Progress report of testing in sites 1 and 2 Progress on service testing results in sites 1 and 2 The report shall include comparative operational testing results, KPI achievement status, interoperability validation evidence, end-user observations, operational incident records and cybersecurity monitoring outputs where applicable. |
||
| M3.8 - Testing setup in operational site 3 | ||
| Finetuned plan for site 3 Contractors shall demonstrate readiness for deployment, integration validation status, operational KPI monitoring arrangements and cybersecurity measures for the Site 3 environment. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.9 - Testing progress in operational site 3 | ||
| Progress and test results in site 3 Contractors shall provide measurable evidence of operational functionality, interoperability performance, user interaction results and cybersecurity-related observations where applicable. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.10 - Testing progress in operational site 3 | ||
| Progress and test results in site 3 Contractors shall provide updated operational testing results from Site 3, including performance improvements, optimisation activities, identified issues and mitigation actions. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.11 - Testing progress in operational site 3 | ||
| Progress and test results in site 3 Contractors shall present consolidated operational testing outcomes for Site 3, including service stability, operational effectiveness, interoperability validation and cybersecurity-related monitoring outcomes. | Deliverable | Expected deadline |
|
No deliverables requested |
||
| M3.12 - Testing results in 3 sites | ||
| Online/site meeting with the PBG Progress and test results of 3 sites Consolidated progress and testing results from the three pilot sites. Contractors shall provide comparative analysis of operational performance, KPI achievement, interoperability validation, end-user feedback and cybersecurity monitoring outcomes across all operational environments. | Deliverable | Expected deadline |
|
D3.5 - Interim report on results of testing in 3 sites Report on testing results. The report shall include consolidated operational testing evidence, KPI measurements, end-user evaluation results, interoperability validation outputs, operational logs, identified residual risks and cybersecurity-related observations. |
||
| M3.13 - Final end of phase report and abstract (TD6) | ||
| The end of phase report should describe the work performed during Phase 3, 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. | Deliverable | Expected deadline |
|
D3.6- End of phase report and abstract (TD6) The end of phase report should describe the work performed during Phase 3, 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. |
||
| M3.14 - Summary of results | ||
| A summary of the main results achieved by each Contractor and conclusions from the PCP in the format required by the EU for publication. | Deliverable | Expected deadline |
|
D3.7 - Summary of results A summary of the main results achieved by each Contractor and conclusions from the PCP in the format required by the EU for publication. |
||
|
D3.8 - Lessons learned - report A deadline by which the Contractors must agree on the text for the summary of overall lessons learnt and results achieved from the PCP, for publication. |
||
|
D3.9 - Demonstration of services A final demonstration of the EU of the final products or services developed during the three phases. |
||
