Page: 1/22 ExoMars CONFIGURATION MANAGEMENT REQUIREMENTS EXM-MS-RS-ESA-00008 Issue 1, Rev. 0 Date and Signature Prepared Agreed HME-CLS P. Provasi 29 June 2007 Approved HME-ME D. McCoy 29 June 2007
Page: 2/22 DOCUMENT CHANGE LOG Issue/ Revision Date Modified pages Observations 1/0 29 June 2007 New document first release
Page: 3/22 Table of Contents 1 DOCUMENT SCOPE...4 2 INTRODUCTION...5 2.1 Convention for Requirements Numbering, Priorities, and Comments...5 3 REFERENCE DOCUMENTS...6 3.1 Normative Documents...6 3.2 Informative Documents...6 4 CONFIGURATION AND DOCUMENTATION MANAGEMENT INTEGRATED REQUIREMENTS...7 5 DOCUMENTATION MANAGEMENT REQUIREMENTS...8 5.1 Supplemental DM implementation requirements...8 6 CONFIGURATION MANAGEMENT REQUIREMENTS...10 6.1 Applicable Standard...10 6.2 Supplemental CM implementation requirements...10 6.3 Supplemental Configuration Identification requirements...11 6.4 Supplemental Configuration Control requirements...11 6.5 Supplemental Configuration Status Accounting requirements...13 6.6 Supplemental Configuration Verification requirements...14 6.7 Supplemental DRD requirements...15 7 LIST OF ACRONYMS AND ABBREVIATIONS...21 7.1 Definitions...21 7.2 Abbreviations...21
Page: 4/22 1 DOCUMENT SCOPE This document defines the Configuration and Documentation Management requirements applicable to the ExoMars Project. It is a complement to the Management Requirements.
Page: 5/22 2 INTRODUCTION The Configuration and Documentation management requirements to be applied for the ExoMars project are defined in the ECSS series of standards. This document integrates those standards by adding supplemental requirements and clarifications. 2.1 Convention for Requirements Numbering, Priorities, and Comments The following convention is adopted for numbering requirements: Acronyms in the first part of the number: PL: Payload Acronyms in the second part of the number: ROV: Rover; GEP: Geophysics and Environment Package. - is used as a separator between acronyms denoting the parts of the system to which the requirement is applicable; / is used as a separator for denoting interfaces between parts of the system. The priority of a requirement is indicated by the use of shall or should, as follows: Priority Meaning Shall Mandatory Mandatory requirements, or hard requirements, which must be implemented. They constitute core requirements of the project in order to fulfil the mission objectives. should Goal These requirements are aiming at improving the performance or outcome of the mission. Until CDR, if a goal is not achieved the boundary conditions under which the performance can be achieved, shall be documented. A goal may be re-classified into a mandatory requirement after the CDR, possibly by limiting the boundary conditions under which the performance is achieved. Table 1: Classification of Requirements Priorities. Each requirement is clearly numbered and, a requirement may be preceded or followed by a commentary (an explanatory note). This commenting text may describe the context in which a requirement has to be understood, explain the rationale for the requirement, or refer to the source of the requirement.
Page: 6/22 3 REFERENCE DOCUMENTS The documents listed here are available on request to the ExoMars Project Office. In case of conflict between Normative References and this document the contractor shall inform the ExoMars Project Office for resolution. 3.1 Normative Documents Normative References are directly applicable in their entirety to this document and are listed below as dated or undated references. These normative references may be cited at appropriate places in the text. For dated references, subsequent amendments to or revisions of any of these document apply to this statement of work only when incorporated in it by amendment or revision. For undated references, the latest signed version is applicable and must be incorporated by the contractor in the project baseline. Normative Documents - Standards NR 01 ECSS-M-40B dated 20 May 2005 ECSS Standard Space Project Management Configuration Management NR 02 ECSS-M-10B dated 13 July 2003 ECSS Standard Space Project Management Project Breakdown Structures NR 03 ECSS-M-50A dated 19 April 1996 ECSS Standard Space Project Management Information/Documentation Management NR 04 ECSS-Q-20-09B dated 8 March 2002 ECSS Standard Space Project Management Non-conformance Control System 3.2 Informative Documents Informative References are applicable to this document only when specifically called up in the text with specific indications of the parts of the document that are to be applicable. Otherwise the documents are listed below for information only as an aid for the purpose of understanding. For dated references, subsequent amendments to or revisions of any of these document apply to this statement of work only when incorporated in it by amendment or revision. For undated references, the latest signed version is applicable and must be incorporated by the contractor in the project baseline pending the use of the document as explained above. Informative Documents - Standards IR 01 ECSS-P-001B dated 14 July 2004 Glossary of Term
Page: 7/22 4 CONFIGURATION AND DOCUMENTATION MANAGEMENT INTEGRATED REQUIREMENTS CMM 010 The ECSS Standards for Configuration and Documentation Management, ECSS-M40B [ND 01] and ECSS-M50A [ND 03], are applicable in their entirely including the Document Requirement Definitions (DRDs) as defined in the annex of the standards. ESA s supplemental requirements defined within this document are also applicable. CMM 020 CMM 030 A compliance matrix to the requirements stated in applicable ECSS Standards, the supplemental requirements within this document, and the DRL shall be provided. The compliance matrix, together with the Contractor CM/DM Plan, is to be submitted as part of the Proposal and to be agreed with the Customer. The Contractor shall clearly state Non Compliances, exceptions, deviations and justifications. In case of non-compliance an alternative way of implementation shall be proposed. The Contractor shall appoint a responsible for the Contractor s Configuration and Documentation Management for the project. In this function, this person shall act as the single-point contact for all matters relating to CM and DM. This person is responsible to guarantee that all actors at any time use identical and controlled data. This person shall be responsible for the: CMM 040 CMM 050 1. preparation, implementation and maintenance of the project compliant CM and DM plan; 2. Establishment and management of a compliant configuration and documentation management system. 3. establishment and identification of Configuration Items; 4. establishment of requirements, approval process and release of Product documentation 5. establishment and preparation for the Configuration Control Board within his own organisation; 6. establishment and distribution of configuration status reports; 7. provision of adequate and accurate documentation support for reviews; 8. processing of changes and waivers, and the release of implementation documents; 9. preparation of engineering change proposals; 10. establishment and operations of a system for the correlation of the as-built and as-designed configuration; 11. maintenance of effectively control (model, types and serial numbers); 12. establishment of an interface control system; 13. establishment of a general project documentation system; 14. establishment and control of document, drawing and software libraries The Contractor shall establish an effective Configuration and Documentation Management system and is responsible for its implementation in its own organisation and at all levels of its Subcontractor s organisation. Hence each Contractor shall transfer all requirements contained in this document to its subcontractors and to efficiently overview their implementation. In case the Contractor feels that tailoring of the requirements to his lower tier Contractors is beneficial, he shall justify the tailoring and bring it to the attention of the pre-teb process of the respective lower tier procurement process. CM shall interface with Project Management, Product Assurance, design, development, production, integration and test functions. The Customer retains the authority to perform CM and DM system audits at all levels of Contractors.
Page: 8/22 5 DOCUMENTATION MANAGEMENT REQUIREMENTS 5.1 Supplemental DM implementation requirements The following implementation requirements are applicable in addition to the ECSS Standard ND-03: CMM 100 The Contractor shall establish and maintain a document management system throughout the lifetime of the project. The document management system shall provide up-to-date information on all aspects of the project at all times and shall be accessible to all project participants. It shall serve as reference for technical interfaces, for the documentation of the design and interface changes. CMM 105 The Contractor shall establish a document classification that identifies documents according the following classes: Class C (controlled): Contractually Controlled Baseline Documentation Class A (approved): documents submitted for Agency approval Class R (reviewed): documents submitted for Agency review Class O (other): all other documents submitted for information The documentation identified as Class C and A shall be signed by the Agency Technical Representative for approval. All changes to these documents shall be formally requested/justified by mean of an ECP and documented by a DCN issued to all recipients. The change shall be approved by the Agency before introduction into the document. CMM 110 CMM 115 Documents shall be identified by a unique title and number. Different versions of a document shall have different Issue/Revision number. The documents shall be identified according to the criteria shown in the Management Requirements Document MGT1200. The Contractor shall agree with the Customer and impose on his lower tier Contractors the procedures and standards for: Classification of documents Document numbering and identification Distribution of documents The format & content for each class of document (Documentation Requirements DRD) Approval for each class of document Updating for each class of document CMM 120 All documents released in the frame of the Project shall be delivered in electronic (searchable PDF) format. When paper versions are made available in addition, it is the responsibility of the Contractor to ensure and verify that the two formats are identical. The delivery shall only be made in either of the two forms: 1. CD/DVD 2. Placing all the files on an FTP Server.
Page: 9/22 The Contractor shall describe and agree with the Agency the method for exchange of data and documents with the Agency and with its subcontractors. CMM 130 Document deliveries to ESA shall include an electronic file (comma separated) of the Meta Data (electronic description of the content of the delivery) The Meta Data shall contain: Document Title, Version Number, Reference Number, Author etc.. The content and format of the Metadata file shall be agreed with ESA prior to delivery. CMM 140 Delivered documentation shall always contain at least the author signature. For formal deliveries (e.g. Data packages), no draft documents will be accepted. CMM 150 CMM 160 All technical documents shall clearly show on their front page the CI number they refer to. Each page of a document shall be individually identifiable with the document identification code page number, revisions status and date of issue. This information shall be typed systematically on the upper right hand or left hand corner of each page such that the information is always opposite the binding fixture. CMM 170 Hard copy document submitted to ESA shall be of adequate quality and the contrast between printed information and background shall be sufficient to allow further reproduction. CMM 175 The Contractor shall agree with the Agency a document storage (as hard or soft copy) period of not less than 2 years after termination of all ExoMars operations. CMM 180 CMM 190 Electronic documents must be formatted in such a way that, if printed, they provide a true copy of the hard copy document. All drawings, pictures tables or diagrams shall be part of the document s electronic file. The Contractor shall ensure that all documents and document updates are approved as required. CMM 195 CMM 196 CMM 197 CMM 198 CMM 199 Documents shall be updated either by a revision or by a new issue. Revisions will be made for minor additions, deletions or changes of information. Any modification between issues and revisions shall be clearly identified in the text. All documents shall be ISO A4 size and shall be suitable for accommodation in loose binders (e.g. ring binders, European Standard). If diagrams, tables and other large document/pages are wider than A4 size they shall conform to an ISO standard size and be folded to A4 size An index of all deliverable documents, the Document Delivery List DDL, shall be established by the Contractor, as answer to the Agency Document Requirement List (DRL), including the document classes and delivery times. The DDL shall be updated and maintained throughout the project lifetime. The DDL shall be delivered for all major reviews. The Contractor shall distribute the agreed Document Delivery Lists to its lower tier Contractors
Page: 10/22 6 CONFIGURATION MANAGEMENT REQUIREMENTS 6.1 Applicable Standard CMM 200 All requirements stated in IR-01 section 5 Configuration Management Requirements- are applicable. All DRD Templates defined in the IR-01 Annex A thru L are applicable. 6.2 Supplemental CM implementation requirements CMM 220 CM shall make use of electronic database software to apply computer aided CM functions such as: CI identification and CI Tree preparation; baseline tracking including as-designed / as-built difference comparison; release status; active change control and impact analysis; status accounting and reporting. Independent of backup solutions all data shall be handled according to single source principles. The Contractors CM Database (CMDB) will contain the CIDL relevant information and additionally the as-built differences. All changes will be formally tracked within the database. The CIDL, ABCL and Status Accounting Reports shall be generated from the database. For the establishment of baselines the corresponding Configuration Lists (e.g. CIDL, ABCL, TDCL) will be issued as a document and after the corresponding review formally released. The contractor shall maintain or establish libraries or repositories for all documents, drawings and software that form or pertain to the configuration baseline. CMM 230 A software library system shall be established and shall include two separate and distinct libraries as follows: 1. Engineering Library (Software Development) - as the coding and informal testing is completed, the codes are released into the Engineering Library for integration and formal integration testing. Change control over codes entered into this library is the responsibility of the software project engineers and software PA. All coding and testing activities use as their basis the controlled baseline versions contained in the Master Software Library.
Page: 11/22 2. Master Software Library (Software Product) - an off-line library containing all source codes and executable codes of software versions, which have been formally released by Software Control Board (including patch versions which have been delivered to the user). This library contains the software transferred onto transportable media (disk, tape, cassette), verified by PA and controlled by CM. Formal change control is enforced and entry to or removal from the Master Software Library may only be authorized by the software CM responsible. All deliveries of software to the Customer shall be copies of the codes residing in the Master Software Library, which have been certified by software PA as an exact copy of the master. The Master Software Library also shall contain the master copies of all digitised files for software documentation. CMM 240 The Configuration Item Data Lists (CIDL), the As Built Configuration List (ABCL)/Test Configuration Data List (TCDL) and all the CSA reports (including the NCR Index and Status List) shall be delivered in the form of a signed document (searchable PDF file) for the project reviews and as an Excel file for the progress meetings and for the reviews. The two formats shall be identical in content. Each delivery (including the Excel ones) shall be identified by a different issue than the previous one. 6.3 Supplemental Configuration Identification requirements CMM 250 Numbering conventions shall be established and applied to the identification of configuration items, configuration documents, changes as well as to parts and assemblies in conformance with the numbering and labelling requirements stated in the ECSS standard. The document identification is further specified in the Management Requirements 6.4 Supplemental Configuration Control requirements CMM 260 Engineering Change Process: The following Engineering Change process shall be implemented by the Contractor with respect to the interface with the Customer. Change Initiation The customer may initiate a change by issuing an Engineering Change Request (ECR) or an equivalent written instruction. The contractor initiates a change by submitting a Engineering Change Proposal (ECP) to the customer. If an ECR is raised, the Engineering Change Requests shall be processed through the customer CCB and shall be tracked and status controlled. Upon validation by the customer CCB, ECRs shall be provided to the Contractor for feasibility evaluation and preparation of a responsive Engineering Change Proposal (ECP), when applicable.
Page: 12/22 The identification number assigned to the ECR shall be referenced on the corresponding Engineering Change Proposal (ECP). Classification of Change The classification of ECPs shall be in compliance with the contractors contract conditions and specific requirements stated by the customer (project). Engineering Change Proposals shall always be accountable against a CI. The ECP shall be addressed to the lowest level of CI where interchangeability is regained (i.e., where either the old or the new configuration may be assembled into the next higher assembly without affecting form, fit, function). In the case where an ECP is written against a higher level CI, related ECPs shall be written against all lower level CIs affected by the change; or, alternatively, all lower level affected CIs shall be included in the same ECP if they are under control of the same organization. Submittal and Approval Changes have to be accepted by the corresponding contractor CCB or EB prior to submittal to the next higher level. No formal approval of modifications may be given in cases of submission of an incomplete ECP package. An ECP shall be revised when requested by the customer. Change Implementation Implementation control starts with an authorised change disposition. The approved change shall be listed in the CIDL besides the documents which are affected.
Page: 13/22 Upon approval of an ECP, the change shall be incorporated first in the affected documentation, and thereafter implemented in the products (hardware, software, firmware product, operations products). After implementation of a change into the affected document, the documents shall be released with a higher index (issue/revision).the incorporated change shall be listed in the change record of the related document. An updated CIDL records the document with the new status (index). All incorporated changes disappear from the current CIDL and shall be tracked by a separate record to identify the incorporated changes. A change as defined in Engineering Change Proposal is not completed and closed until all consequential changes have been implemented and affected items have been approved and released. CMM 270 Baseline Management: Baselines shall be managed applying the following: 1. The Contractor shall manage its baseline so that a configuration baseline shall only be established when all the actions coming from a Review are satisfactorily closed by updating and releasing the affected documentation. 2. The baseline is represented by the full set of documents contained in the review data package updated version (the list of paragraph 5.3.1.4 of the ECSS-M40B, shall be completed by including the Design Justification documents like analyses, trade offs and design reports, test and verification documentation, as per paragraph 3.1.18 of the same standard. 3. To complete the list of baselines of para 4.3.2.4 of the ECSS-M40B, the Contractor shall include as part of the baselines the result of the Test Readiness Reviews, the Test Review Boards and the deliveries of all the models that are linked to the FM (e.g. STM, EM, QM). 4. The contractor shall relate all baselines to each other and shall manage their evolution and differences so that they are controlled, justified, assessed and tracked. 5. Each configuration item baseline shall be linked to the higher and lower level items baselines and consistency shall be ensured or discrepancies controlled and reported. 6. After the approval of a baseline, all changes to the documents composing the baseline shall be formally requested/justified by means of an ECP. The change shall be approved by the Customer before introduction. 6.5 Supplemental Configuration Status Accounting requirements CMM 280 For Configuration Status Account Reporting all Index and Status Lists can be merged in a single document. CIDL and ABCL/TCDL shall be different documents.
Page: 14/22 6.6 Supplemental Configuration Verification requirements CMM 290 Reviews and configuration audits shall be performed before the acceptance of a configuration baseline to assure that the product complies with its contracted or specified requirements and to assure that the product is accurately reflected by its configuration documents. The configuration verification activities include: 1. The formal examination to check that a configuration item has achieved the performance and functional characteristics specified in its configuration documents. 2. The formal examination of the 'as built' configuration of a configuration item to check that it conforms to its product configuration documents. Configuration verification is an integral part of the total verification process. CMM 295 The Contractor shall conduct audits to verify the application of Configuration Management requirements by its lower tier Contractors.
Page: 15/22 6.7 Supplemental DRD requirements Configuration and Documentation Management Plan CM-01: In addition to the DRD defined in Annex A of the ECSS-M-40B standard, the following shall also be included: CMM 500 CMM 510 The Documentation Management Plan shall address all requirements stated in ECSS-M-50A dated 19 April 1996. The contractor shall provide a description of the Configuration Management and Documentation Management tools used and how the requirements (stated within this document and the ECSS Standards) have been implemented within this environment. CMM 520 The contractor shall identify the relationship between the Contractor s SW and HW configurations in the product tree. CMM 530 The Contractor shall identify the ESA CM/DM requirements made applicable to the subcontractors in the form of an applicability matrix, with explanation in case of deviation. CMM 540 The Contractor shall describe the methods to be used for the product as-built configuration baselining and how its relation with the manufacturing, assembling, testing and verification functions/activities will be implemented. CMM 550 Examples of CIDL, ABCL, Index and Status Lists with relevant instruction on how to generate, maintain and use them CMM 560 Samples of the CR, ECP, DCN, CCN, RFW, NCR forms with the relevant instructions CMM 570 For SW items the Contractor shall provide the description of the methods to be used to identify the version of source/object executable code
Page: 16/22 Product Tree - PT CM-02: In addition to the DRD defined in Annex B of the ECSS-M-40B standard, the following shall also be included: CMM 600 The PT shall be in two forms, indented list and graphical diagram CMM 610 The PT shall have the structure of defined product items and their hierarchical division and subdivision, such that every sub-tree contains all products related to that respective node. The subdivision shall go down to at least include the items of every subcontract and all models CMM 620 A hierarchical address code shall be used. CMM 630 The item specification shall be identified (Specification Tree). CMM 640 The item responsible company shall be identified. Configuration Item List - CIL CM-03: In addition to the DRD defined in Annex C of the ECSS-M-40B standard, the following shall also be included: CMM 700 The CIL shall be structured in form of an indented list and of a graphical diagram. The level of detail shall be at least the same of the PT, or lower. CMM 710 It shall also contain all the necessary data to identify and correlate the PT to the configuration documentation, such as: Item number and title as per PT CI number Part number (drawing number) Model CIDL reference
Page: 17/22 Configuration Item Data List - CIDL CM-04: In addition to the DRD defined in Annex D of the ECSS-M-40B standard, the following shall also be included: CMM 800 The Contractor shall list in the review s CIDL all documents contained in Review Data Packages. CMM 810 The CIDL shall contain all the lower level CIs and shall list for each of them, as a minimum, the Interface documentation, the technical specifications and all the applicable documents, the relevant CIDL and ADP, and all the changes and departures to these documents that are approved and not yet incorporated. CMM 820 All the documents and drawings shall be listed showing, at least, the title, the document reference, the (last valid) issue and revision, the date and, for the drawings, the sheets with their revision index. CMM 830 The modification of the CIDL shall be marked by showing, for each document and drawing/part, the CIDL issue that has seen that entry introduced or modified the last time. CMM 840 The CIDL shall contain the list of all the Applicable Documents associated to the relevant Change Notices (CR, ECP, DCN) and approved Deviations (until incorporation). CMM 850 The CIDL shall contain the list of all the valid engineering and design documents produced according to the customer DRL or requested via CR, and all the documents that require the customer approval. All documents contained in Review Data Packages shall be listed as well. CMM 860 Per each document, the relevant approved Deviations and Change Notices shall be recorded as well, until their incorporation in a higher version of the document. CMM 870 The CIDL shall contain the indented list of the parts (including subcontractor s ones and SW) that constitute the C.I with their relevant drawings/specifications, their Part Numbers and quantity, down to the lowest level of detail. Per each part/drawing, the applicable approved Deviations and Change Notices shall be associated, until their incorporation in a higher version of the document.
Page: 18/22 As-Built Configuration List ABCL & Test Configuration Data List TCDL CM-05: In addition to the DRD defined in Annex E of the ECSS-M-40B standard, the following shall also be included: CMM 900 The Contractor shall obtain from the CM system the ABCL/TCDL to provide all information on the As-Built configuration of the CI specimen (Serial Number) and to enable comparison to the as-designed and reconciliation. The ABCL/TCDL, generated per each C.I. S/N shall be suitable for the physical inspection of the item. CMM 910 The indented list of parts (part breakdown section) shall be obtained from the equivalent section of the CIDL and shall be completed by adding: CMM 920 1. The actually used issue/revision of the drawing/part/specification 2. The installed quantities 3. The installed serial numbers or the lot/batch numbers 4. The reference to the applicable NCR, RFW or ECP 5. The QA certification reference 6. The relevant Log Book or Work Item 7. The differences between CIDL and ABCL shall be justified by the Contractor and approved by the Customer CMM 930 It shall contain all the sections and the data of the CIDL with associated approved nonconformances, waivers and changes applicable to the Item identified by the S/N.
Page: 19/22 Configuration Status Accounting Reports CM-06: In addition to the DRD defined in Annex G of the ECSS-M-40B standard, the following shall also be included: CMM 1000 The contractor shall generate all status accounting reports from the CM system. CMM 1010 The lists shall be organized by Configuration Items and, per each of them, shall be ordered by the reference number. CMM 1020 Document Index and Status List DSL shall also include: 1. Status (draft, formally released, Customer approved, under preparation/modification, superseded by, DCNxxx to be considered) 2. Change log (reference to the last change, included/not included) CMM 1030 Change Proposal Index and Status List CSL shall also include: 1. Contract number 2. Change classification 3. Change effectivity 4. Status (draft, formally released, rejected, withdrawn, approved, under preparation/modification, superseded by, implemented, etc) 5. Related documents like Customer Change Request, Disposition Record, impacted documentation, NCR/RFW, other changes The numbering of the change documents shall follow the document identification as described in the Management Requirement Document. Document Change Notice DCN CM-08: CMM 1100 A Document Change Notice shall be issued before to proceed with the modification of class C and A documentation (see CMM 105). The Document Change Notice shall contain: 1. Reference, title, issue and revision of the affected document 2. Related documents like CR, ECP 3. All affected pages (From-To) The DCR numbering shall follow the document identification as described in the Management Requirement Document.
Page: 20/22 NCR Index and Status List CM-11 CMM 1200 CMM 1210 The list of Non Conformance Requests (NCR) shall be automatically generated by the CM system and shall contain no discrepancies with the ABCL and the RFW Index and Status List. It shall cover both the spacecraft and the science instruments. The NCR numbering shall follow the document identification as described in the Management Requirement Document. The list shall be organized by Configuration Items and, per each of them, shall be ordered by the reference number. CMM 1220 Per each NCR, it shall list: 1. NCR document reference 2. Title 3. Issue/revision 4. Issue date 5. Class (Major/Minor) 6. CI number affected 7. Model affected 8. S/N affected 9. Drawing/Part affected (if any) 10. Design impact (yes/no) 11. Requirements impact (yes/no) 12. Reference to the RFW (if any) 13. Status (draft, formally released, withdrawn, approved) 14. Acceptance Data Package CM-12 The term End Item Data Package is related to system level deliveries, while The term Acceptance Data Package is generic and for ExoMars used for all lower tier deliveries. CMM 1300 CMM 1310 CMM 1320 CMM 1330 For each model/specimen delivered, the Contractor is requested to prepare a Data Package that shall contain, as a minimum, the Product Tree, the CIL, the CIDL, the ABCL and the TCDLs, the SCF, all the CSA reports, the NCR Index and Status List, the copies of all RFDs and the copies of all Major RFWs and NCRs. The End Item Data Package on system level shall also contain all Verification documentation like the VCD, the Verification and Inspections Plans, Procedures and Reports. The Data Package shall contain all lower levels data packages. All lower levels Acceptance Data Packages shall be prepared according to the above requirements
Page: 21/22 7 LIST OF ACRONYMS AND ABBREVIATIONS 7.1 Definitions Refer to ND 01 and to ND 05 7.2 Abbreviations Abbreviation ABCL ADP AR CCB CDR CI CIDL CIL CM CP CR CSA DB DDL DIL DM DRD DRL EB ECR EIDP EM FM HME H/W ICD ID Meaning As-built Configuration Data List Acceptance Data Package Acceptance Review Configuration Control Board Critical Design Review Configuration Item Configuration Item Data List Configuration Item List Configuration Management Change Proposal Change Request Configuration Status Accounting Design Baseline Document Delivery List Deliverable Item List Documentation Management Document Requirements Definition Document Requirements List Engineering Board Engineering Change Request End Item Data Package Engineering Model Flight Model Directorate of Human Spaceflight, Microgravity and Exploration Hardware Interface Control Document Informative Documents
Page: 22/22 NCR ND PA PDR PT QA QM QR RFD RFW RID SCF S/N SRR STM S/W TCDL TEB TRR VCD Nonconformance Report Normative Documents Product Assurance Preliminary Design Review Product Tree Quality Assurance Qualification Model Qualification Review Request for Deviation Request for Waiver Review Item Discrepancy Software Configuration File Serial Number System Requirements Review Structural & Thermal Model Software Test Configuration Data List Tender Evaluation Board Test Readiness Review Verification Control Document Agency European Space Agency ESA