CONTROL SYSTEM: RISK IDENTIFICATION AND MITIGATION PLAN Françoise GOUGNAUDJanuary 14th 21016

| PAGE 2 OVERVIEW OF THE CONTROL RISKS TABLE 3 items:  Management of the WP  Owner: ESS AB  Design and development  Owner: CEA-ESSI  These risks and issues have a high probability to occur  Tests and commissioning  Owner: CEA-ESSI

| PAGE 3 CONTROL SYSTEM MANAGEMENT RISKS CEA is the first stakeholder to implement the CS, CS in a learning curve phase  lost time & delay in delivery. ICS coming to Saclay to bring efficient support.

| PAGE 4 CONTROL SYSTEM MANAGEMENT RISKS ICS coming to Saclay to bring efficient support. CB based on the small company IOxOS, may be unable to support hardware during the whole time of project Find backup solution. CEA is the first stakeholder to implement the CS, CS in a learning curve phase  lost time & delay in delivery.

| PAGE 5 CONTROL SYSTEM MANAGEMENT RISKS ICS coming to Saclay to bring efficient support. CB based on the small company IOxOS, may be unable to support hardware during the whole time of project Find backup solution. Additional cybersecurity requirements. CEA is the first stakeholder to implement the CS, CS in a learning curve phase  lost time & delay in delivery. Cybersecurity requirements to set up rapidly: activate SELinux, firewall, higher security on PLCs, authentication on common computers.

| PAGE 6 CS DESIGN & DEVELOPMENT RISKS Not all the guidelines and specifications have been provided yet to CEA-ESSI:  reworks will be needed. « Baseline PS and LEBT CS design » has to be written by CEA and approved by ESS. Done for the Source.

| PAGE 7 CS DESIGN & DEVELOPMENT RISKS Late delivery of ESS partners devices or cabling  delay of integration for the Source. All the guidelines and specifications have not been provided yet to CEA-ESSI: -  reworks could be needed. « Baseline PS and LEBT CS design » has to be written by CEA and approved by ESS. Done for the Source..

| PAGE 8 CS DESIGN & DEVELOPMENT RISKS Late delivery of ESS partners devices or cabling  delay of integration for the Source. New technologies with mandatory and inherent updates may lead to issues in software installation. ICS has to have its own repository to stabilize the development environment. Not all the guidelines and specifications have been provided yet to CEA-ESSI: -  reworks could be needed. « Baseline PS and LEBT CS design » has to be written by CEA and approved by ESS. Done for the Source.

| PAGE 9 CS TESTS & COMMISSIONING RISKS Evolution in technology (VME to µTCA) or updates during tests may extend the duration of tests. Anticipate technology evolution (VME to µTCA) by using real test benches and stabilizing the software environment.

| PAGE 10 CONCLUSION  Currently the major risks for CEA are delays in CS deliveries for Source & LEBT  Action plan  Mission to Catania End-January  to start the CS installation  to get a status of the installation and cabling of the cabinets