21.01.2015 Views

Quality Assurance at F4E - Fusion For Energy

Quality Assurance at F4E - Fusion For Energy

Quality Assurance at F4E - Fusion For Energy

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

QA REQUIREMENTS<br />

CONTRACT IMPLEMENTATION<br />

‘<strong>Fusion</strong> for <strong>Energy</strong>’<br />

MAY 2009 QA ON PROJECT IMPLEMENTATION 1


Origin - <strong>Quality</strong> Requirements<br />

French<br />

Authority<br />

Regul<strong>at</strong>ions<br />

ITER QA PROGRAM<br />

Compliant with<br />

French Authority Regul<strong>at</strong>ions<br />

<strong>F4E</strong> QA PROGRAM<br />

Compliant with<br />

French Authority Regul<strong>at</strong>ions<br />

and ITER QA Program<br />

ITER has been classified as an<br />

“Install<strong>at</strong>ion Nucléaire de Base” (INB),<br />

and within this larger class recognising<br />

the objective limit of the risks, in the<br />

subclass of Labs and Fuel Plants<br />

ITER must comply, <strong>Quality</strong> wise, with:<br />

• ARRETE QUALITE DU 10 AOUT<br />

1984<br />

• IAEA Safety Requirements GS-R-3<br />

(2006) – “The Management System for<br />

Facilities and Activities”.<br />

Associ<strong>at</strong>e<br />

or<br />

Industry<br />

QUALITY PLAN<br />

Compliant with<br />

<strong>F4E</strong> QA Program<br />

MAY 2009 QA ON PROJECT IMPLEMENTATION 2


Management Specific<strong>at</strong>ion - Requests<br />

<strong>Quality</strong> and Management requirements are addressed in Annex A<br />

Annex A is the Management Specific<strong>at</strong>ion and requests a <strong>Quality</strong> Plan<br />

AT TENDER LEVEL<br />

The Bidder shall provide, in its offer a meaningful outline of a dedic<strong>at</strong>ed <strong>Quality</strong> Plan where the plans,<br />

schedules and explan<strong>at</strong>ion of the provisions to comply with the following requirements will be assembled.<br />

The Bidder will be evalu<strong>at</strong>ed, inter alia, on the basis of its <strong>Quality</strong> Plan according to the Tender<br />

Specific<strong>at</strong>ions.<br />

During offer, due to the n<strong>at</strong>ure of the process, the Bidder might not have all the inform<strong>at</strong>ion th<strong>at</strong> he will have<br />

as a successful Bidder. As result of this limit<strong>at</strong>ion, <strong>at</strong> this stage the <strong>Quality</strong> Plan cannot be a “complete”<br />

version and is referenced as an “outline’ version where:<br />

– Some sections will be addressed as a description of the previewed system (proposed system).<br />

– The remaining sections shall have the description of the Bidder current system.<br />

AT CONTRACT LEVEL<br />

After the Contract sign<strong>at</strong>ure, the <strong>Quality</strong> Plan shall encompass the following sequential stages (in<br />

accordance with §5):<br />

1. <strong>at</strong> the kick-off meeting the Supplier shall provide the proposed <strong>Quality</strong> Plan;<br />

2. the Supplier shall not begin any work without the <strong>Quality</strong> Plan being released in writing by <strong>F4E</strong>;<br />

3. during Contract implement<strong>at</strong>ion, the Supplier shall upd<strong>at</strong>e the <strong>Quality</strong> Plan (or parts of it) as/if<br />

required and shall submit it to <strong>F4E</strong> for release.<br />

MAY 2009 QA ON PROJECT IMPLEMENTATION 3


QUALITY PLAN<br />

The dedic<strong>at</strong>ed <strong>Quality</strong> plan describes the<br />

oper<strong>at</strong>ional quality system implemented<br />

by the bidder/supplier to ensure th<strong>at</strong>:<br />

• Contract requirements will be met,<br />

• Evidence of such compliance will be<br />

maintained.<br />

The compliance with the <strong>Quality</strong> Plan shall<br />

replace any need for QA certific<strong>at</strong>ion.<br />

Certific<strong>at</strong>ion is not mand<strong>at</strong>ory, but<br />

recommended.<br />

MAY 2009 QA ON PROJECT IMPLEMENTATION 4


PROCESSES FLOWCHARTS<br />

FLOW OF DOCUMENTATION<br />

RESPONSIBLE<br />

FUSION FOR ENERGY ACTIVITIES<br />

CUSTOMER ACTIVITIES<br />

DOCUMENT<br />

On going Process<br />

