1. Bari, 25.01.2017 Giorgos Androulakis
QAQC
Bari,
Giorgos Androulakis
23rd physical QAQC Meeting, , Bari.

2. QA/QC External review
QAQC external review meeting: Catania, 17/03/2016.
Reviewers:
Jim Haugen (IceCube Instrument Systems Engineer)
Stefano Cecchini (Former Antares Quality Manager)
Mario Musumeci (Former KM3NeT-IT Technical Manager)
Gene Massion (KM3NeT STAC member)
Review report (27/04):
++ action points and concerns
Our response was sent (07/11) and there was no further feedback .
Last STAC meeting: Satisfied with our QAQC system too.
“Overall this committee found the QA/QC processes developed for the project seem quite good.”
“(…) the overall QA/QC outcome for KM3NeT will only be as good as the rigor with which the processes are actually implemented on a day to day basis by the personnel at each of the integration sites.”
(…) Regardless of how good the formal QA/QC processes are and how well intentioned the personnel are, learning how to integrate a large quantity of sophisticated subsystems into a working submarine research system is a challenging task.”
23rd physical QAQC Meeting, , Bari.

3. QA/QC reinforcement I
Review: KM3NeT QA/QC system is adequate for ensuring quality in production;
ARCA-DU3 failure: Among others, reinforcement of QA/QC has been decided by the management team.
Approach: pragmatic, rather than industrial standards/ISO-certified, designed to be implemented in a few months.
QA/QC reinforcement actions:
Redefinition of the LQS’s role and further training
Reorganize the QAQC discussions in SC meetings
New NCR handling protocol
Refined rules for documentation & DB product registration
Train the Steering Committee (SC) to QAQC
Revive Risk analysis – perform FMECA
Finalize QAQC external review
Finalize quality forms integration with the DB
In situ quality inspections
23rd physical QAQC Meeting, , Bari.

4. QA/QC reinforcement II
Local Quality supervisors (LQSs): provide the link between QAQC management and production sites; they are physically able to spot local quality issues.
LQSs play a key
role in QC
Support of the Institute Board to the LQSs has been secured in the IB meeting in Noto.
Some LQSs were too busy. These were re-appointed.
Further training has been done in the regular quality meetings. For new LQSs, personalised Skype training sessions.
Physical meeting in Bari.
Report non conformities;
arrange shipments administration;
carry out quality forms administration;
perform periodic quality checks;
check compliance with documentation rules;
verify/help in DB product registration;
report on all the above to the QAQC management.
KM3NeT STAC Meeting, , Naples.

5. QA/QC reinforcement III
Irene, Daan, Andrea, Stefano, Emanuele: THANKS!
23rd physical QAQC Meeting, , Bari.

6. QA/QC reinforcement IV
QAQC discussion reorganized during SC meetings:
NEW NCR handling protocol:
Past:
One presentation that included a general QA/QC update plus reminders for pending NCRs/DCRs.
Currently:
Two presentations:
QAQC status update on the first day
Quality summary of the concurrent meeting (pending NCRs, DCRs, status of documentation etc.)
Improved NCR administration
Improved NCR
follow up
23rd physical QAQC Meeting, , Bari.

7. QA/QC reinforcement V Refined rules for documentation:
APPLICABLE documents:
Are approved after preparation
Contain a list of REFERENCE documents
Have to be followed exactly
Changes have to be approved by a DCR
Example: DOM Integration Procedure
REFERENCE documents:
Describe sub-procedures
Provide input for APPLICABLE documents
Are to be reviewed by subgroup coordinator
& reported to SC both when established
& when changed
Example: Optical network
All others:
Mainly working documents until they are promoted to REFERENCE documents
Videos, pictures, drawings, material from the development phase
Actions supporting the classification above:
Definition of applicable and reference documents for each sub-project;
List their cross-references;
New templates for app/ref documents & re-arrangement of GD folder structure;
Benefits:
All integration sites are using the same version of documents;
New versions of app/ref docs are reviewed by sub-project coordinators before distributing;
Easier to control changes in cross-referenced documents (procedures).
23rd physical QAQC Meeting, , Bari.

