control bench contract product assurance requirements...

VG-AP-2-C-0005-CNES(1.5)A_sign.doc Version validée SDS Imprimé le 11 / 04 / 03

CENTRE NATIONAL D'ETUDES SPATIALES

Sous-Direction Développements Sol

18, Avenue Edouard-Belin 31401 TOULOUSE Cedex 4

Rond-point de l'Espace 91023 EVRY Cedex

SDS/G BP 254 - 97377 KOUROU CEDEX

CODE IDENTIFICATION PROJET

VG-AP-2-C-0005-CNES

EDITION : 1 REVISION : 5

Date édition ou dernière révision :28/03/2003

REF. D'AUTEUR :DLA/SDS/AP/SY/2003.7

CLASSE : 1 CATEGORIE : 1

RESERVE A L'INDUSTRIEL

PROJET : VEGA GROUND SEGMENT

TITRE DU DOCUMENT :

Control bench contract Product Assurance

Requirements and Tasks

NOM & FONCTION DATE & SIGNATURE

PREPARE PAR :

F. DELAMOTTE DLA/SDS/AP/SY

A. DESROCHES DLA/SDS/AP/CM

POUR APPROBATION :

A. CUENCA DLA/SDS/AP/SY

A. RAGOT

DLA/SDS/AP/D

POUR ACCEPTATION :

J. TANGUY DLA/SDS/PL/SE

M. VALES VEGA-GS Coordinator

APPLICATION AUTORISEE

PAR :

M. PANICUCCI M. CARDONE

ESA/IPT

LISTE DE DIFFUSION Nb A I

SDS/SG/MS/BT 1 X

Les signataires SDS + 1 X

ESA/IPT M.CARDONE 1 X

ESA/IPT D.COULON 1 X

ESA/IPT J.M MONTHILLER 1 X

ESA/HQ E.LEFORT 1 X

ESA/ESTEC J.PINEL 1 X

SDS/PL 1 X

SDS/PL/SE 1 X

SDS/AP/MR 1 X

SDS/AP/G 1 X

CG/SDP/SE B.SALVETAT 1 X

SDS/PL/SV M. VALES 1 X

A=Action I=Information



Sous-Direction Développements Sol

18, Avenue Edouard-Belin 31401 TOULOUSE Cedex 4

Rond-point de l'Espace 91023 EVRY Cedex

SDS/G BP 254 - 97377 KOUROU CEDEX

LANGUE :Fr EDITION : 1 REVISION : 5

DATE D'EDITION OU DERNIERE REVISION : 28/03/2003

CODE IDENTIFICATION PROJET

VG-AP-2-C-0005-CNES

FICHE SIGNALETIQUE

FICHIER INFORMATIQUE

C:\Mes documents\Nouveau dossier\SDS-PL-SE\TANGUY\VG-AP-2-C-0005-CNES(1.5)A_sign.doc

Nombre de pages totales (y/c annexes et pages de garde) :

37

Nb de pages annexes :

TBD

TITRE :

Control bench contract Product Assurance Requirements and Tasks

NOM (S) AUTEUR (S) CNES

TYPE DE DOCUMENT

ASSURANCE PRODUIT

CLASSEMENT PHYSIQUE N° MARCHE CLASSE : 1

CATEGORIE : 1

RESUME D'AUTEUR

This document provides the Product Assurance Requirements and Tasks to be applied by the Control bench Industrial Contractor for the VEGA Ground segment.

