1 / 28

WP7 Summary: Development of QA-RA in KM3NeT

KM3NeT WP7 Meeting, Pylos (Greece), 16-18 January 2007:. WP7: RISK ASSESSMENT AND QUALITY ASSURANCE. WP7 Summary: Development of QA-RA in KM3NeT. R. Garaguso, M. Morganti C. Sollima INFN-University of Pisa. Contents. Roadmap Membership and activities performed Results

reden
Download Presentation

WP7 Summary: Development of QA-RA in KM3NeT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

  2. Contents • Roadmap • Membership and activities performed • Results • Future activities KM3NeT : Colaboration meeting

  3. RA road map QA road map • Deepstudy of the Project to identify the processes involved • RA Questionnaire • 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 • 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 • QAQuestionnaire • Implement QA • Development of a preliminary QA manual according to KM3NeT specifications WP7: QA & RA Program DIAGRAM KM3NeT : Colaboration meeting

  4. Membership • INFN (Stefano Cecchini) • NCSRD (Ioannis A. Papazoglou ) • CEA-Saclay (Frédéric Louis ) • IN2P3 (Laurence Caillat) KM3NeT : Colaboration meeting

  5. WPs cross-link • 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: twice per year KM3NeT : Colaboration meeting

  6. 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 KM3NeT : Colaboration meeting

  7. 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 diffuse the “Quality Culture” overall the WPs • Obtained a common standardisation by an integrated strategy among the different WPs. KM3NeT : Colaboration meeting

  8. 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) KM3NeT : Colaboration meeting

  9. Quality manual Documented procedures Work instructions Forms Quality plans Specifications External documents Records WP 7 QA activities: How to reach the goals KM3NeT : Colaboration meeting

  10. WP 7 QA activities: How to reach the goals IDENTIFICATION /TRACEABILITY KM3NeT : Colaboration meeting

  11. WP 7 QA activities: How to reach the goals • Macro Area • Process Analysis • Functional Analysis • Quality Control • Tools KM3NeT : Colaboration meeting

  12. WP 7 QA activities: How to reach the goals Macro Area – example (to be discussed) • Infrastuctures • Electronics • Software • Logistic • (Suppliers) KM3NeT : Colaboration meeting

  13. WP 7 QA activities: How to reach the goals Processes Analysis (1 of 2) Unit, Subunit, Element, Item (USEI) • Requirements • Specifications • Designs Prototype • Production Preproduction Production • Test (Including System) • Integration IN • Storage OUT KM3NeT : Colaboration meeting

  14. WP 7 QA activities: How to reach the goals Processes Analysis (2 of 2) Unit, Subunit, Element, Item (USEI) • Packaging • Transport Shore Operations • Deployment Off Shore Operations • Recovery • Suppliers • Interfaces KM3NeT : Colaboration meeting

  15. WP 7 QA activities: How to reach the goals Structural Functional Analysis Example Data Acquisition • Optical Module Power Supply Instrumentation Boa Anchor • Structural Layout Structural Interface Electronics Power Supply Data Acquisition • Connections Control • Software Structural (Interface and Cable) • Logistic Layout KM3NeT : Colaboration meeting

  16. WP 7 QA activities: How to reach the goals • Design • Suppliers Quality Control • Logistic • Production • Software • Acceptance • Storage • Integration • Test • Packaging • Delivering KM3NeT : Colaboration meeting

  17. WP 7 QA activities: How to reach the goals Tools Proposed Process • Flow Diagrams Logistic • Block Diagrams • Questionnaires • Audit • Software (Database, etc.) • Functional tree • Product tree KM3NeT : Colaboration meeting

  18. WP 7 QA activities: How to reach the goals 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 KM3NeT : Colaboration meeting

  19. WP7: RA Objectives & Road Map for KM3NeT • Objectives • Define the mission of the neutrino telescope in quantifiable terms; • Assess specific scenarios (sequences of events) that can lead to the inability of the system to perform its mission; • Assess the probability of each and every scenario. • 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. KM3NeT : Colaboration meeting

  20. WP7: Risk Analysis Actual Activities FMECA ANALYSIS Qualitative Example (related to PCC Rome Meeting Request) Analyzed Component : Optical Module Hypothesis: • OM into its environmental conditions (working life); • Components cant’be repair (MTBF=MTTF=1/λ) • Criticality Analysis is only qualitative and based on MIL-STD 1629 A normative ; • 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. KM3NeT : Colaboration meeting

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

  22. WP7: General RA Conclusion • Although Qualitative,Criticality Matrix focuses on : Possible Criticality, using color rankingfrom Red (unacceptable condition) to Green (acceptable without revision) Objects ordered by criticalities • 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 KM3NeT : Colaboration meeting

  23. 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 KM3NeT : Colaboration meeting

  24. 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 KM3NeT : Colaboration meeting

  25. WP7:RISK ASSESSMENT AND QUALITY ASSURANCE WE HAVE A DREAM: “Let us try” KM3NET WP7 Motto "Design Study for a Deep Sea Facility in the Mediterranean for Neutrino Astronomy and Associated Sciences” KM3NeT : Colaboration meeting

  26. WP7:RISK ASSESSMENT AND QUALITY ASSURANCE THANK VERY MUCH FOR YOUR KIND ATTENTION "Design Study for a Deep Sea Facility in the Mediterranean for Neutrino Astronomy and Associated Sciences” KM3NeT : Colaboration meeting

  27. WP 7 future activities • 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) • Deepstudy 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 & RAQuestionnaire (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) KM3NeT : Colaboration meeting

  28. Work plan: WPs cross-link WP1 • Project Management • Policy Statement • QA & RA Management • QAP and RA Development • Procedures (General) • Audit • Data Base of the Final Documents WP7 • QA & RA Interface • QC (Development and Application) • Procedures (General &/or Detailed) • Data Base of the Work Documents WPi KM3NeT : Colaboration meeting

More Related