8. QA/QC reinforcement VI
Documentation: List of procedures has been defined
!! However, many documents are still under preparation.
23rd physical QAQC Meeting, , Bari.

9. QA/QC reinforcement VII
Refined rules for DB product registration :
Sub-project coordinators decide what information relevant to the products of their sub-project needs to be stored in the DB;
Assign PBS and UPI (if needed) & get TPM approval;
Producers (or receivers in case of external supply) register what is missing.
SC members include QA/QC in their presentations:
Treat all NCRs and DCRs which fall in their areas and propose solutions;
Check and approve all technical documentation meant to become of reference or applicable, including specifications;
Report on all things above, i.e.
Follow up actions for open NCRs/DCRs
Suggest closure of NCRs/DCRs
Mention the status of non-finalised documentation
to the SC in dedicated slides at each meeting.
23rd physical QAQC Meeting, , Bari.

10. QA/QC reinforcement VIII
New NCR template with 5 severity classes classification:
The severity of an NCR is defined by the sub-group coordinator and the LQS, on the basis of the risk register and experience.
Of course, as the NCR is followed up, its severity might change in the light of new findings.
23rd physical QAQC Meeting, , Bari.

11. QA/QC reinforcement IX
Quality forms – DB integration
In situ quality inspections
Quality inspections at production sites based on a checklist containing
Lab set up, specifications, ESD protection, storage etc.;
Hardware/software versions, products with expiration date;
Communication in case of NCRs/DCRs between technicians, local integration coordinators and LQSs.
& my experience from following the development of the DOM integration site in Athens from scratch.
Task: Quality forms (NCRs and SRSs in particular) are uploaded in the DB, parsed and then store their information in appropriate tables.
In products’ pages
Steps:
Develop the web interface for uploading, parsers, tables in the DB;
Include in the products’ page the location field and the OK/Not_OK flag;
Upload older forms (most of them are in different template/format);
Consistently upload all new forms.
Location field, extracted from the last SRS for a given product.
Location history, from all SRSs for a given serial #.
OK/Not_OK flag extracted from the most recent NCR.
23rd physical QAQC Meeting, , Bari.

12. Current status I LQSs are doing a better job
And sub-group coordinators care more for quality:
Two site inspections (Nikhef & Naples) have already been performed.
Risk analysis revival is ongoing
Increased interest, more questions;
increased participation to the quality meetings;
less or no mistakes in Q-forms filling/handling;
accelerated NCR opening;
closer NCR follow up;
SRSs regularly opened & uploaded to the DB
DB registration checking
Expected NCRs pending for long now opened
Quality reporting during SC meeting presentations
Sub-group meetings devote time to NCRs/DCRs
QA/QC discussion in SC according to the reinforcement plan.
Risk register updated using existent NCRs and feedback by the SC members.
New NCR template will be released once the DB web interface for uploading is ready.
Taskforce for initiating the failure mode propagation analysis has been defined.
FMECA is under discussion.
23rd physical QAQC Meeting, , Bari.

13. Current status II Quality forms – DB integration
KM3NeT DB web interface
DB web interface for quality form uploading
NB! Uploading to DB is can be used for debugging.
23rd physical QAQC Meeting, , Bari.

14. Current status III Quality forms – DB integration NCRs: SRSs:
Web interface for uploading tested & functional;
Uploading to be distributed to LQSs, timescale ~ March 2017.
SRSs:
Large number already integrated;
New SRSs consistently uploaded to the DB;
At least for new sites (e.g. Athens), all traceable products are contained in SRSs which are already on the DB.
once SRSs are integrated
Extract of a penetrator’s (PBS ) DB page.
23rd physical QAQC Meeting, , Bari.

15. Current status IV Quality forms – DB integration Querying:
Most queries are drop-down menus that are filled empirically.
23rd physical QAQC Meeting, , Bari.