Reliability Applied to KM3NET

Slides:



Advertisements
Similar presentations
Operation & Maintenance Engineering Detailed activity description
Advertisements

Software Quality Assurance Plan
Medical Device Software Development
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
Mission Success Starts With Safety GSFC Electrostatic Discharge (ESD) Control Program Are you plugged in? Jeannette Plante, Program Manager, Code 300.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
SAE AS9100 Quality Systems - Aerospace Model for Quality Assurance
C.Sollima INFN - University of Pisa for the KM3NeT Consortium “Quality Assurance and Risk Assessment in the KM3NeT Neutrino Telescope Design Study” Technical.
Stepan Potiyenko ISS Sr.SW Developer.
10/25/2001Database Management -- R. Larson Data Administration and Database Administration University of California, Berkeley School of Information Management.
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
Copyright © 2006 Software Quality Research Laboratory DANSE Software Quality Assurance Tom Swain Software Quality Research Laboratory University of Tennessee.
Overview of Software Requirements
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
20 February Detailed Design Implementation. Software Engineering Elaborated Steps Concept Requirements Architecture Design Implementation Unit test Integration.
Oracle Database Administration. Rana Almurshed 2 course objective After completing this course you should be able to: install, create and administrate.
Functional Testing Test cases derived from requirements specification document – Black box testing – Independent testers – Test both valid and invalid.
10/5/1999Database Management -- R. Larson Data Administration and Database Administration University of California, Berkeley School of Information Management.
Configuration Management Process and Environment MACS Review 1 February 5th, 2010 Roland Moser PR a-RMO, February 5 th, 2010 R. Moser 1 R. Gutleber.
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Configuration Management, Logistics, and Universal CM Issues Larry Bauer Boeing Commercial Airplanes NDIA Conference Miami March 4-5, 2005
Introduction to ISO New and modified requirements.
Introduction to Software Quality Assurance (SQA)
INFORMATION SYSTEM APPLICATIONS System Development Life Cycle.
Standard WBS Version 1.0 WBS2-3.pptPage 1 Standard Work Breakdown Structure Legend = Decomposes to lower level WBS elements 4.0 Implementation 4.0 Implementation.
Information Systems Security Computer System Life Cycle Security.
Software Quality Assurance Activities
From Research Prototype to Production
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Software System Engineering: A tutorial
Water | Slide 1 of Water for Pharmaceutical Use Part 3: Operational considerations Supplementary Training Modules on Good Manufacturing Practice.
What is a life cycle model? Framework under which a software product is going to be developed. – Defines the phases that the product under development.
1 Configuration Management “The Cookbook Approach”
VST: dome THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS Ing. Davide Fierro THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS.
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Installation and Maintenance of Health IT Systems
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
SJDEVLA Advisory Committee Meeting September 6-7, EVLA Production and Maintenance Steven Durand presenting for the E lectronics Division.
Important informations
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
Georgia Institute of Technology CS 4320 Fall 2003.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Archival Workshop on Ingest, Identification, and Certification Standards Certification (Best Practices) Checklist Does the archive have a written plan.
WGISS /09/2015 DATA PRESERVATION – CNES APPROACH B. Chausserie-Laprée.
1 DISTRIBUTION A. Approved for Public Release; Distribution Unlimited. 88ABW , 23 May Integrity  Service  Excellence ADT 101: Introduction.
Safety-Critical Systems 7 Summary T V - Lifecycle model System Acceptance System Integration & Test Module Integration & Test Requirements Analysis.
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
Over View of CENELC Standards for Signalling Applications
File that defines the basic organization of a database. Contains a list of all files in the database number of records in each file Names and types of.
Software Engineering Lecture 8: Quality Assurance.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
C.Sollima INFN - University of Pisa for the KM3NeT Consortium “Quality Control Considerations for the KM3NeT Very Large Volume neutrino Telescope” The.
11T Quality Assurance O. Housiaux, R. Berthet, S. Menu, R. Principe 3rd International Review on the 11T dipoles at collimator Section for the HL-LHC 6-8.
Medical Device Software Development
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Accelerator Readiness Review October 31, 2006
Supportability Design Considerations
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Chapter 11: Software Configuration Management
Fides and RAMS training Km3Net
Oracle Database Administration
IEEE Std 1074: Standard for Software Lifecycle
Release Management Release Management.
Chapter 11: Software Configuration Management
Quality by Design (QbD)
HART Technologies Process Overview
PSS verification and validation
DOE Review of the LCLS Project October 2006
Machine Protection PLC Based System Verification and Validation Plan
Presentation transcript:

Reliability Applied to KM3NET S.Colonges CLB meeting 30/01/2014

