R. Garaguso, M. Morganti C. Sollima INFN-University of Pisa KM3NeT WP7 Meeting, Pylos (Greece), January 2007: WP7 Summary: Development of QA-RA in KM3NeT WP7: RISK ASSESSMENT AND QUALITY ASSURANCE

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting2 Contents  Roadmap  Membership and activities performed  Results  Future activities

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting3  Deep study of the Project to identify the processes involved  RA Questionnaire  Functional Analysis  Functional Analysis of the processes  Division of the Project in Units, Sub-Units, Components and Elements  FMEA/FMECA standards and methodology study and analysis (process & project)  Implement FMEA/FMECA  Compensating provisions & remarks in RA deviations according to KM3NeT specifications RA road map  Deep study of the Project to identify the needed standards and normative for each process  Collection and selection of several suitable normative and standards (ISO CD-ROM)  Link between the different normative and standards and its applications  QA Questionnaire  Implement QA specifications  Development of a preliminary QA manual according to KM3NeT specifications QA road map WP7: QA & RA Program DIAGRAM

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting4

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting5 Membership  INFN (Stefano Cecchini)  NCSRD (Ioannis A. Papazoglou )  CEA-Saclay (Frédéric Louis )  IN2P3 (Laurence Caillat)

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting6 WPs cross-link  INTERFACE:  INTERFACE: it is proposed to have one QA/RA responsible for each WP and per country. He refers directly to the WP7  Steering Committee: -Representative of the partners of the WP7: C. Sollima, S. Cecchini, I.A.Papazoglou, Frédéric Louis, L. Caillat  WP7 Meetings:  WP7 Meetings: twice per year

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting7 WP 7 activities: Starting Point 1.) Deep study of the overall Project to identify the WPs’ links 2.) RA & QA activities are carried out in the framework of the KM3NeT Project:  to increase the knowledge about the submarine technologies and neutrinos detection (lesson learned from ANTARES, NEMO & NESTOR Projects) (meetings were done in Paris, Marseille, Aberdeen and Italy)  to prove the reliability of the RA & QA methodology (from the PCC meeting of October 2006, application to the on going project)  to identify the weakest points

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting8 WP 7 activities performed: QA  Analysis of the ANTARES project -QA should start with the design study to be ready for the production  Analysis of the NEMO project -Application of the QA and RA methodology developed to: Define and diffuseDefine and diffuse the “Quality Culture” overall the WPs Obtained a common standardisation by an integrated strategy among the different WPs.

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting9 WP 7 results Development of the QA applications for KM3NET  QA index  QA questionare  Plan activities form (preliminary)  Test form (preliminary) Development of the RA methodology for KM3NET  Plan of the activities (RA CDR)  Example of FEMCA (methodology) to the Optical module (Antares/NEMO-1)

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting10 Quality manual Documented procedures Work instructions FormsQuality plansSpecification s External documents Records WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting11 WP 7 QA activities: How to reach the goals IDENTIFICATION /TRACEABILITY Id. NoSpecification No Test No Procedure No Instruction No Registration No FormRisk indexBar Code (?)

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting12 1.Macro Area 2.Process Analysis 3.Functional Analysis 4.Quality Control 5.Tools WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting13 Macro Area – example (to be discussed)  Infrastuctures  Electronics  Software  Logistic  (Suppliers) WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting14 Processes Analysis ( 1 of 2 )  Requirements Unit, Subunit, Element, Item (USEI)  Specifications  Designs Prototype Preproduction Production  Production  Test (Including System)  Integration IN OUT  Storage WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting15 Processes Analysis ( 2 of 2 )  Packaging Unit, Subunit, Element, Item (USEI)  Transport  Recovery  Suppliers Shore Operations Off Shore Operations  Deployment  Interfaces WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting16 Functional Analysis Example 4.Software 5.Logistic Layout Structural Data Acquisition Power Supply 1.Optical Module Instrumentation Boa Anchor Structural Interface 2.Structural Layout Electronics Power Supply Data Acquisition Control 3.Connections Structural (Interface and Cable) WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting17 Quality Control  Suppliers  Production  Acceptance  Integration  Test  Storage  Packaging  Delivering WP 7 QA activities: How to reach the goals  Design  Logistic  Software

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting18 Tools Proposed  Flow Diagrams  Block Diagrams  Audit  Software Process Logistic  Questionnaires (Database, etc.) WP 7 QA activities: How to reach the goals  Functional tree  Product tree

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting19 Just to recall  QUALITY = Requirements definition  QUALITY ASSURANCE = To plan the actions to achieve the requirements defined  QUALITY CONTROL = Measurement of the results achieved with reference to the requirements defined WP 7 QA activities: How to reach the goals

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting20 WP7: RA Objectives & Road Map for KM3NeT Road Map Risk Analysis involves three major stages: Collect project/processes data; Assessment of the undesired consequences of a potential set of actions; Assessment of the probability that these consequences may obtain. Objectives 1)Define the mission of the neutrino telescope in quantifiable terms; 2)Assess specific scenarios (sequences of events) that can lead to the inability of the system to perform its mission; 3)Assess the probability of each and every scenario.

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting21 WP7: Risk Analysis Actual Activities FMECA ANALYSIS Qualitative Example (related to PCC Rome Meeting Request) Analyzed Component : Optical ModuleOptical Module Hypothesis: 1.OM into its environmental conditions (working life); 2.Components cant’be repair (MTBF=MTTF=1/λ)(MTBF=MTTF=1/λ) 3.Criticality Analysis is only qualitative and based on MIL-STD 1629 A normative ; 4.Objects Information are based on the available licterature (there are not yet available risk data). Goals:  Give remarks about possible test benchs development to simulate the Failure Causes put in evidence;  Focus on Risk parameters needed.

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting22 WP7: Risk Analysis Actual Activities FMECA ANALYSIS Steps  Explode the Objects under analysis in all its parts (through a filled Questionnaires)(through a filled Questionnaires)  Build up FMECA TABLE by using modified MIL-STD 1629 A worksheet worksheet  Put in evidence the relevant functions by logical flow diagramflow diagram  Brainstorming on potential failure modes, causes and effects  Allocate severity level and probability of occurrence using MIL- STD-1629 A reference tablesreference tables  Build Up “Criticality Matrix”“Criticality Matrix”  Give final remarks

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting23 WP7: General RA Conclusion 1.Although Qualitative, Criticality Matrix focuses on : Possible Criticality, using color ranking from Red (unacceptable condition) to Green (acceptable without revision) Objects ordered by criticalities 2.Although Qualitative, Criticality Matrix gives a priority to the objects tests (related to the failure causes) based on the above ranking Example of procedure after FMECA results: Step 1) rank Criticality level by unacceptable to acceptable Step 2) Calculate experimental MTBF from the worst to the better condition Step 3) Verify availability and find solution to improve, if is necessary

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting24 EXAMPLE OF FMEA WORKSHEET FORMAT ID N°ITEMFUNCTION FAILURE MODE EFFECTCAUSESOCC.DET. SEV. RPN COMPENSATING PROVISIONS REMARKS Actual activities : RA Tools (ex MIL-STD-1629A) ID N° ITEMFUNCTION FAILURE MODE CAUSES SEVERITY CLASS FAILURE EFFECT PROBABILITY (β) FAILURE MODE RATIO (α) FAILURE RATE (λ) OPERATIN G TIME (t) CRITICALITY INDEX I c REMARKS EXAMPLE OF FMECA (CA) WORKSHEET FORMAT BACK

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting25 FUNCTION SIGNIFICANTFUNCTIONNON-SIGNIFICANTFUNCTION YES YES YES YES NO NO NO NO DOES THE LOSS OF FUNCTION HAVE AN ADVERSE EFFECT ON SAFETY OR INTEGRITY OF STRUCTURE? DOES THE LOSS OF FUNCTION HAVE AN ADVERSE EFFECT ON OPERATIONS? DOES THE LOSS OF FUNCTION HAVE AN ADVERSE ECONOMIC IMPACT? IS THE FUNCTION PROTECTED BY AN EXISTING Project Management TASK? FUNCTION WP7: Significant Function Identification BACK

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting26 WP7: Risk Analysis Actual Activities FMECA Reference - Criticality Parameters Table BACK

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting27 Example “Optical Module” OM Support Optical Module Upper Hemisphere Lower Hemisphere Gel Cage PMT Base + 2 Boards Cable & connections Penetrator LED Data taken from NEMO / OM …… x y z NEMO TOWER “ITEM” Optical Module BACK

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting28 MTBF (Mean time between failures) Is defined by the expressions: 1.MTTF: Mean time to Fail 2.MTTR: Mean time to ripair 3.λ : Failure rate N.B: when the object can’t be repair (as in KM3NeT case) MTTR=0 It means: BACK

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting29 WP 7 results 1 of 2 The work performed outlines that for a correct application of the QA and RA, it is needed to develop in the design study:  Functional analysis  Definition of the requirementes  Definition of the technical specifications It means interaction with the WPs

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting30 WP 7 results 1 of 2 The QA/RA needs to define the reliability level to be reach. It is translated in:  Tests to be performed  Relation with the suppliers, which -Tests they should perform -Certificate they should release -Level of non conformity we consider acceptable  Definition of the preproduction and production specifications

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting31 WP7: RISK ASSESSMENT AND QUALITY ASSURANCE "Design Study for a Deep Sea Facility in the Mediterranean for Neutrino Astronomy and Associated Sciences” WE HAVE A DREAM: “Let us try” KM3NET WP7 Motto

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting32 WP7: RISK ASSESSMENT AND QUALITY ASSURANCE "Design Study for a Deep Sea Facility in the Mediterranean for Neutrino Astronomy and Associated Sciences” THANK VERY MUCH FOR YOUR KIND ATTENTION

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting33  Draft CDR contribution describing the standards and the quality evaluation method for all the Design Study procedures and initial results of the FMECA RA studies (16 month) -Deep study of the Project (July 2006) -Collection of several normative and standards (June 2006) -Selection of the suitable normative and its application (ISO) (May 2006) -QA & RA Questionnaire (May 2006) -Development of a preliminary QA manual (July 2006) -Preliminary Standard Data-Base model (June 2006) -FMEA/FMECA standards and methodology study (July 2006) WP 7 future activities

Pylos (Greece), April 2007 KM3NeT : Colaboration meeting34 Work plan: WPs cross-link  Project Management  Policy Statement Interface  QA & RA Interface  QC (Development and Application)  Procedures (General &/or Detailed)  Data Base of the Work Documents  QA & RA Management  QAP and RA Development  Procedures (General)  Audit  Data Base of the Final Documents WP1 WP7 WPi