MOTS CLES (mis par l'auteur) RESERVE AUX INDUSTRIELS

VEGA Quality Product Assurance Dependability Control bench Configuration



Titre du document : Control bench contract Product Assurance


Sous-direction Développements Sol

VG-AP-2-C-0005-CNES

Page : 3/37 Ed.: 1 Rév.: 5 Date :28/03/2003

EDITION REVISION DATE OBJET DE LA MODIFICATION

1 0 20/01/2003 Edition Originale.

1 1 12/02/2003 This issue takes into account the CNES internal comments and the issue 1.1 of the RD6

1 2 17/02/2003 This revision takes into account the issue 1.2 of the VG-SM-21x-C-0002-CNES and the CNES comments.

1 3 21/02/2003 In this issue the DRL and the DRD have been removed.

1 4 11/03/2003 This document is updated in order to be compliant with the VG-SM-200091-C-0003-CNES

1 5 28/03/2003 Update of the english wording.






VG-AP-2-C-0005-CNES

Page : 4/37 Ed.: 1 Rév.: 5 Date :28/03/2003

SOMMAIRE

1. SUBJECT ..........................................................................................................................6

2. APPLICABLE DOCUMENTS ............................................................................................6

2.1. General documents..........................................................................................................................................................6

2.2. Quality Assurance Documents .......................................................................................................................................6

2.3. RAMS Documents...........................................................................................................................................................7

3. REFERENCE DOCUMENTS.............................................................................................7

4. GLOSSARY AND ACRONYMS ........................................................................................8

5. PA RELATIONSHIP ..........................................................................................................9

6. QUALITY REQUIREMENTS AND TASKS......................................................................10

6.1. General requirements and tasks ..................................................................................................................................10

6.2. Tailored Requirements and Tasks...............................................................................................................................10

6.3. Documents Requirement list (DRL) ................................................................................................................16

7. RAMS REQUIREMENTS AND TASKS...........................................................................19

7.1. General requirements ...................................................................................................................................................19

7.2. Tailored Requirements Tasks ......................................................................................................................................19

7.3. Reminder of specified requirements............................................................................................................................22 7.3.1. Reminder of severity classes ..................................................................................................................................22 7.3.2. Reminder of qualitative objectives .........................................................................................................................22

7.4. Qualitative and quantitative Requirements................................................................................................................23

7.5. Documentation Requirement List (DRL)....................................................................................................................23

8. CONFIGURATION MANAGEMENT................................................................................24

8.1. General requirements and tasks ..................................................................................................................................24

8.2. Tailored Requirements and Tasks...............................................................................................................................24

8.3. Documentation Requirement List................................................................................................................................26






VG-AP-2-C-0005-CNES

Page : 5/37 Ed.: 1 Rév.: 5 Date :28/03/2003

9. APPENDIX.......................................................................................................................28

APPENDIX A1 – CRITICAL ITEM FORM .................................................................................29

APPENDIX A2 –ECR (CHANGE REQUEST) FORM................................................................29

APPENDIX A3 –REQUEST FOR WAIVER FORM ...................................................................29

APPENDIX A4- NON-CONFORMANCE REPORT FORM........................................................29

APPENDIX A5 - CRITICAL ITEMS LIST FORM .......................................................................29






VG-AP-2-C-0005-CNES

Page : 6/37 Ed.: 1 Rév.: 5 Date :28/03/2003

1. SUBJECT This document provides the product assurance requirements to be applied by the VEGA Ground segment control bench Contractor.

2. APPLICABLE DOCUMENTS For the CNES DLA/SDS documents that are listed here after, if you read one of these following wording( CNES/DLA/SDS, CNES or SDS ) it is necessary to remove this wording by CUSTOMER.

2.1. General documents (AD1) VG-SM-200091-C-0003-CNES Spécification de management du contrat bancs de contrôle

(AD2) CSG-RS-10A-CN

Safety regulations - General rules (AD3) CSG-RS-21A-CN

Safety regulations - Ground installations specific rules (AD4) CSG-RS-24A-CN

Safety regulations - Inter-sites specific rules Not available in English version - French version identification is CSG-RS-240-CN

(AD5) DS-MP-AS-02 Works site regulations Issue 1, revision 1 - 26/06/2000

(AD6) VG-ST-200091-C-0015-CNES VEGA ground checkout equipment requirements specification Issue 3, revision 1

(AD7) to (AD10) Intentionally not used

2.2. Quality Assurance Documents (AD11) DS-MP-AQ-05

Quality and manufacturing key point flowchart (Title TBD) (AD12) DS-MP-AQ-06

Factory and site acceptances (AD13) DS-MP-AQ-07

Non-conformities, anomalies and waivers management (AD14) DS-MP-AQ-09

Action items and pending points management (AD15) Intentionally not used (AD16) DS-MP-AQ-15 (TBC this document is not referenced)

Temporary transfer procedure (AD17) VG-AP-2-C-0002-CNES VEGA Ground Segment Software Product Assurance Requirements

(AD18) to (AD19) Intentionally not used






VG-AP-2-C-0005-CNES

Page : 7/37 Ed.: 1 Rév.: 5 Date :28/03/2003

2.3. RAMS Documents (AD20) DS-MP-SF-04 V. 1.0

Guide for management of system safety and maintainability analysis activities (AD21) DS-MP-SF-06 V. 1.0 V. 1.2

Rules for human errors prevention (AD22) DS-MP-SF-10

Critical points management (AD23) DS-MP-SF-12 V. 1.1

Dependability qualitative rules

3. REFERENCE DOCUMENTS (RD1) VG-SF-2-C-0004-CNES

Preliminary hazard analysis VEGA - Ground Segment (RD2) Functional classification (draft version in progress) (TBC) (RD3) VG-ST-200091-C-0015-CNES Cahier des Exigences du banc de contrôle VEGA

Issue 3.0 (RD4) Intentionally not used (RD5) VG-SF-2-C-0005-CNES

List of dependability sheets per contract (RD6) VG-SM-21X-C-0002-CNES Spécification de management (partie technique) du contrat « «

Issue 1.2 (RD7) DS-MP-AQ-01

Quality requirements applicable in design, manufacturing et installation Issue 1, Revision 0 – 07/10/1994






VG-AP-2-C-0005-CNES

Page : 8/37 Ed.: 1 Rév.: 5 Date :28/03/2003

4. GLOSSARY AND ACRONYMS ADR Software Architectural Design Review ARB Acceptance Review Board CCB Configuration Control Board CDR Critical Design Review CNES Centre National d’Etudes Spatiales (French Space Agency) EC European Community ECR Engineering Change Request (PM) DDL Document Delivery List DDR Software Detailed Design Review DRB Delivery Review Board DRD Document Requirement Definition DRL Document Requirement List FAR Final Acceptance Review (TBC) HW Hardware QA Quality Assurance QR Qualification Review (TBC) ESA European Space Agency FTRR Factory Tests Readiness Review FTRB Factory Tests Review Board IAR Industrial Acceptance Review IPT Integrated Project Team IQR (TBD) ICDR Industrial Critical Design Review IPDR Industrial Preliminary Design Review KIP Key Inspection Point KOM Kick - Off Meeting MIP Mandatory Inspection Point NCR Non Conformance Report OSTRR On Site Tests Readiness Review OSTRB On Site Tests Review Board PA Product Assurance PVRI Procès-Verbal de Réception Industrielle QA Quality Assurance RAMS Reliability, Availability, Maintainability and Safety SRR Software Requirements review SDS Sous-Direction Développement Sol (Ground Segment Sub-Directorate) SW Software TBC To Be Confirmed TBD To Be Defined WBS Work Breakdown Structure






VG-AP-2-C-0005-CNES

Page : 9/37 Ed.: 1 Rév.: 5 Date :28/03/2003

5. PA RELATIONSHIP The PA contractor manager reports to the PA Infrastructure Manager who reports to the ESA/IPT PA manager (through PA Ground Segment Manager). The industrial contractor shall not normally have direct links with ESA/IPT PA Manager except in some cases, through or with CNES DLA/SDS :

major NCR processing configuration management boards MIP/KIP audits

The customer of the industrial contractor is ESA represented by the technical officer for technical matters.

ESA/IPT

CNES DLA/SDS

VEGA Ground Segment Technical Officer

VEGA Program Management

PA Manager

M.PANICUCCI

PA Ground Segment Manager

A.RAGOT

QA Control Bench Manager

F. DELAMOTTE

RAMS Manager

A.DESROCHES






VG-AP-2-C-0005-CNES

Page : 10/37 Ed.: 1 Rév.: 5 Date :28/03/2003

6. QUALITY REQUIREMENTS AND TASKS 6.1. General requirements and tasks

The general requirements and tasks are described in the RD7. The contractor has to apply these requirements and to give them to his sub-contractors. He is in charge to check the application of these requirements and to provide the application visibility to the customer. The main quality tasks to be performed by the industrial contractor are :

To define product assurance organisation : means and tasks description in order to ensure quality requirements application. This product assurance organisation must provide the quality assurance plan and submit it to the customer approval.

To ensure correct implementation of quality assurance requirements, during project phases : design, purchase, manufacturing and factory tests, installation, on site tests and validation, final acceptance operations and warranty with the customer for him and his sub-contractors.

To ensure visibility to his customer on the quality aspects : main quality points, problems, difficulties, non-conformities, anomalies and waivers status, pending points and action items status, factory and site acceptances status, quality checks, audits... To perform this task, he shall, in particular, provide a quality assurance report at each progress meeting, at each review and for acceptance phases

The acceptance tests include two steps : 1st step is factory tests before delivery on site and 2nd step is tests on site.

6.2. Tailored Requirements and Tasks

This section is a customisation of the RD6.






VG-AP-2-C-0005-CNES

Page : 11/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement number Requirement area Requirement text

902 Quality Assurance Industrial contractor must designate a PA manager, by name, at the beginnthis project. This PA manager must be hierarchically independent from the pr

904 Quality Assurance Plan

Industrial contractor must provide a Quality Assurance Plan explaining how asked by the customer shall be taken into account and applied


Quality Assurance Plan must be delivered according to the AD1.


Any quality assurance plan modification must be submitted to the approval of


For the whole warranty, the Quality Assurance Plan is applicable to the contr

910 Quality Assurance Industrial contractor must define the specific assurance quality requirecompliant with the customer’s requirements.


Industrial contractor must provide a quality assurance report giving at least th- performed quality tasks, - non-conformities and waivers status, - pending points, - preventive actions and corrective actions status, - factory and site acceptances status.

912 Audits The customer and its representatives could decide to implement an audit to requirements or any other contractual requirement. He shall be authorisecontractor premises and facilities.

913 MIP/KIP The customer must allow the customer and its representatives to accesspremises and facilities.

914 Audits Industrial contractor must implement preventive and corrective actions issueimplementation.

916 Quality documentation

Industrial contractor PA manager must ensure that means and procedures documentation management requirements asked by the customer. He shalldocuments codification, the presentation of the documents, the signatures vof the management.






VG-AP-2-C-0005-CNES

Page : 12/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement

number Requirement area Requirement text

917 Configuration Control quality

Industrial contractor PA manager must ensure that means and procedures configuration control management requirements asked by Industrial contractor PA manager must check, at least by sampling, the config

918 Actions items management quality

Industrial contractor PA manager must ensure that means and procedures action item management requirements asked by the customer.

919 Actions items management quality

Industrial contractor PA manager must ensure that action items closure are are in correspondence with action item problem resolution.

920 Purchasing quality Industrial contractor must check conformity between purchased items and shelf items . The acceptance checks for these items must be performed befocontractors.

922 Purchasing quality Industrial contractor must give the previous date of these checks one calenda923 Purchasing quality Long lead items, that is to say more than six months, list shall be provided by

at ICDR. 924 Test and checks Inside of the Manufacturing inspection flow chart, industrial contractor must g

quality plan, the main steps and submission date to the customer. 926 Manufacturing

inspection flow chart

Tests and checks results issued from manufacturing inspection flow chart meetings and test readiness review on factory and on site.

928 Manufacturing inspection flow chart

Tests and checks of Manufacturing inspection flow chart must be performedThese procedures must describe the operation, the methodology and the exp






VG-AP-2-C-0005-CNES

Page : 13/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement


930 Regulations Industrial contractor must apply on site rules : access and works site activitie931 Regulations The components and facilities must be consistent with mandatory directives, 932 Regulations Industrial contractor shall provide, for the facilities relevant to directives

established by an official agreed organism, e.g. electrical power. 934 On - shelf items Industrial contractor shall provide a conformity certificate for on the she

conformity. 936 Modified on - shelf

items Industrial contractor supplies on -shelf items with modifications, he mustconditions (interface and environment) and provide the results in order to com

938 Specific items For specific items, industrial contractor quality responsible must check and a• a industrial design file (DID in French : Dossier Industriel de Défin• a industrial manufacturing plan (DIF in French : Dossier Industriel • a tests and checks industrial file (DIC in French : Dossier Indust

representative conditions (interface and environment) and prorequirements

• management file 940 Marking or labelling All supplied hardware items must be identified and marked in a single way w

the identification must be clearly visible and indelible. 944 Handling, storage

and transportation Industrial contractor must provide means and procedure to avoid supplies da






VG-AP-2-C-0005-CNES

Page : 14/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement


945 Handling, storage and transportation

Industrial contractor must ensure that supplies are correctly protected agaihumidity, temperature,…)

946 Checks, tests and measurement equipment

Any check, test and measurement mean must have : • equipment identification • last calibration date with validity date • operator or organism identification in charge of calibration

947 Software The (AD17) is applicable to this contract. The software requirements reviews (SRR) shall be hold with the IPDR. The software architectural or preliminary design reviews (ADR) shall be holdThe software detailed design reviews (DDR) shall be hold with the ICDR.

948 Non-conformance management

The contractor must manage all the non-conformances whatever who detecthe contractor.

950 Non-conformance management

For each detected non-conformance a non-conformance form is issued. Thbefore the factory acceptance TRR.

951 non-conformance The non-conformance form must be filled one hour after the non-conformancdetects this non-conformance.

960 Acceptance phase Before customer convocation to acceptance operations (checks, tests,…),system is correctly completed

962 Acceptance phase Before acceptance operations with the customer, the industrial contractor msystem is in condition for acceptance operations. Test results must be registe

974 Test readiness review

Test procedures must be sent to the customer, for approval, at least one cale






VG-AP-2-C-0005-CNES

Page : 15/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement number Requirement area Requirement text

975 Test Readiness Review

The minute of the Test Readiness Review, see format in the AD12, shall be wand by the customer for on-site acceptance. The minute must be signed by cand assurance quality representatives

976 Test readiness review

Industrial contractor must invite the customer to the test readiness review, bybefore the foreseen date. Customer and industrial contractor technical and asthis review.

977 Acceptance tests with the customer

Acceptance tests must be performed in accordance with the approved proced


Some tests may be performed with the future user participation


During tests, no corrective intervention may be implemented without representatives written agreement.

995 Test review board The minute of the tests review board, see format in the AD12, shall be writtenacceptance and by the customer for on-site acceptance. The minute must betechnical and assurance quality representatives






VG-AP-2-C-0005-CNES

Page : 16/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement


996 Acceptance review board

After on site tests review board, in case of satisfactory results, industrial acceThe customer writes the minutes of the acceptance review board. The minutecontractor technical and assurance quality representatives According to acceptance review board results, the customer shall decide : • acceptance without due points or with minor due points. A official c

contractor is provided for property transfer from industrial contractor to cu• postponed acceptance. The industrial contractor must close major due

acceptance operations • reject if the system is not repairable. In general, this decision is not for th

The substitution of this part or this component by a new one may auacceptance operations

984 Pending points (Reserves)

The pending points treatment is performed in agreement between the responsible, due date.


For major pending points, the customer and the industrial contractor must de• precise reserve identification • corrective actions to implement in order to close the reserve • mandatory checks and tests to validate these actions • closure steps schedule


Minor pending points closure, decided by the customer, must be performindustrial contractor and approved by the customer, providing the reserve su

986 Deliverable documentation

See section 6.3 : Quality Documentation Requirement List

6.3. Documents Requirement list (DRL) The industrial contractor provides the quality assurance documents which are listed hereafter : Quality assurance Plan Software quality assurance plan Hardware Manufacturing inspection flow chart Audit Report Quality Assurance progress report KIP and MIP report PVRI or Factory Industrial Acceptance Report Individual Acceptance Register Readiness and test review board Action items and pending points list Non-conformity or anomaly Reports Non conformities and anomalies list and status Waivers List and status






VG-AP-2-C-0005-CNES

Page : 17/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Waiver Reports The schedule to deliver these documents is specified in the AD1 that defines the DRL for the contractor. The tables of content for each document are defined in the AD1 (DRD).






VG-AP-2-C-0005-CNES

Page : 18/37 Ed.: 1 Rév.: 5 Date :28/03/2003






VG-AP-2-C-0005-CNES

Page : 19/37 Ed.: 1 Rév.: 5 Date :28/03/2003

7. RAMS REQUIREMENTS AND TASKS 7.1. General requirements

The requirements and tasks are described in the AD20.

7.2. Tailored Requirements Tasks These requirements are derived from the RD6.






VG-AP-2-C-0005-CNES

Page : 20/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement number

Requirement area Requirement text

702 RAMS RAMS industrial Plan to be provided

704 Functional analysis Functional analysis must be provided by industrial contractor

706 Preliminary Hazard Analysis

PHA must be provided by industrial contractor

708 RAMS apportionment

If necessary, the contractor shall provide a RAMS apportionment for subsystem included in subcontract

710 FMEA/FMECA The contractor shall provide the HW and SW FMEA/FMECA then reduction risk actions shall be opened.

712 Feared events The contractor shall perform an analyse of the feared events which have been specified in a list. The fault tree method is advised. This approach have to take account the hardware, software and operational failures and to assess the probability of the feared events.

714 Reliability analysis The industrial contractor shall provide a reliability model by reliability diagram or another appropriate method.

716 Reliability data The industrial contractor shall provide and justify the origin (databank, industrial data,…) of the reliability data (MTBF; MTTR,..) for every component.

718 Reliability assessment

The industrial contractor shall perform a reliability assessment of the system for the duration of its mission. The comparison with the requirements shall be done. The search of weak HW components shall be performed and the relevant actions shall be opened.

722 Availability analysis The industrial contractor shall perform system intrinsic and operational availability analysis to assess the system MDT.

776 Maintainability analysis /. Spare parts list

The industrial contractor shall perform maintainability analysis to assess MTTR at component and MDT at system level. The industrial contractor shall provide a spare parts list coming from the maintainability analysis and take into account the Turn Around Time relevant of the spare parts on site






VG-AP-2-C-0005-CNES

Page : 21/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement number

Requirement area Requirement text

726 Safety analysis The industrial contractor shall perform safety analysis to identify and assess risks against personal and facilities. The comparison with the requirements shall be done.

728 Single point failure The industrial contractor shall identify the HW SPF and take into account in RAMS analysis.

730 Common mode failure The industrial contractor shall identify the HW common mode failures and take into account in RAMS analysis.

732 Zone analysis The industrial contractor shall perform and provide a zone analysis report to the customer

734 RAMS actions The RAMS actions coming from RAMS analysis must be listed and managed by industrial contractor.

736 Critical Item List The industrial contractor shall provide the CIL coming from RAMS analysis

738 RAMS report The industrial contractor shall provide a RAMS reports to the customer for progress meetings and according to the AD1

770 Human errors The AD21 is applicable to this contract

772 Critical points The AD22 is applicable to this contract

774 Dependability qualitative rules

The AD23 is applicable to this contract






VG-AP-2-C-0005-CNES

Page : 22/37 Ed.: 1 Rév.: 5 Date :28/03/2003

7.3. Reminder of specified requirements 7.3.1. Reminder of severity classes

The severity classes for the technical and operational hazards of the VEGA ground segment are described as follows:

Severity class

Index Definition of the feared potential event

Catastrophic G0A Feared events concerning the CSG personnel Feared events concerning the ground facilities outside the ZLV G0B Feared events concerning the ground facilities of the ZLV Feared events concerning the launcher

Critical

G1 Feared events concerning the Payload

G2.3 Delayed launch > 1 day

G2.2 Delayed launch = 1 day

Major

G2.1 Timetable stopped without delayed launch (launch within the window after H0)

7.3.2. Reminder of qualitative objectives

The dependability qualitative requirements or objectives that were specified for the VEGA ground system design are as follows:

Severity class Design criterion Description of the criterion

Catastrophic FS / FS No combination of hardware or software failures or of an operating error must entail feared potential events with major catastrophic consequences. In other words, the system must remain safe after a double failure of the VEGA Ground Segment or of the operators

Critical FS No hardware or software failure, or operating error must entail feared potential events with critical consequences. In other words, the system must remain safe after a failure of the VEGA Ground Segment

Major FO No single hardware or software failure must entail a feared potential event with a significant consequence In other words, the system must remain operational during certain fully identified operations






VG-AP-2-C-0005-CNES

Page : 23/37 Ed.: 1 Rév.: 5 Date :28/03/2003

7.4. Qualitative and quantitative Requirements See RD3 The quantitative requirements are collected in the following diagram

Risks Major Critical Catastrophic

Prob./ camp.

G2.1 G2.2 G2.3 G1 G0B G0A

1

10-2 6,8 10-3

10-3 2,9 10-3

4,8 10-4 10-4

10-5 1,3 10-5

10-6

1,2 10-6

10-7

6,2 10-8

10-8

The detailed qualitative requirements are included in paragraphs 5.6.4 and 5.6.5 and quantitative requirements in paragraphs 5.6.6 and 5.6.7 of AD6.

7.5. Documentation Requirement List (DRL) The industrial contractor provides the RAMS documents which are listed hereafter : RAMS report file RAMS progress report Preliminary Hazard Analysis (PHA) RAMS Apportionment FMEA/FMECA Feared events list and CIL RAMS action items Reliability analysis and assessment Availability analysis Maintainability analysis Safety analysis Common mode failures Single points failures Zone analysis RAMS plan RAMS analysis and assessment report file RAMS progress report






VG-AP-2-C-0005-CNES

Page : 24/37 Ed.: 1 Rév.: 5 Date :28/03/2003

The schedule to deliver these documents is specified in the AD1 that defines the DRL for the contractor. The tables of content for each document are defined in the AD1 (DRD).

8. CONFIGURATION MANAGEMENT 8.1. General requirements and tasks

The contractor has to apply these requirements and to give them to his sub-contractors. He is in charge of checking application of these requirements and to provide application visibility to the customer. The main configuration management tasks to be performed by the industrial contractor are :

To define the configuration management organisation : means and tasks description in order to ensure the configuration management requirements application. This configuration management organisation must be provided in the configuration management plan and submitted to customer approval.

To ensure correct implementation of the configuration management requirements, during project phases : design, purchase, manufacturing and factory tests, installation, on site tests and validation, final acceptance operations and warranty with the customer for him and his sub-contractors.

To ensure visibility to his customer on configuration management aspects : To perform this task, he shall, in particular, provide a configuration management status in the progress report at each progress meeting, at each review and for acceptance phases.

8.2. Tailored Requirements and Tasks In the following array, for each requirement on the configuration management of the section 8.4 of the RD6 , the customisation for this contract is pointed out. Requirement

reference Customisation 600 The contractor shall manage under configuration all hardware, software items and

documents except the consumables. 601 The contractor is responsible of the correctness of the configuration of its product

including hardware, software and documentation. 603 All documents must be managed under configuration from the IPDR until the end of the

warranty. The hardware and the software must be managed under configuration from the ICDR until the end of the warranty.

609 The contractor must deliver a document “Product tree” according to the AD1 611 The configuration shall be managed with some data processing tools 613 The configuration report must be delivered to the customer according to the AD1. 614 The ‘Liste unique’ must be delivered to the customer according to the AD1. 620 The contractor must describe the detail of the hardware and software of each equipment

in the “configuration registers”. The “configuration registers” must be delivered to the customer according to the AD1.

622 Any equipment or on line replaceable unit must be replaceable with an item of the spare part and the configuration documents, the installation manuals and the maintenance






VG-AP-2-C-0005-CNES

Page : 25/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Requirement reference Customisation

manuals, and then works nominally according to its specification. 634 The AD17 is applicable to this contract 648 The contractor must manage the changes in accordance with the procedures described

In ESA statement of work in such a way that : - any change request must analysed in a change proposal and agreed in writing before to be implemented, - any change must be verified and documented, - a change can be only proposed by the contractor or the customer.

650 The change requests must be written. With the agreement of the contractor, a responsible of the analysis of the change request is designated. He is in charge to analyse the change request and in particular its cost, its delay and the technical solutions in a change proposal.

652 The contractor manages the changes and modifications until the factory acceptance if they have no impact on the contract, e.g. : specifications, cost and delay. The customer is informed by the contractor of all the changes or modifications.

654 From the factory acceptance or if the change has an impact on the contract, e.g. : specification, cost or delay, the contractor has to be compliant with the change management of the customer, in particular the reference of the change is given by the customer.

658 The contractor is in charge of any change in order to be compliant with the contract. The changes are always performed under the contractor responsibility.

660 The requests for waiver must have a reference as the other documents.

662 If needed, the contractor writes a request for waiver, see the section 6. A form for the request for waiver is in the appendix. All the fields of this form must be filled. Any document can be annexed to a request for waiver. The requests for waiver must be issued to the customer for approval or rejection.

664 If a request for waiver is rejected, the contractor must be compliant with the requirements without any modification.

666 A request for waiver can be accepted by the customer with or without a modification of the cost, the delay and the use of the product. If the customer and the contractor do not approve or reject a waiver, the Acceptance certificate can not be issued.

668 The configuration management plan is deliverable according to the DRL of the AD1. The configuration management plan can be included in the management plan.

669 The software configuration management plan must be delivered to the customer according to the DRL of the AD1.

671 The configuration management documents must be delivered to the customer according to the DRL of the AD1.

674 The configuration management documents must be compliant with the DRD of the AD1.

.






VG-AP-2-C-0005-CNES

Page : 26/37 Ed.: 1 Rév.: 5 Date :28/03/2003

8.3. Documentation Requirement List The schedule to deliver the configuration documents is specified in the AD1 that defines the DRL for the contractor. The tables of content for some documents are defined in the AD1 (DRD).






VG-AP-2-C-0005-CNES

Page : 27/37 Ed.: 1 Rév.: 5 Date :28/03/2003

Safety regulations The industrial contractor must apply the following requirements :

SR1 : The industrial contractor must apply on site rules of the AD5 SR2 :Components and installations must be consistent with mandatory directives, norms and

rules applicable on French territory SR3 :The industrial contractor shall provide a certificate delivered by an officially agreed

organism See applicable documents AD2 to AD4






VG-AP-2-C-0005-CNES

Page : 28/37 Ed.: 1 Rév.: 5 Date :28/03/2003

9. APPENDIX






VG-AP-2-C-0005-CNES

Page : 29/37 Ed.: 1 Rév.: 5 Date :28/03/2003

APPENDIX A1 – CRITICAL ITEM FORM

APPENDIX A2 –ECR (CHANGE REQUEST) FORM

APPENDIX A3 –REQUEST FOR WAIVER FORM

APPENDIX A4- NON-CONFORMANCE REPORT FORM

APPENDIX A5 - CRITICAL ITEMS LIST FORM


DLA / SDS / AP DEPENDABILITY CRITICAL

POINT SHEET1 PROJECT: VEGA Ground Segment

1. CRITICAL POINT IDENTIFICATION Function: Equipment: Phase:

SHEET NO.

DATE:

ISSUE:

MANAGER:

STUDY REF.:

2. CRITICAL POINT DESCRIPTION (including possible causes) 3. TYPE OF CRITICALITY (linked to)

Probability Severity PDU Detectability Others 4. EFFECT ON THE PRODUCT OR THE SYSTEM (including the severity level)

G.0.A G.0.B G.1 G.2 5. ACTIONS TO REDUCE THE RISK OR SOLUTIONS FOUND 5.1 DATE OF OPENING: 5.3 DATE OF CLOSING:

5.2 DESCRIPTION OF PROPOSED ACTIONS

5.4 DESCRIPTIONS OF ACTIONS CARRIED OUT

Open Confirmed Closed Mitigated

6. COMMENTS ON PROCESSING: 7. NAME AND SIGNATURE OF MANAGERS 7.1 CNES 7.2 ESA / IPT Dependability Manager: AP Manager: Dependability Manager: AP Manager:

Technical Manager: Project Manager: Project Manager:

1 This sheet will be included in the CIL logbook


PROJECT LOGO

CHANGE PROPOSAL

REQUEST

Sheet 1

Request No. :

R Date of request:

PROJECT :

Origin: CLASS:

BUDGET IMPACT ORIGINATOR ORIGINATOR MANAGER Budget size: € Return on investment criteria:

QLTY SAFE RENT Other

Name: Department : Date : Signature :

Name: Department: Date : Signature :

TITLE:

IAE/SSP: IAE title:

DESCRIPTION OF THE REQUEST: Encl:

JUSTIFICATION OF REQUEST : Encl:

APPLICABLITY: IDENTIFIED IMPACTS

IMP No. PT code Description of the product Engineering Manager

Issuee

CHANGE BOARD COMMENTS

Name: Date: Decision Step 0 :


PROJECT: CHANGE PROPOSAL

INSTRUCTION

Sheet 2 page 1

Request No.: Filiation Instruction No.

R - - CLASS:

Instruction Authority Originator Manager Name:

Department : Date : Signature:

Name: Department : Date : Signature:

TITLE:

IAE/SSP: IAE title:

Product Ref::

DESCRIPTION OF INSTRUCTION : Encl:

JUSTIFICATION OF INSTRUCTION : Encl:

Contractual influences : Costs: delay :

APPLICABILITY:

AFFECTED DOCUMENTS

Reference Iss./Rev Description of the Product Updating manager

Impact on the Product

Safety Functional Reliability Performance Availability Interfaces Life limit Qualification Interchangeability Implementation


PROJECT: CHANGE PROPOSAL INSTRUCTION

Sheet 2 page 2

Request No.: Filiation Instruction No.

R - - CLASS:

TITRE :

Financing : Budget code 1: Budget code 2: Contract No.: Payment: Service order Cash with order Modification to order

Manager estimated cost :

Performance time limit from order::

ESTIMATE AND WORK PERFORMANCE ORDER

Estimate ref. Date Originator Amount Currency

Decision W.P.O. Reference

Date of W.P.O.


Name of board: Date : Decision Step 1 :

(if detailed comments, see sheet page 4)

WORK FOLLOW-UP:

PV reference Date Description of compliance PV Engineering Manager report

VALIDATION:

Validation report reference

Date Description of validation report Engineering Manager decision

CLOSING OF CHANGE FILE


Name of board: Date : Decision Step 2 :

(if detailed comments, see sheet page 4)


��

��

VEGA Programme Company REQUEST FOR WAIVER Waiver noVEGA-GS project RFQ

design charc. Functionalcategory

Critical CF0Major CF1Minor CF2

CF3Company Contractual

levelClass Date

Name RequesterLevel 2, level3

MajMin

Sub-Contractorlevel 1

MAI MinMAS

PrimeIndustrial contractor

MAI MinMAS

Authority : Prime Industrial Contractor Name :

Quality opinion

Opinion Name Date Signature

Project Decision

Issue date

Contractor nameRequesting Dpt.

Tech. Organigram no.

Application

Atached doc.no.

SimpleMultipleNot ident. Batch

Brief description of defectQuantity involved

NCR no.

Refer MRB

Life time/potential Other

Consequences

Description of defect

Immediate corrective action :

Identified cause :

Preventive action :

Justification synthesis, residual risks and consequences(reference documents) :

RAMS Restriciton for use

Coupling Specific operaitons

Reference :

Designation :

Functional performances

Serial or batch no.

Common VEGA/ArianeAriane Dev. Reference

Precedences

12


Product involved at this level :Requester

Level 3

Consequences on product : Level 2

Prime contractor

Consequences on upper level product :

CNES/DLA/SDS

Advice on proposed actions and justification files :

Class MAJ MIN Class MAJ MIN Class MAJ MIN Class MAJ MIN Class MAJ MINAcceptable Yes No Acceptable Yes No Acceptable Yes No Acceptable Yes No Acceptable Yes No

Name, date, signature Name, date, signature Name, date, signature Name, date, signature Name, date, signature

ProjectCNES/DLA/SDS ESA/IPT

VEGA ProgrammeVEGA-GS Project

Contractor level

Quality Assurance Technical assessmentRAMS Quality assurance

Waiver request investigation form

Company Requester Waiver no.Issue date

22


ANOMALY REPORT (FA) NON-CONFORMANCE REPORT (NCR)

PROJECT : VEGA GROUND SEGMENT

FA/NCR N° : | | | | / |__|__|__|__|

LOCATION : Contract identification : …………………………………… FACILITY (EAI) : Issue date MANUFACTURING EXPLOITATION SYSTEM (SSP) : / / INTEGRATED TESTS CAMPAIGN Writer

COMPONENT : Name : SOFTWARE DOCUMENT IDENTIFICATION N° .O.T.P. : Company : HARDWARE

CONSTAT : Procedure identif. |__|__|__|__|__|__|__|__|__|__|__|__|__| Operation identif. |__|__|__|__|__|__|__|

Tittle : ............................................................................................................................................................................. ANOMALY OR NON-CONFORMANCE DESCRIPTION, CIRCUMSTANCES : ANALYSIS : CAUSES, POTENTIAL RISKS :

CLASSIFICATION FA/NCR

major minor secondary

LEVEL 1 ACTION ITEM : Technical manager suggestion : FUNCTIONAL CATEGORY

CF0 CF1 CF2 CF3

Quality Manager Technical Manager Project Manager Tests Manager

NAME : NAME : NAME : NAME : OPINION AND SIGNATURE

OPINION AND SIGNATURE

OPINION AND SIGNATURE

DECISION AND SIGNATURE :

LEVEL 1 ACTION ITEM CLOSURE : INTERVENTION DESCRIPTION : Spare part serial number _____________________If change give Ref : ___________________

Date : ............................... Ref. Oper. : ......................... AP Manager : ..................... Visa AP :

MRB REMARKS : CTTA N° Level 2 Action item RFW N° : YES NO Complementary distribution :

Original :.Quality manager Copies : VEGA Project Manager Contractor


Sheet n° Critical item

2 O: ouvert, C: confirmé, F: Fermé ou clos, A: atténué