Technical Reviews – Contents –

Thomas Hott Technical Reviews Contents, 2nd CDE-WS, 12th & 13th May 09XFEL Technical Coordinator

1

Technical Reviews

– Contents –

1


23C

Technical Reviews shall ensure for all deliverables:•Completeness•Compatibility•Compliance

Generating deliverables is a long(er)-term process. –> In order to ensure final 3C it is recommendable to subdivide this process into so-called Product Lifecycle Phases and perform intermediate 3C checks when moving from one phase to the subsequent. This has two aspects:

1.Backward2.Forward

That means:1.A project lifecycle phase can be concluded because

all belonging outputs are generated

2.The subsequent lifecycle phase can be started because all necessary inputs are available


3

Output Input Output InputOutput InputOutput Input

Product Lifecycle Phases

Requirementsdefinition

CDR

Conceptualdesign

Detaileddesign

Fabricationplanning

DR PRR

•Reviews timing must leave time for corrective actions

•Technical Reviews shall be scheduled as milestones

Fabrication


4

XFELCentral Tasks

WP A

WP B InstallationFabricationFabricationPlanning

ConceptualDesign

DetailedDesign

ConceptualDesign

DetailedDesign

Independent and concurrent WPs contribute different parts of the facility.

Independent and concurrent WPs contribute different parts of the facility.

Reviews, resp. milestones create follow-up activities at integrated facility

Reviews, resp. milestones create follow-up activities at integrated facility

integrate-> Approval

Reviews (MS) are coupling WP and central activities by sets of mandatory deliverables

Reviews (MS) are coupling WP and central activities by sets of mandatory deliverables

QA QA

placeholderA,B

Inter-faceproof

CDR

QA

as-builtdoc’s

B

Review

Accept forinstallation

in XFEL

QA

QCdoc’s

B

Review

Accept forproductiontendering

Reviews link WPs & Central Tasks

QA

review &Approval

detaileddesign

B

DREvery deliverable is QA-ed on reception according to QA standards

Every deliverable is QA-ed on reception according to QA standards


5Reviews -> To be scheduled as milestones

Reviewing is a QA measure of eminent importance

Different Reviews are required at different times

They couple WP activities and Central Tasks by sets of mandatory inputs & outputs

They provide sureness to the WPs & PM

They initiate ‘Follow-Up Activities’ in the project

Concerns all major deliverables and sub-systems

Timing must leave time for corrective actions


6

Mandatory Outputs / Inputs (Deliverables)•Deliverables / System Description•Requirements Analysis•Target Specifications•Design (conceptual –> detailed)•Fabrication Planning•Quality Management Plan (QMP)•Tendering Documents•Further Mandatory Technical Documents

Reviews Contents

–> To be reviewed by all requesting & interfacing parties (WPLs, Coordinations)–> Changes to be incorporated (coordinated updating of all concerned docs)–> Finally to be approved by the Project Board


7Deliverables / System

DescriptionThe Deliverables / Systems Description shall

clarify:

1.PurposeWhat shall the system effect (Zweck –> Was soll das System

leisten)• General technical context• Which needs of other systems shall be satisfied• Which functionalities shall be delivered, provided to

other systems• What do they mean for the performance of the

2.ScopeWhat shall the system achieve and what not anymore (Abgrenzung)• Which performance extent is needed, which not anymore

3.Concept & LayoutHow shall the system achieve it• General layout (segmentation, subcomponents, hardware, software, assembly steps)


8Requirements Analysis

Requirements ElicitationProblem: Beside formulated requirements there are usually non-formulated

expectations – They might be as important!Requirements Analysis shall ensure:1.Completeness (product lifecycle, interfaces at each

lifecycle phase)

2.Consistency (eliminated contradictions = negotiation results)

3.Prioritisation (must, nice to have, must not)

4.Verifiability (req. must be formulated such that their fulfilment can be verified / measured


9Target Specifications

Target Specifications shall define:1.Set of Requirements that shall be satisfied finally

(issuers)• Functional req. (= capabilities)• Non-functional req. (= constraints; incl.

regulations, standards & norms)2.Exact technical specification how the deliverable shall be built• Design choices (e.g. technologies, materials …)• Self-produced parts• Purchase parts• Software (features & structure)• Interfaces (mechanics, signal levels & structure)

3.Explanation how that technical layout will satisfy the requirements


10Design

conceptual –> detailed

The Design shall comprise:(conceptual –> detailed; high level –> low level; feasibility

study –> shop drawings)

1.System Model ("Architecture": 3D, UML, written documents …)

2.Calculations (analytical, numerical)

3.Simulations (FEM, Start-to-End, Monte Carlo …)

4.Safety analysis (written documents, prototype tests …)

5.Interface Definitions (e.g. 3D Placeholders -> confirmed ‘Collision Free’, documents approved by requesting & interfacing parties like WPLs, Coordinations …)


11Fabrication Planning

Fabrication Planning shall comprise:1.Envisaged methods (description and reasoning, incl. advantages, constraints, disadvantages)

2.Fabrication adaptation (adapted models, drawings, plans …)

3.Side Conditions (availability/readiness of subsequent issues, e.g. test or storage environments, trained personnel …)


12QMP

Concluding a lifecycle phase requires two QM measures:

1. Verification (= Requirements coverage check; "Is the right thing done?")

2. Validation (= Compliance check; "Was it done right?")

The Quality Management Plan* shall stipulate all QM measures for all product lifecycle phases

The QMP shall therefore pre-define (pre-identify) all:

1. Verification criteria, methods, tools

2. Regulations, standards, norms

Finally the QMP shall provide for each phase a complete specification of all needed inputs and resources, as well as planned outputs–> However, it will be a living document as understanding grows–> Nevertheless, it must be appropriate at any time* The QMP shall follow in general the recommendations of the EN ISO 9001 standard as much as possible


13Tendering Documents

Tendering Documents shall comprise:1.Technical part (written specs, fabrication models, shop drawings, QM measures …)

2.Commercial part (terms of contract, awarding matrix …)

–> Both must be complete, consistent, compliant (3C)

–> Criteria etc. to be pre-defined and are part of the QMP


14Further Technical

DocumentsFurther Mandatory Technical Documents are:1.Instructions / Manuals (assembly, installation, maintenance …)

2.Drawings (circuit diagrams, operation flow charts …)

3.Safety & Health Plans (for installation/integration activities at XFEL conducted under the own WP responsibility)

4.… (to be defined for each WP)


15

CDR – Review Content•Deliverables / System Description•Requirements Analysis•Target Specifications•Conceptual Design•Quality Management Plan (QMP)

Conceptual Design Review


DR PRRCDR

Conceptualdesign

Fabricationplanning

Detaileddesign


Fabrication


16

DR – Review Content•Deliverables / System Description•Requirements Analysis•Target Specifications•Detailed Design•Fabrication Planning•Quality Management Plan (QMP)

Design Review



DR PRRCDR

Conceptualdesign

Fabricationplanning

Detaileddesign Fabrication


17

PRR -> Required Information

•Deliverables / System Description•Requirements Analysis•Target Specifications•Design (conceptual –> detailed)•Fabrication Planning•Quality Management Plan (QMP)•Tendering Documents•Further Mandatory Technical Documents

Production Readiness Review



DR PRRCDR

Conceptualdesign

Fabricationplanning

Detaileddesign Fabrication