RESPONSIBLE<br />

FUSION FOR ENERGY<br />

ACTIVITIES<br />

IO ACTIVITIES<br />

(Inspection, Test, Design, …)<br />

AUTHOR<br />

(ORIGINATOR)<br />

REVIEWER<br />

START OF DOCUMENT FLOW<br />

PROCEDURE<br />

1.Draft Document<br />

Prepar<strong>at</strong>ion or<br />

Review Change<br />

2.Document REVIEW<br />

3.Review<br />

CHANGE &<br />

DEVIATION<br />

HANDLING<br />

All Personel<br />

WPM<br />

QA Officer<br />

START OF PROCEDURE<br />

2. HOLD PROCESS<br />

Activity can be initi<strong>at</strong>ed<br />

by Customer or <strong>F4E</strong><br />

1. Detect/Identify NC<br />

(Requirement not fulfilled)<br />

YES<br />

COMMENTS<br />

NO<br />

RESPONSIBLE<br />

FUSION FOR ENERGY ACTIVITIES<br />

IO ACTIVITIES<br />

DOCUMENT<br />

YES<br />

3.Process<br />

involves<br />

AUTHOR<br />

(ORIGINATOR)<br />

4. EXTERNAL<br />

REVIEW<br />

REQUIRED<br />

YES<br />

Document COMMENT<br />

by IO<br />

Frozen Specific<strong>at</strong>ion<br />

Requirements<br />

WPM<br />

QA Officer<br />

4.Segreg<strong>at</strong>e item NC<br />

and Identify<br />

Product<br />

NO<br />

Indentific<strong>at</strong>ion<br />

Tag<br />

APPROVER<br />

NO<br />

5. Document<br />

APPROVAL<br />

IO<br />

COMMENTS<br />

NO<br />

YES<br />

Competent Person<br />

1.Identify<br />

Problem/Improvement<br />

Request<br />

START OF CHANGE MANAGEMENT<br />

IO CHANGE NOTICE<br />

Change<br />

Notice<br />

WPM<br />

5.Issue NC<br />

REPORT<br />

Nonconformity<br />

opened<br />

Nonconformity<br />

Report<br />

PROCEDURE<br />

Nonconformity stays<br />

NO<br />

6.APPROVAL<br />

WPM<br />

2.DRAFT CHANGE<br />

REQUEST<br />

Draft CR<br />

PM +<br />

Affected WPM<br />

6.MAJOR<br />

NC<br />

YES<br />

7.Send to CUSTOMER<br />

RO<br />

open<br />

Major NC<br />

LIST<br />

YES<br />

AUTHOR<br />

(ORIGINATOR)<br />

7.EXTERNAL<br />

APPROVAL<br />

REQUIRED<br />

YES<br />

Final ACCEPTANCE<br />

by IO<br />

WPM<br />

+ Integr<strong>at</strong>ion<br />

3.IMPACT ANALYSIS<br />

4.IMPACT ANALYSIS<br />

No Change<br />

Impact Report<br />

PM + WPM<br />

NO<br />

8.Decision on Corrective/<br />

Preventive Actions<br />

Corrective/<br />

Preventive<br />

Action<br />

NO<br />

NO<br />

C<br />

AUTHOR<br />

(ORIGINATOR)<br />

ADMINISTRATION<br />

8. FINAL RELEASE<br />

TO CUSTOMER<br />

9.ARCHIVE<br />

ORIGINAL & UPDATE<br />

DOC PLAN<br />

IO<br />

APPROVAL<br />

YES<br />

NO<br />

PM/WPM<br />

WPM<br />

NO<br />

6.Issue Internal<br />

CHANGE<br />

REQUEST<br />

5.Change of<br />

CUSTOMER<br />

requirement<br />

YES<br />

9.Issue<br />

CHANGE<br />

REQUEST<br />

8.Change<br />

Beneficial<br />

(Conference<br />

CUSTOMER)<br />

YES<br />

Change<br />

Request<br />

WPM<br />

WPM<br />

9.Record NC in NC-LIST<br />

Nonconformity<br />

stays open<br />

10.Implement<br />

CORRECTIVE/<br />

PREVENTIVE ACTION<br />

<strong>F4E</strong> Minor NC-<br />

LIST<br />

C<br />

<strong>F4E</strong> Minor NC-<br />

LIST<br />

Customer copy<br />

APPROVED<br />

Corrective/<br />

Preventive Action<br />

Minor NC<br />

LIST<br />

Corrective/<br />

Preventive<br />

Action<br />

YES<br />

10.DOCUMENT<br />

NEEDS<br />