Who am i? Stéphane COLONGES APC Laboratory Electronic Product Assurance Manager Activities: Support engineering to improve reliability Components & system qualification Projects: Auger Observatory (1830 boards in harsh environment) Space projects: Taranis, SimbolX, R&D anti-coïndidence CTA observatory (QAM)

Table of contents Development process Reliability for KM3net - Reliability analysis My contribution Conclusion

Development process V Cycle

Concept of operation Product definition (scientific needs) Think Needs before solutions! - Constraints (environment, life cycle, maintenance, costs…)

Requirements and architecture -Requirements (functional, performances, environmental, RAMS…) -Functional analysis (SADT method) -Applicable needs -PBS

Requirements and architecture -FMECA (using tools like FTA and RBD) Avoid SPF, reduce failures criticism  Iterative process!

FMECA 8

Good conception = high reliability Design Good conception = high reliability Parts selection, consider: - Obsolescence (Vs LTA) , maturity, wide distribution - Environment: temperature, ESD, salt, humidity… - MTBF (FIT) - ROHS Vs Whiskers? - Improve reliability ( Derating - ECSS-Q-ST-30-11C, redundancies, ESD protections, ESR compromise…)

Design Reliability analysis - MTTF : - Acceptable failure rate? - Spare quantities - FMECA (identify failure modes and reduce effects). Iterative process: Identify the weakness points Identify failure type and process Change the design to improve reliability

Design Critical Design Review: -Definition justification document - Objectives: -Validate the detailed product conception -Prototype analysis and test results -Check the product conformity with the specifications - Documentation: -Definition justification document -Manufacturing files, procedures and documents -RAMS plan and FMECA (Reliability analysis) & MTBF evaluation -Interfaces Control Document -Preliminary user guide

Pre-production (Detailled design) -Goal: -Produce a small quantity of boards, update the design to production process, design hardening -Industrialization: -PCB rules (IPC2221… IPC600…) -Manufacturing and soldering processes -Manufacturing test and inspection (In situ tests, test bench…) -HASS procedure (eliminate youth failures) -Environment protection (coating, ESD suppressor…) -Storage, packaging, handling…

Pre-production (Detailled design) -Production Readiness Review: -Manufacturing sub-contractor, public tender…(instructions, CCTP…) -Industrial files

Production (Implementation) -Dividing in batches, allow to: -Detect weakness point (PCB layout, production process) -Change layout or production process (non conformities correction) - Configuration follow up : -Non conformities taken into account -Modification taken into account -Document folder: customer/sub contractor use the same files and document version

Installation (Integration, test and verification) -Installation procedures: -10% of failures = human error -ESD and lightning protection -Test bench (laboratory) -Test facilities (to test systems on the site before installing lines)

Commissionning (System verification and validation) -Verify functions and performance according to requirements -Parameters useful for failure detection correctly monitored -Monitoring software (easy abroad parameters access)

Operation and maintenance - Evaluate maintenance resources (spares quantities, costs, people…) - Recovery procedures - Update FMECA and MTTF: iterative update using experiment feedback (failures data collection) - Database - Record maintaining activities - Local staff training

Reliability for KM3net How to jump on the bandwagon? Requirements and functional analysis MTTF analysis and FMECA Verify design rules (Derating…) Documentation Review Then next steps (pre-prod, Production, …)

Reliability analysis - Tools 26/04/2017 Reliability analysis - Tools 19

26/04/2017 FIDES - Based on failure physics and calibrated with test feedback and field failure data 20

 MIL-HDBK-217 is not maintained since 1995 FIDES Begins 26/04/2017 Why FIDES ? Reliability Data book prediction are obsolete! (don’t cover actual component technologies)  MIL-HDBK-217 is not maintained since 1995 FIDES  Funding in 2001 by DGA (French DoD) and 8 international companies (+ BOEING, JAXA, CNES, CNRS… interested) Handbook and tools : www.fides-reliability.org 21 21

FIDES 26/04/2017 Based on physics failure , accelerating factors and process contribution: 22 22

MTTF / Bath tub 26/04/2017 23

My Contribution Reliability guidelines (in google doc) 26/04/2017 Reliability guidelines (in google doc) CLB MTTF evaluation Help for the other boards FIDES Quickstart guide Help for CDR and support for preparing production 24

Conclusion People should be aware on QA added value! 26/04/2017 People should be aware on QA added value! Your collaboration is necessary Keep in mind: reliability is an iterative process … And 2 other words : Brainstorming and workgroups… 25

More slides… 26/04/2017 26

FMECA An iterative process 27

Methodology 28

Reliability analysis - Methodology 26/04/2017 29

MTTF / Temperature Composants optiques : 0.8 eV 26/04/2017 Composants optiques : 0.8 eV Bipolar Ics, transistors, diodes : 0.7 eV MOS ICs : 0.6 eV T1: normal temperature (related to the FIT) T2: new temperature 30

FMECA 31