Collaborating for Quality Quality Assurance (QA) & Quality Control (QC) in the Accelerator Project (ACCSYS) Matthew Conlon ACCSYS QA/QC 20 April 2016

ESS Quality: Q Div and Project QA/QC 2

Contracts Technical Reviews Quality Plans …means that the Stakeholders, ESS and its Partners, engage and work together to deliver high quality products, the most important of which are the equipment systems and components of the ESS operational facility. We engage through: Contracting Quality Planning Technical Review Collaboration for Quality 3 assuring and controlling QUALITY in Work and Products

Contracting for Quality Types of contracts: ESS procurement Supply Agreements and their SoW, specs, etc. IKC Agreements and their ‘Schedules’ a.k.a Technical Annexes (TA), other collaboration agreements Quality activities in making contracts: consultation during the development of contracts assures value and integrity of the SoW and related docs: – Ts & Cs, technical requirements, specifications, reference design – ESS MS documents including ESS processes and templates conducting internal Quality review with Accelerator’s Internal stakeholders: – WP teams, planners, Safety and specialty engineers 4

Planning for Quality Developing and agreeing the Project Quality Plan (PQP) … a graded approach, tailored for the scope and for the needs and capabilities of ESS, Partners and their sub- partners. … made through discussions, visits and other collaborative activities: … delivered via a succession of drafts in the data packages for Technical Reviews 5

Purpose of a Project Quality Plan 6 PQP Partner ESS PQP serves as a link and covenant between Partner and ESS PQP is an agreed plan addressing activities necessary to secure high quality work, and to secure high quality deliverables - especially the components and systems products PQP is developed, negotiated and approved jointly by both Parties before manufacturing starts QUALITY in Work and Products

ESS - ISO Template ESS has developed a PQP template for guiding ESS and partners for QA and QC. 7 based on ISO 10005: “Quality management systems (ISO 9001) - guideline for Quality plans” all headings should be addressed / referenced Partners with certified management systems may use their own templates and formats ESS PQP

Contents Scope Quality Goals Management responsibilities Documentation and storage Control of records Resources Requirements Customer communication Design and development process Purchasing Production and service provisions Customer property Preservation of product Control of Non-conforming product Identification and traceability Monitoring and measurements Audits Implementation of the PQP 8 Scope Describe the purpose of the PQP, identify what products and define ‘quality’ applicable for them, and how Quality in general to be achieved through Quality planning in this project i.e. introduce the Quality Goals. Describe the specific aspects of this particular Project and any limitations or delimitations, certain conditions that affects the validity of the PQP – what organisations and what products does it apply for, which stages of work or timeframe Documentation and storage Describe how the PQP, its supporting references (Partner’s QMS), and especially the document deliverables of the Project: are identified/named; the responsibilities/identities for authors, reviewers and approvers; and are distributed, stored and maintained. Non-Conforming products Describe how non-conforming products, primarily in the realised components and system deliverables of the Project, are identified, and how their non-conformance is tracked, communicated, and resolved. PQP Content

Quality through Technical Reviews Technical Reviews facilitate: hands-on collaboration between ESS and partners risk identification and sharing governance of the contracted SoW and its stages configuration management through baselines product Acceptance - transfer of ownership Technical Reviews progress through the stages of: Design ‘Realization’ – procurement, manufacture, pre-and post- delivery verification including inspections and testing Installation, Commissioning and Initial Operations 9

Types of Technical Reviews Design Reviews, for example PDR CDR Readiness Reviews, for example Production RR Integration or Assembly RR TRR Accelerator RR ORR System Acceptance Reviews: SAR 10

Contracts Technical Reviews Quality Plans Collaborating for Quality questions? discussion recommendations? 11 assuring and controlling QUALITY in Work and Products

BACK-UP Slides Contracting for Quality - IKC Agreements IKCA Schedules also known as Technical Annexes: Chapter 1. SCOPE summary Chapter 2. RELATED DOCUMENTS for the Schedule: – 2.1 contractually Applicable documents: requirements, specs., reference design etc. – 2.2 Reference documents for guidance Chapter 3. TERMS AND DEFINITIONS 12

BACK-UP Slides Contracting for Quality - IKC Agreements Chapter 4. PROJECT DEFINITION i.e. defining the work to be done and the deliverables – 4.1 Deliverable Item Definition: an executive summary of deliverables, time schedule and value of work – 4.2 defining the work Stages in executing the scope: Design: activities, review and other milestones, tech. data packages Realization and Verification i.e. procurement, manufacture, pre-and post-delivery verification including test. support for Installation, Commissioning and Initial Operations – 4.3 defining the Project time Schedule and Key Milestones – 4.4 defining the Deliverables 13

BACK-UP Slides Contracting for Quality - IKC Agreements Chapter 5. TASKS APPLICABLE TO ALL PROJECT STAGES – 5.1 Project Management and Control – 5.2 Risk Management – 5.3 Configuration Management – 5.4 Project & Quality Assurance and Safety Chapter 6. DOCUMENTATION FORMAT Chapter 7. TRANSPORTATION AND DELIVERY Chapter 8. WARRANTY Chapter 9. EXCLUDED BACKGROUND 14

BACK-UP Slides Types of Technical Reviews - explanations Design Reviews, for example PDR: a review of Preliminary (i.e. conceptual, pre-prototype) Design CDR: a review in detail of the complete or near finalized detailed design data and documentation of the components or systems. – includes reviewing results, decisions from any analysis, prototyping testing. – ‘Critical’ because it is a risk-reducing ‘toll-gate’ review, for proceeding to component and system procurement and manufacture – May also be held for agreement high-value, long-lead time procurement Readiness Reviews, for example TRR: Test Readiness Review – confirms a component’s or assembled system’s ‘as-built’ status, and – confirms planning and that all is ready for verification ORR: Operational Readiness Review. post-commissioning. (Component, ) System Acceptance Reviews: confirm results of FAT, SAT and other verification activities. Includes check of QC inspections and tests the mechanism for ESS to accept products – enacts the transfer of ownership 15