CHANGES<br />

NO<br />

Review Group<br />

(in Man. Plan)<br />

7.Technical Review of<br />

Proposed Change<br />

10.Send to CUSTOMER<br />

RO<br />

Disposition of<br />

CHANGE<br />

Disposition<br />

Disposition<br />

QA Officer<br />

11.Completition and<br />

Control of the Correction<br />

Actions<br />

Nonconformity<br />

closed<br />

END OF NONCONFORMITY<br />

Closed<br />

NCR<br />

END OF DOCUMENT FLOW<br />

PROCEDURE<br />

FUSION FOR ENERGY<br />

IO<br />

Project/Contract<br />

Management<br />

11.CHANGE<br />

REQUEST<br />

APPROVED<br />

NO<br />

No Change<br />

PROCEDURE<br />

FUSION FOR ENERGY ACTIVITIES<br />

C<br />

Reject (Scrap), Repair,<br />

Rework, Use-As Is<br />

CUSTOMER ACTIVITIES<br />

YES<br />

Customer<br />

No Change<br />

NO<br />

IMPACT<br />

REPORT<br />

DOCUMENTATION<br />

FLOW<br />

Project/Contract<br />

Management<br />

WPM<br />

12.Establish Work<br />

Plan with resources<br />

and schedule<br />

13.CHANGES<br />

IMPLEMENTATION<br />

14. UPDATE<br />

Specific<strong>at</strong>ion<br />

Requirements<br />

Acceptance<br />

YES<br />

UPDATE Specific<strong>at</strong>ion<br />

Requirements<br />

Work Plan<br />

Upd<strong>at</strong>ed<br />

Specific<strong>at</strong>ion<br />

NONCONFORMITY<br />

HANDLING<br />

END OF CHANGE MANAGEMENT<br />

PROCEDURE<br />

Change Request<br />

Closed<br />

FUSION FOR ENERGY ACTIVITIES<br />

IO ACTIVITIES<br />

MAY 2009 QA ON PROJECT IMPLEMENTATION 5


French Regul<strong>at</strong>ion for Nuclear Safety <strong>Quality</strong><br />

Order (resume)<br />

QUALITY ORDER OF AUGUST 10, 1984 FRENCH REGULATION FOR NUCLEAR SAFETY<br />

The required quality is obtained and maintained on one hand by activities performed and on the other hand by<br />

organized and appropri<strong>at</strong>e verific<strong>at</strong>ion.<br />

Art 1. Graded quality management system according to safety importance of components and activities (SIC). Set up <strong>at</strong><br />

the design stage and extended throughout all the subsequent stages of existence of the Install<strong>at</strong>ion.<br />

Art 2. Definition of safety relevant activities.<br />

Art 3. Definition of Oper<strong>at</strong>or and contractors.<br />

Art 4. Oper<strong>at</strong>or is responsible for safety and responsible of applic<strong>at</strong>ion by contractors of adequ<strong>at</strong>e QA system.<br />

Art 5. QA manual + QA compliance report + contractors assessment.<br />

Art 6. Safety requirement are defined and monitored.<br />

Art 7. Appropri<strong>at</strong>e human and technical resources in agreement to<br />

safety objectives.<br />

Art 8. Independent verific<strong>at</strong>ion of safety relevant activities.<br />

Art 9. QA management team + Evalu<strong>at</strong>ion and correction<br />

monitoring.<br />

Art 10. Records and reporting + frequency.<br />

Art 11. Correctly storage records and hardcopies.<br />

Art 12. & 13. Devi<strong>at</strong>ions definition, devi<strong>at</strong>ion records, declare to<br />

NSA, feedback.<br />

Art 14. Safety relevant studies are concerned by QA (apply QA<br />

during design).<br />

KO DA<br />

RU DA<br />

JP DA<br />

USA DA<br />

IN DA<br />

ITA<br />

French Authority<br />

Requirements<br />

ITER<br />

QMS<br />

CN DA<br />

<strong>F4E</strong><br />

PP<br />

QP<br />

PP<br />

PP<br />

PP<br />

EU<br />

SUPPLIER<br />

EU<br />

SUPPLIER<br />

QP<br />

<strong>F4E</strong><br />

QA PROGRAM<br />

PP<br />

QP<br />

QP<br />

EU<br />

SUPPLIER<br />

EU<br />

SUPPLIER<br />

PP = Comercial Contract +<br />

Technical Specific<strong>at</strong>ion +<br />

Management Specific<strong>at</strong>ion<br />

MAY 2009 QA ON PROJECT IMPLEMENTATION 6

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!